navigation-design

Design website and application navigation models with orientation, hierarchy, and responsive verification.

1|Updated Sep 11, 2026
One-click install
npx skills add https://github.com/rebuildup/my-web-2026 --skill navigation-design-rebuildup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: navigation-design
Source: https://github.com/rebuildup/my-web-2026/tree/main/skills/navigation-design
Command: npx skills add https://github.com/rebuildup/my-web-2026 --skill navigation-design-rebuildup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Designing navigation often devolves into stacking menu components without deciding whether navigation is needed, what information space it moves through, or how users understand their current location. This Skill provides a structured workflow to choose the right navigation model, preserve orientation and context, and verify the delivered interaction across responsive and accessible states. ## Core Features & Use Cases - Navigation model selection: Classify journeys (repeated non-linear tasks vs. linear transactions) and decide whether persistent navigation, breadcrumbs, side navigation, tabs, in-page navigation, or pagination fits. - Orientation and hierarchy design: Ensure current page, parent context, breadcrumbs, and headings agree so users always know where they are, even from deep links. - Responsive and accessibility verification: Check that wording, order, destination, current-state, and keyboard reachability survive breakpoint transformations. - Use Case: Redesigning a product docs site, use this Skill to separate global navigation from section side navigation, add hierarchy-only breadcrumbs, and verify keyboard access and current-state semantics across mobile and desktop. ## Quick Start Use the navigation-design skill to review my site's header, sidebar, and breadcrumbs and propose a navigation model that keeps users oriented on every page.

Frequently Asked Questions about navigation-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose the right navigation model for a website?

Classify the user journey first: repeated non-linear tasks with multiple destinations justify persistent navigation, while linear transactions or wizards should use continue, back, and progress instead. Then match scope to pattern, such as side navigation for repeated section switching or breadcrumbs for hierarchy.

When should I use breadcrumbs vs tabs in navigation design?

Use breadcrumbs only to show a page's ancestor hierarchy as secondary navigation, never for progress, history, or flat structures. Use tabs only when switching panel visibility within the same context; if activation changes the URL, treat it as a navigation link model instead.

Should every page be listed in the primary navigation?

No. Primary navigation should hold only the important top-level destinations needed to understand the product or service. Rare or contextual destinations belong in secondary locations, body links, or search so the navigation stays selective.

How do I keep navigation accessible on mobile and responsive layouts?

Preserve wording, relative order, destination, current-state meaning, and keyboard and touch reachability when navigation collapses or transforms across breakpoints. Verify by resizing continuously, opening collapsed states, and testing with long labels and keyboard-only operation.

When should I avoid adding persistent navigation?

Avoid persistent navigation for clear end-to-end transactions, wizards, or question flows where users move linearly. Simplify the journey first and use continue, back, and task progress; add navigation only when users must choose among multiple destinations themselves.