navigation-patterns
Navigation-Patterns is a Claude Code skill for selecting and designing navigation systems that align with product structure, user tasks, and platform norms. It provides frameworks for choosing among global navigation types (tab bars, sidebars, top nav), local navigation (tabs, breadcrumbs), utility navigation (account, settings), and contextual links. Use this skill when architecting information systems for mobile or desktop products, evaluating navigation trade-offs, or ensuring users can consistently orient themselves and discover content across your interface.
git clone --depth 1 https://github.com/Owl-Listener/designer-skills /tmp/navigation-patterns && cp -r /tmp/navigation-patterns/interaction-design/skills/navigation-patterns ~/.claude/skills/navigation-patternsSKILL.md
# Navigation Patterns You are an expert in designing navigation systems that make products legible, traversable, and orientating. ## What You Do You select and design the right navigation patterns for a product's information architecture, platform, and usage patterns — so users always know where they are, where they can go, and how to get back. ## Navigation Types ### Global Navigation Present on every screen; provides access to top-level sections. - **Tab bar** (mobile): 3–5 destinations at bottom of screen; icons + labels; always visible - **Bottom navigation** (Android/web mobile): Material equivalent; same rules as tab bar - **Top navigation bar** (desktop/web): horizontal links in header; works for 4–7 destinations - **Side navigation / sidebar** (desktop apps): vertical list of destinations; scales to more items; supports nested structure - **Hamburger / drawer**: hides navigation behind a menu icon; reduces discoverability; reserve for secondary nav or screen-constrained contexts ### Local Navigation Scoped to the current section. - **Tabs**: switch between parallel views within a section; all tabs same hierarchy level - **Segmented control**: compact tab variant for 2–4 tightly related views - **Sidebar within section**: sub-navigation within a section (settings categories, doc chapters) - **Breadcrumbs**: show path from root to current page; essential in deep hierarchies ### Utility Navigation High-reach, low-frequency: account, notifications, search, settings, help. - Separate from primary navigation visually (typically top-right on desktop) - Should not compete with primary nav for visual attention ### Contextual Navigation Links between related content. - In-line links within body content - Related items (recommended articles, related products) - "Also in this section" links ## Choosing the Right Pattern | Situation | Recommended pattern | |---|---| | Mobile, 3–5 primary destinations | Tab bar | | Desktop app, many destinations or nested structure | Side navigation | | Simple marketing site or docs | Top nav bar | | Deep content hierarchy | Breadcrumbs + local sidebar | | Parallel views of the same content | Tabs or segmented control | | Occasional, non-primary access | Utility nav or overflow menu | ## Navigation Design Principles - **Orientation**: users should always know where they are (active state, breadcrumb, page title) - **Wayfinding**: users should be able to predict where a destination will take them before clicking - **Reachability**: on mobile, primary destinations must be in thumb reach (bottom of screen) - **Consistency**: navigation structure and placement must not change between screens - **Scent**: labels must accurately describe their destinations — test with first-click tests ## Active States Every navigation item needs a clear active/selected state that survives: - Default and active - Hover and focus - Disabled - Notification badge (when applicable) Active state must be distinguishable by more than color alone (weight, underline, indicator bar). ## Common Mistakes - Using a hamburger menu for primary navigation on desktop — it hides critical paths - Mixing navigation levels (global + local) in the same visual component - Inconsistent active states across different sections - Navigation labels that use internal product names users don't recognize - Too many top-level destinations (more than 7 creates choice paralysis; revisit IA before adding nav items) ## Best Practices - Validate navigation labels with first-click tests before building - Match platform conventions — users carry expectations from the OS and other apps - Design navigation before designing individual screens; navigation errors compound across the product - Test navigation with tasks that require users to cross sections — inter-section navigation is where IA breaks show up
Facilitate a structured team critique — framing, feedback rules, and actionable outcomes. Use when running a session with people in the room. For a solo expert review, use `heuristic-evaluation` (prototyping-testing).
Inventory and prioritise accumulated design inconsistencies across a product. Use when drift has built up over time. For token coverage specifically use `design-token-audit` (designer-toolkit); for WCAG gaps use `accessibility-audit` (design-systems).
Communicate design's contribution to business and user outcomes in stakeholder language. Use when reporting results upward. For choosing the metrics in the first place, use `metrics-definition` (ux-strategy).
Build a QA checklist for verifying that a build matches the design. Use at implementation review. For the spec engineers build from, use `handoff-spec`.
Establish review gates — criteria, checkpoints, and approval flow. Use when work ships without consistent review. For running one individual session, use `design-critique`.
Plan and facilitate a design sprint from challenge framing through prototype testing. Use when compressing discovery into days. For ongoing team cadence, use `team-workflow`.
Write the implementation handoff — measurements, behaviours, assets, states, and edge cases. Use when engineering picks up the work. For verifying the result afterwards use `design-qa-checklist`; for reusable library components use `component-spec` (design-systems).
Design the team's operating rhythm — task management, collaboration rituals, and tooling. Use when the day-to-day cadence needs structure. For a time-boxed sprint, use `design-sprint-plan`.