AGENT SKILL

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).

License 许可
MIT
最近更新
2026-11-04
Stars
★ 0
Forks
0

01 前言 Front Matter

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).
disable-model-invocation
true

02 资源文件 3

03 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

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

04 同仓库更多 Skills

jorgesolerrr
jorgesolerrr/skills

explainroo

Make an explainer video (MP4) with a voice-over using explainroo. The voice is made on this computer and no API key is needed. Use when the user asks for an explainer, how-to, walkthrough, launch or tutorial video, an animated diagram with a voice-over, or a short for YouTube, Reels or TikTok.

★ 0
jorgesolerrr
jorgesolerrr/skills

unslop

Cut AI tells from prose a human will read. Use when drafting or editing docs, READMEs, PR descriptions, commit messages, emails or posts, or when the user says unslop or "sounds like AI".

★ 0
jorgesolerrr
jorgesolerrr/skills

technical-writing

Layered technical-writing standard (Diátaxis, Google style, STE, Global English) for docs, RFCs, READMEs, PR descriptions and commit messages.

★ 0
jorgesolerrr
jorgesolerrr/skills

no-comments

Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.

★ 0
jorgesolerrr
jorgesolerrr/skills

ponytail

Lazy senior dev mode: the smallest change that fully solves the task, and a reply a busy human understands in one read. Use on any coding task (writing, fixing, refactoring, reviewing, choosing dependencies) and when the user says "ponytail", "be lazy", "simplest solution", "yagni", or complains about over-engineering or bloat. Levels: lite, full (default), ultra.

★ 0
jorgesolerrr
jorgesolerrr/skills

ponytail-review

Quality review of a change: is the logic right, is it safe, does it hold under real load, is risky code tested, is it fast enough, and is every line needed. Reads the connected code, not only the diff. Each finding is explained in plain English. Use for "review this", "code review", "review the last commit", "review my PR", "is this over-engineered", /ponytail-review.

★ 0