agentleFS
phazurlabsphazurlabs/sumi/skills/navigation-pattern-encyclopedia/SKILL.md

navigation-pattern-encyclopedia

Skill58 starsChanged 23 days agoApache-2.0View on GitHub

Every navigation pattern with specs, trade-offs, and production code: top bars, sidebars, bottom tabs, mega menus, breadcrumbs, command palettes, and contextual and mobile navigation. Use when choosing a nav model, fixing discoverability, or structuring information architecture.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When to use it, and the condition that rules it out

    line 58

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Navigation Pattern Encyclopedia — Every Nav Pattern

Mental model

Navigation answers three questions, in this order: where am I, where can I go, and how do I get back. A pattern that answers only the second is a menu, not a navigation system.

  • Visible beats hidden. Nielsen Norman's study (179 participants, six sites) found hidden navigation cuts content discoverability by nearly half and raises both time on task and perceived difficulty. Hide navigation only when the screen genuinely cannot hold it.
  • Information scent is the whole game. A label must let someone predict what is behind it. "Solutions" has no scent; "Pricing" has perfect scent.
  • Depth costs more than breadth. Two levels of fifteen items beat four levels of four. Every extra level is a place to get lost.
  • The pattern follows the destination count. Three to five destinations means bottom tabs or a top bar. Twenty-plus means a mega menu or search-first. Fifty means a command palette, because no menu structure survives that.

Index

IfPatternReference
5-7 destinations, marketing or app shellTop horizontal barprimary-navigation-patterns.md
20+ destinations, e-commerce or enterpriseMega menuprimary-navigation-patterns.md
Brand-led marketing siteCentered logo navprimary-navigation-patterns.md
Search is the primary actionNav with integrated searchprimary-navigation-patterns.md
Deep app, many sectionsSidebarprimary-navigation-patterns.md
Power users, 50+ destinationsCommand paletteprimary-navigation-patterns.md
Mobile, 3-5 destinationsBottom tab barmobile-navigation-patterns.md
Mobile, more than 5Drawer or hamburgermobile-navigation-patterns.md
Showing position in a hierarchyBreadcrumbssecondary-navigation-patterns.md
Switching views of one objectTabs, segmented controlsecondary-navigation-patterns.md
Long result setsPaginationsecondary-navigation-patterns.md
Linear multi-step processSteppersecondary-navigation-patterns.md
Any of the above, made accessible—navigation-accessibility.md
Deciding the structure underneath—information-architecture.md

Reference architecture

FileCoversLines
references/primary-navigation-patterns.md27 primary patterns with TSX1822
references/secondary-navigation-patterns.md22 secondary patterns1339
references/mobile-navigation-patterns.mdmobile-specific patterns1146
references/navigation-accessibility.mdARIA, keyboard, focus1046
references/information-architecture.mdIA methods, taxonomy, URLs861

What every reference file contains

  1. Anatomy — the structural parts and what each is called
  2. When to use it, and the condition that rules it out
  3. Complete React/TSX plus CSS, runnable, no placeholders
  4. The responsive transformation at each breakpoint
  5. ARIA roles, keyboard map, and focus order
  6. Anti-patterns specific to that pattern

Routing

For primary navigation — 27 patterns with specs and TSX, including top bar, mega menu, centered logo, integrated search, sidebar and command palette: read references/primary-navigation-patterns.md.

For secondary navigation — breadcrumbs (simple, dropdown, truncated), tabs, segmented controls, pagination and steppers: read references/secondary-navigation-patterns.md.

For mobile — bottom tab bar (iOS), bottom navigation (Material 3), hamburger and drawer variants, and the gesture patterns around them: read references/mobile-navigation-patterns.md.

For making it accessible — ARIA landmarks, skip navigation, current-page indication, expanded/collapsed state, and focus management: read references/navigation-accessibility.md.

For structuring the content underneath — IA research methods, IA structures, labeling and taxonomy, sitemap design and URL structure: read references/information-architecture.md.

For odds and ends — the patterns that had no home in the files above when this skill was converted to a router: read references/navigation-supplementary.md.

Cross-References

  • mobile-ux-design — iOS and Android navigation deep dives
  • desktop-app-design — Desktop navigation conventions
  • layout-block-intelligence — Header/nav block patterns and layout integration
  • accessibility-inclusive-design — Full WCAG navigation requirements
  • screen-flow-patterns — User flow patterns that connect to navigation
  • component-patterns-code — Production code for nav components
  • interaction-motion-design — Navigation transition animations
  • responsive-block-patterns — Responsive transformation specs

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.