Navigation Patterns

Select and design a navigation pattern — tabs, drawer, hierarchy, or hub — matched to product structure and user tasks. Use when choosing how users move between sections. For the underlying content structure, use `information-architecture` (ux-strategy).

3,414 stars 447 forksFrontend & Design Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add Owl-Listener/designer-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add Owl-Listener/designer-skills --skill navigation-patterns
Manual install
git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git /tmp/designer-skills
mkdir -p ~/.claude/skills
cp -r /tmp/designer-skills/interaction-design/skills/navigation-patterns ~/.claude/skills/navigation-patterns

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.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
Read the full skill on GitHub

Details

Skill name
navigation-patterns
Path
interaction-design/skills/navigation-patterns/SKILL.md
License
MIT
Repo updated
5 September 2026

FAQ

What does the Navigation Patterns skill do?

Select and design a navigation pattern — tabs, drawer, hierarchy, or hub — matched to product structure and user tasks. Use when choosing how users move between sections. For the underlying content structure, use `information-architecture` (ux-strategy).

How do I install the Navigation Patterns skill?

Claude Code plugin: /plugin marketplace add Owl-Listener/designer-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Navigation Patterns popular?

It lives in Owl-Listener/designer-skills, which has 3,414 GitHub stars and 447 forks.

Related skills

A B Test Design

3.4k

Owl-Listener/designer-skills

Design an A/B experiment — hypothesis, variants, primary metric, and sample size. Use when a change can be measured quantitatively at scale. For observing behaviour qualitatively, use `test-scenario`.

Testing & QA447

Accessibility Audit

3.4k

Owl-Listener/designer-skills

Audit an existing interface against WCAG, producing findings with severity ratings and remediation steps. Use when you have a design or build to assess now. Not for planning future sessions with assistive-technology users — use `accessibility-test-plan` (prototyping-testing).

Frontend & Design447

Accessibility Test Plan

3.4k

Owl-Listener/designer-skills

Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol. Use when scheduling testing with real AT users. Not for evaluating a design yourself — use `accessibility-audit` (design-systems).

Testing & QA447

Readable Measure

3.4k

Owl-Listener/designer-skills

Set line length and measure for comfortable reading across type sizes and breakpoints. Use when tuning body text. Covers measure only — for the full size and weight scale, use `typography-scale`.

Frontend & Design447

Naming Convention

3.4k

Owl-Listener/designer-skills

Establish naming rules for components, tokens, and layers with patterns and worked examples. Use when names are inconsistent or being set. For what the tokens actually contain, use `design-token`.

Frontend & Design447

Search UX

3.4k

Owl-Listener/designer-skills

Design search — query input, zero results, refinement, and result presentation. Use when users retrieve rather than browse. For browse structure, use `navigation-patterns`.

Frontend & Design447

Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.