navigation_skill

This skill helps you design intuitive app navigation and information architecture to improve findability and reduce user effort.

144

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill whawkinsiv/solo-founder-superpowers --skill navigation

  • SKILL.md4.6 KB

Overview

This skill helps you organize app navigation, structure content hierarchies, and improve findability for SaaS products. It focuses on practical patterns—top bars, sidebars, command palettes, breadcrumbs, and URL conventions—to match user mental models. Use it to design menu systems, labels, and flat vs deep information structures that reduce cognitive load.

How this skill works

I inspect your product surface to map primary and secondary navigation, suggest grouping and labels, and recommend URL patterns that mirror the information architecture. I propose page types (dashboard, list, detail, settings), content hierarchy, and progressive disclosure so users can find tasks without thinking. I also identify search, filter, and breadcrumb needs and flag overly deep nesting or ambiguous labels.

When to use it

  • At product inception to set navigation foundations
  • When redesigning navigation or improving findability
  • Before building menus, routes, or URL schemas
  • When users report difficulty finding features or feel lost
  • When adding new sections that might increase depth

Best practices

  • Match navigation to user tasks and mental models, not internal org charts
  • Prefer flatter structures; avoid more than 3 URL depth levels
  • Use clear, specific labels; if you must explain a label, change it
  • Show breadcrumbs for depth >2 and a page title answering “Where am I?”
  • Expose primary actions prominently and use progressive disclosure for advanced options

Example use cases

  • Design a sidebar + top-bar hybrid for a complex workspace app
  • Convert an existing deep menu into 5–9 clear groups via card-sorting
  • Define URL patterns and route names that mirror the IA for SEO and shareability
  • Add a global command palette (Cmd/Ctrl+K) for power-user navigation and actions
  • Create consistent page templates: dashboard, list, detail, settings, and empty states

FAQ

Keep 3–7 top-level sections for horizontal top nav; if you need more, use a sidebar or group items.

When should I prefer sidebar over top navigation?

Choose a sidebar for 5–20 sections, complex products, long sessions, or when sections have subsections; use headers and collapsible groups to manage depth.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational