Impeccable
bestofjs/bestofjs
A skill your agent uses when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a…
Select and design a navigation pattern — tabs, drawer, hierarchy, or hub — matched to product structure and user tasks.
Install Navigation Patterns
$ npx skills add Owl-Listener/designer-skills --skill navigation-patterns -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Owl-Listener/designer-skills navigation-patterns --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/interaction-design/skills/navigation-patterns .claude/skills/navigation-patterns && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "navigation-patterns" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/interaction-design/skills/navigation-patterns into .claude/skills/navigation-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "navigation-patterns", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Owl-Listener/designer-skills/tree/main/interaction-design/skills/navigation-patternsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Owl-Listener/designer-skills --skill navigation-patterns -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Owl-Listener/designer-skills navigation-patterns --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/interaction-design/skills/navigation-patterns .agents/skills/navigation-patterns && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "navigation-patterns" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/interaction-design/skills/navigation-patterns into .agents/skills/navigation-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "navigation-patterns", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Owl-Listener/designer-skills --skill navigation-patterns -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Owl-Listener/designer-skills navigation-patterns --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/interaction-design/skills/navigation-patterns .cursor/skills/navigation-patterns && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "navigation-patterns" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/interaction-design/skills/navigation-patterns into .cursor/skills/navigation-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "navigation-patterns", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Owl-Listener/designer-skills.git --path interaction-design/skills/navigation-patterns--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Owl-Listener/designer-skills --skill navigation-patterns -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Owl-Listener/designer-skills navigation-patterns --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/interaction-design/skills/navigation-patterns .gemini/skills/navigation-patterns && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "navigation-patterns" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/interaction-design/skills/navigation-patterns into .gemini/skills/navigation-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "navigation-patterns", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Owl-Listener/designer-skills navigation-patternsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Owl-Listener/designer-skills --skill navigation-patterns -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/interaction-design/skills/navigation-patterns .github/skills/navigation-patterns && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "navigation-patterns" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/interaction-design/skills/navigation-patterns into .github/skills/navigation-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "navigation-patterns", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Owl-Listener/designer-skills --skill navigation-patterns -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Owl-Listener/designer-skills navigation-patterns --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/interaction-design/skills/navigation-patterns .opencode/skills/navigation-patterns && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "navigation-patterns" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/interaction-design/skills/navigation-patterns into .opencode/skills/navigation-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "navigation-patterns", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
navigation-patterns- GitHub stars
- 2.9k
- Used in
- 1 other repo
- Token cost
- ~1k tokens
- SKILL.md length
- 502 words
- Files
- 1
- Skills in repo
- 107
- Repo updated
- First seen
- Licence
- MIT
At a glance
Select and design a navigation pattern — tabs, drawer, hierarchy, or hub — matched to product structure and user tasks.
- Choosing how users move between sections
- SKILL.md covers What You Do, Navigation Types, Choosing the Right Pattern and Navigation Design Principles, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Tasks that involve UX design
What it does
Navigation Patterns is an agent skill from Owl-Listener/designer-skills. 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).
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Frontend & Design, covering UX design. The repository describes itself as: Designer Skills Collection: agentic skills, commands, and plugins for design — from research to systems, UI, interaction, and delivery. The licence is MIT.
When your agent uses it
- Choosing how users move between sections
- Tasks that involve UX design
Example prompts
- “/navigation-patterns”
What it can do on your machine
Read from SKILL.md and the folder at commit 9a6930c. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Navigation Patterns loads about 1k tokens when it runs. Until then it costs about 69 tokens; SKILL.md has 502 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Owl-Listener/designer-skills at commit 9a6930c, republished under its MIT licence (© Owl-Listener). 502 words, ~1,036 tokens.
Download SKILL.mdSave it as
.claude/skills/navigation-patterns/SKILL.md (or your agent's skills folder).- name
- navigation-patterns
- description
- 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).
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 |
Show full SKILL.md (211 more words)Show less
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
© Owl-Listener, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in interaction-design/skills/navigation-patterns of Owl-Listener/designer-skills.
Open the folder on GitHubat commit 9a6930c
Used in 1 other repository
We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in Owl-Listener/designer-skills, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Navigation Patterns next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Navigation Patterns this skillOwl-Listener/designer-skills | 2.9k | 1 repos | ~1k | Automated safety check: Pass | MIT | |
| Impeccablebestofjs/bestofjs | 3.1k | 27 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Interface Design for Dashboards and Appsholaboss-ai/holaOS | 11k | 3 repos | ~6k | Automated safety check: Pass | MIT | |
| Animategrowupanand/ConvoForm | 102 | 6 repos | ~1.9k | Automated safety check: Pass | Apache-2.0 | |
| Migrate Content Iadocker/docs | 4.7k | — | ~5.1k | Automated safety check: Pass | Apache-2.0 | |
| UX WalkthroughXiaoMi/hiui | 878 | — | ~1.3k | Automated safety check: Pass | MIT |
Similar skills
Interface Design for Dashboards and Apps
holaboss-ai/holaOS
Pushes an agent past generic defaults when designing dashboards, admin panels, SaaS apps and tools, with attention to structure, type, navigation and how data is shown.
Animate
growupanand/ConvoForm
Review a feature and enhance it with purposeful animations, micro-interactions, and motion effects that improve usability and delight.
- Official
Migrate Content Ia
docker/docs
Handle Hugo docs information-architecture moves: discover old vs new URLs, add front matter aliases (Phase 1), update in-repo links (Phase 2), interactive List 2 resolution and fragment validation…
UX Walkthrough
XiaoMi/hiui
体验走查 skill。适用于代码库、URL、截图三种输入，输出结构化体验问题报告，并同步生成本地 docx 报告。触发词：体验走查、UX review、交互走查、界面审查、体验问题。
Color Audit
rome-os/rome
Audit a design system's color palette against measurable color-science disciplines — WCAG/APCA contrast of declared token pairs, perceptual (OKLCH) ramp uniformity, color-blindness safety of…
More from Owl-Listener/designer-skills
All 107 skills in this repoA B Test Design
Owl-Listener/designer-skills
Design an A/B experiment — hypothesis, variants, primary metric, and sample size.
Accessibility Test Plan
Owl-Listener/designer-skills
Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol.
Aesthetic Usability
Owl-Listener/designer-skills
Apply the Aesthetic-Usability Effect — polished, consistent interfaces are perceived as more usable and forgive minor friction.
Affinity Diagram
Owl-Listener/designer-skills
Cluster many qualitative data points into themes and insight statements.
Animation Principles
Owl-Listener/designer-skills
Apply animation principles — easing, staging, follow-through — to one specific UI motion.
Business Design
Owl-Listener/designer-skills
Read financials, map competitive landscapes, and argue design decisions in the language of value.
Related
Categories
Questions about Navigation Patterns
What does Navigation Patterns do?
Select and design a navigation pattern — tabs, drawer, hierarchy, or hub — matched to product structure and user tasks. Navigation Patterns is an agent skill from Owl-Listener/designer-skills. Select and design a navigation pattern — tabs, drawer, hierarchy, or hub — matched to product structure and user tasks.
When should I use Navigation Patterns?
Navigation Patterns fits situations like: choosing how users move between sections; tasks that involve UX design.
How do I install Navigation Patterns in Claude Code?
Run `npx skills add Owl-Listener/designer-skills --skill navigation-patterns -a claude-code`. Or copy the skill folder (interaction-design/skills/navigation-patterns in Owl-Listener/designer-skills) into .claude/skills/navigation-patterns in your project. Claude Code loads it when a task matches its description.
How do I install Navigation Patterns in Codex?
Run `npx skills add Owl-Listener/designer-skills --skill navigation-patterns -a codex`. Or copy the skill folder (interaction-design/skills/navigation-patterns in Owl-Listener/designer-skills) into .agents/skills/navigation-patterns in your project. Codex loads it when a task matches its description.
Can I use Navigation Patterns in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Owl-Listener/designer-skills --skill navigation-patterns -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/navigation-patterns, .gemini/skills/navigation-patterns, .github/skills/navigation-patterns and .opencode/skills/navigation-patterns in your project.
What does Navigation Patterns need to run?
SKILL.md names no scripts, command-line tools or credentials: Navigation Patterns is instructions for the agent only.
Does Navigation Patterns access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Navigation Patterns safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Navigation Patterns use?
Navigation Patterns is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Navigation Patterns use?
About 1k tokens (SKILL.md is roughly 4.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Navigation Patterns?
Skills that share tags, products or a category with Navigation Patterns: Impeccable (bestofjs/bestofjs, 3.1k stars), Interface Design for Dashboards and Apps (holaboss-ai/holaOS, 11k stars), Animate (growupanand/ConvoForm, 102 stars) and Migrate Content Ia (docker/docs, 4.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Navigation Patterns?
Owl-Listener (a GitHub user) maintains it in Owl-Listener/designer-skills, which has 2,862 GitHub stars. The repository holds 107 skills in this directory. The repository was last updated on September 5, 2026.
Source: Owl-Listener/designer-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.