본문으로 건너뛰기
cccskills
무료GitHub에 공개

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(1)

  • SKILL.md4.1 KB

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

SituationRecommended pattern
Mobile, 3–5 primary destinationsTab bar
Desktop app, many destinations or nested structureSide navigation
Simple marketing site or docsTop nav bar
Deep content hierarchyBreadcrumbs + local sidebar
Parallel views of the same contentTabs or segmented control
Occasional, non-primary accessUtility 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

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Owl-Listener/designer-skills3천2026년 9월 6일 업데이트

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Owl-Listener/designer-skills3천2026년 9월 6일 업데이트

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Owl-Listener/designer-skills3천2026년 9월 6일 업데이트

Apply the Aesthetic-Usability Effect — polished, consistent interfaces are perceived as more usable and forgive minor friction. Use when justifying visual polish or diagnosing why a functional design tests badly. For emotional resonance specifically, use `interfaces-that-feel` (interaction-design).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Owl-Listener/designer-skills3천2026년 9월 6일 업데이트

Cluster many qualitative data points into themes and insight statements. Use when synthesising across multiple sessions or sources. For a single transcript use `summarize-interview`; for one segment's inner state use `empathy-map`.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Owl-Listener/designer-skills3천2026년 9월 6일 업데이트

Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use `motion-system` (design-systems); for a full interaction spec use `micro-interaction-spec`.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Owl-Listener/designer-skills3천2026년 9월 6일 업데이트

Owl-Listener의 스킬 모두 보기

이 스킬의 문제 신고