Skip to content
cccskills
FreePublished on GitHub

navigation-patterns

Select and design navigation patterns that match product structure, user tasks, and platform conventions.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md3.9 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Design rigorous A/B tests with hypotheses, variants, metrics, and sample size calculations.

The English summary is being prepared. Showing the original description.

Infrasity-Labs/dev-gtm-claude-skills142Updated Jun 29, 2026

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro.

The English summary is being prepared. Showing the original description.

Infrasity-Labs/dev-gtm-claude-skills142Updated Jun 29, 2026

Format CVs for academic positions with publications, grants, and teaching

The English summary is being prepared. Showing the original description.

Infrasity-Labs/dev-gtm-claude-skills142Updated Jun 29, 2026

Conduct a comprehensive accessibility audit against WCAG guidelines with severity ratings and remediation steps.

The English summary is being prepared. Showing the original description.

Infrasity-Labs/dev-gtm-claude-skills142Updated Jun 29, 2026

Create accessibility testing plans covering assistive technologies and WCAG criteria.

The English summary is being prepared. Showing the original description.

Infrasity-Labs/dev-gtm-claude-skills142Updated Jun 29, 2026

When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising platform. Also use when the user mentions 'ad copy variations,' 'ad creative,' 'generate headlines,' 'RSA headlines,' 'bulk ad copy,' 'ad iterations,' 'creative testing,' 'ad performance optimization,' 'write me some ads,' 'Facebook ad copy,' 'Google ad headlines,' 'LinkedIn ad text,' or 'I need more ad variations.' Use this whenever someone needs to produce ad copy at scale or iterate on existing ads. For campaign strategy and targeting, see ads. For landing page copy, see copywriting.

The English summary is being prepared. Showing the original description.

Infrasity-Labs/dev-gtm-claude-skills142Updated Jun 29, 2026

See all skills by Infrasity-Labs

Report a problem with this skill