TypingMindTypingMindThe best frontend for AI
Navigation Design logo

Navigation Design

Community
flitzrrr
navigation-design

Menu patterns, breadcrumbs, search functionality, information architecture, and user flow. Navigation as the backbone of every website with accessible implementation.

Overview

Publisherflitzrrr
Repositoryfrontend-design-skills
Skill namenavigation-design
Stars
9
Forks
2
Bundled files
Instructions only
LicenseMIT
Links
Skill sourceRepository
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by flitzrrr on GitHub. Read the source before you install it.

Installation

Install the Navigation Design AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/flitzrrr/frontend-design-skills/tree/main/skills-src/navigation-design
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/flitzrrr/frontend-design-skills.git /tmp/frontend-design-skills
mkdir -p .claude/skills
cp -r /tmp/frontend-design-skills/skills-src/navigation-design .claude/skills/navigation-design
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Navigation Design in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Navigation Design on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Navigation Design is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Navigation Design

Navigation is the table of contents of a website. It shows users at all times where they are, where they can go, and how to get back.

Scope

Use this skill when you:

  • Design or review a navigation structure
  • Select menu patterns for a specific website type
  • Design breadcrumbs, meta navigation, or footer navigation
  • Integrate a search function
  • Translate information architecture into navigation
  • Need to ensure accessible navigation

Principles

1. Navigation Is Orientation

Navigation shows users at all times where they are, where they can go, and how to get back. It is the table of contents of the website.

2. Information Architecture Before Navigation

Structure the content first, then derive the navigation from it. Never the other way around.

3. Clarity Over Creativity

When naming navigation items, clarity takes precedence over originality. Users must be able to predict what lies behind a link.

4. Visibility on Large Screens

Never hide the navigation on desktop. The hamburger menu is a mobile pattern, not a universal pattern.

5. 3-Click Rule as a Guideline

Users should be able to reach any important information in a maximum of 3 clicks. Not as a dogma, but as a design benchmark.

Rules

DO: Structure the Main Navigation Clearly

  • LIMIT the main navigation to 5-7 items.
  • PLACE the most important links at the beginning and end (Serial Position Effect).
  • START with the core offering, end with the primary CTA ("Contact", "Book a Demo").
  • USE a horizontal main navigation in the header as the default.

DO: Use Descriptive Menu Items

  • NAME menu items precisely (e.g., "WordPress Tutorials" instead of "Tutorials").
  • USE the language of the target audience, not internal jargon.
  • INTEGRATE relevant keywords for SEO.

DO: Offer Multiple Navigation Paths

  • COMBINE main navigation, meta navigation, footer navigation, and breadcrumbs.
  • PROVIDE a search function starting at approximately 100 subpages.
  • USE in-page links within the content area.
  • ADD a "back to top" button on long pages.

DO: Use Meta Navigation

  • PLACE meta navigation in the top-right of the header.
  • INCLUDE: search function, language selector, login, contact, legal notice.
  • KEEP the meta navigation identical across all pages.

DO: Use the Footer as Supplementary Navigation

  • REPEAT the most important links in the footer.
  • ADD secondary links (terms & conditions, privacy policy, sitemap, social media).
  • GROUP footer links thematically with clear headings.

DO: Use Breadcrumbs Correctly

  • USE breadcrumbs when there are more than 2 hierarchy levels.
  • START with a link to the homepage.
  • The current page is the last element and is not a link.
  • PLACE breadcrumbs directly below the global navigation.

DO: Implement Accessible Navigation

  • ENSURE full keyboard operability.
  • IMPLEMENT visible focus indicators.
  • USE a logical tab order and skip links.
  • SIZE touch targets to a minimum of 44x44px.
  • MAINTAIN minimum contrast of 4.5:1 for text, 3:1 for icons.

DON'T: Use Hamburger Menu on Desktop

  • ALWAYS show the full main navigation on large screens.
  • DO NOT hide navigation behind icons when sufficient space is available.

DON'T: Build Overly Deep Hierarchies

  • AVOID more than 3 navigation levels.
  • LIMIT dropdown menus to 2-3 levels.

DON'T: Hide Navigation Creatively

  • AVOID unconventional navigation positions.
  • DO NOT use icons without text labels for primary navigation items.

Patterns

Navigation Concept by Website Type

Website TypeRecommended Navigation
CorporateHorizontal main nav + footer + breadcrumbs
E-CommerceMega menu + search with filters + breadcrumbs
BlogMain nav + category/tag navigation + pagination
PortfolioMinimalist, category filters, subtle
Content PortalMulti-level + tags + robust search + breadcrumbs
One-PageScroll navigation + back-to-top button

Mega Menu

For e-commerce and large content portals. Full-width dropdown with multi-column layout, maximum 2-3 levels. Visual previews for categories, most important categories on the left (eye-tracking). For details, see references/navigation-patterns.md.

Sidebar Navigation

For web applications, dashboards, documentation sites. Vertical navigation on the left, collapsed to icons only, with full labels on hover/click.

Scroll Navigation (One-Page)

For portfolio sites, event landing pages. Navigation items scroll to the section, the active item highlights on scroll. "Back to top" button after a defined scroll depth.

Site Search

Starting at approximately 100 subpages. Search field in the header, highly visible. Autocomplete for large websites. Zero-results page with alternative suggestions.

Anti-Patterns

Generic Menu Item Labels

"Services", "Products", "More" without specification. Users cannot predict what to expect. Solution: Precise labels: "Web Design Packages", "WordPress Themes".

Too Many Menu Items

10+ items in the main navigation. Overwhelms users, slows decision-making. Solution: Maximum 7 items. Move secondary links to meta navigation or footer.

Icon-Only Navigation Without Labels

Icons are ambiguous. Not all users know icon conventions. Solution: Always combine icons with text labels, at minimum as a tooltip.

Dropdown on Hover for Touch Devices

Dropdown menus do not work on touch devices. Solution: Hover menus with toggle option. First tap opens, second tap navigates.

Broken Back Button Behavior

Browser back button does not function correctly (SPA routing errors). Solution: Implement the History API correctly.

Checklist

Structure

  • Information architecture developed before navigation
  • Maximum 5-7 main navigation items
  • Maximum 3 hierarchy levels
  • Most important links at the beginning and end

Naming

  • Menu items descriptive and in target audience language
  • Keywords integrated into menu items and URLs
  • Consistent naming across all pages

Elements

  • Logo linked to homepage (top-left)
  • Visible main navigation on desktop
  • Hamburger icon on mobile only
  • Meta navigation present
  • Footer navigation with grouped secondary links
  • Breadcrumbs for more than 2 levels
  • Search function for more than 100 subpages

Visual Feedback

  • Active menu item visually highlighted
  • Links recognizable as such
  • Visible focus indicator for keyboard navigation

Accessibility

  • Full keyboard operability
  • Skip links present
  • ARIA labels for navigation regions
  • Minimum contrast of 4.5:1 maintained
  • Touch targets at least 44x44px

Cross-References

  • usability -- Navigation as a core usability element
  • responsive-design -- Responsive navigation (hamburger, breakpoints)
  • accessibility -- Accessible navigation (WCAG, keyboard, ARIA)
  • ui-design -- Visual design of navigation elements
  • branding-identity -- Navigation as a brand touchpoint

Frequently asked questions

What does the Navigation Design AI skill do?

Menu patterns, breadcrumbs, search functionality, information architecture, and user flow. Navigation as the backbone of every website with accessible implementation.

Why use Navigation Design on TypingMind?

Because you install it once and use it with any model. Navigation Design is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Navigation Design in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/flitzrrr/frontend-design-skills/tree/main/skills-src/navigation-design. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Navigation Design?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Navigation Design?

As many as you like. As long as a model supports skills, you can use Navigation Design with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Navigation Design AI skill free?

Yes. It is published on GitHub by flitzrrr under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

Related AI Skills

View all
coreyhaines31 logo

Aso

coreyhaines31
CommunityPopular

When the user wants to audit or optimize an App Store or Google Play listing. Also use when the user mentions 'ASO audit,' 'app store optimization,' 'optimize my app listing,' 'improve app…

7.7K
50.7K
6 files
View
coreyhaines31 logo

Attribution

coreyhaines31
CommunityPopular

When the user wants to figure out which marketing actually drives conversions and revenue, choose or interpret an attribution model, or reconcile conflicting numbers across tools. Also use when the…

7.7K
50.7K
5 files
View
coreyhaines31 logo

Churn Prevention

coreyhaines31
CommunityPopular

When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,'…

7.7K
50.7K
3 files
View
coreyhaines31 logo

Co Marketing

coreyhaines31
CommunityPopular

When the user wants to find co-marketing partners, plan joint campaigns, or brainstorm partnership opportunities. Use when the user says 'co-marketing,' 'partner marketing,' 'joint campaign,' 'who…

7.7K
50.7K
2 files
View

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇