Loading...
Loading...
Found 17 Skills
When the user wants to audit, redesign, or plan their website's structure, URL hierarchy, navigation design, or internal linking strategy. Use when the user mentions 'site architecture,' 'URL structure,' 'internal links,' 'site navigation,' 'breadcrumbs,' 'topic clusters,' 'hub pages,' 'orphan pages,' 'silo structure,' 'information architecture,' or 'website reorganization.' Also use when someone has SEO problems and the root cause is structural (not content or schema). NOT for content strategy decisions about what to write (use content-strategy) or for schema markup (use schema-markup).
Website architecture planning: page hierarchy, navigation, URL structure, internal linking strategy. Use when user says "site structure", "page hierarchy", "URL structure", "navigation design", or "information architecture". NOT for XML sitemaps (use seo-sitemap).
Select and design navigation patterns that match product structure, user tasks, and platform conventions.
The persistent shell around an application — the top bar, the app launcher, the tenant and environment cue, and in heavy tools a status bar. In an estate of several applications the shell belongs to the estate rather than to any one app, and it is what carries a user between tools. Use when designing a top bar, an app switcher, a tenant selector, an environment cue, a status bar, or navigation between separate tools behind one login. For the locale, currency and unit controls the shell carries, see global-toolbar-controls.
Apply Fitts's Law to size and position interactive targets for fast, accurate interaction.