Implementing Navigation logo

Implementing Navigation

Community
ancoleman
implementing-navigation

Implements navigation patterns and routing for both frontend (React/TS) and backend (Python) including menus, tabs, breadcrumbs, client-side routing, and server-side route configuration. Use when building navigation systems or setting up routing.

Overview

Publisherancoleman
Repositoryai-design-components
Skill nameimplementing-navigation
Stars
523
Forks
73
Bundled files
20
LicenseMIT
Links
  • 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.

  • 20 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

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

Installation

Install the Implementing Navigation 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.
  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/ancoleman/ai-design-components.git /tmp/ai-design-components
mkdir -p .claude/skills
cp -r /tmp/ai-design-components/skills/implementing-navigation .claude/skills/implementing-navigation
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Implementing Navigation 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 Implementing Navigation 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 Implementing Navigation 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 Patterns & Routing Implementation

Purpose

This skill provides comprehensive guidance for implementing navigation systems across both frontend and backend applications. It covers client-side navigation patterns (menus, tabs, breadcrumbs) and routing (React Router, Next.js) as well as server-side route configuration (Flask, Django, FastAPI).

When to Use

Use this skill when:

  • Building primary navigation (top, side, mega menus)
  • Implementing secondary navigation (breadcrumbs, tabs, pagination)
  • Setting up client-side routing (React Router, Next.js)
  • Configuring server-side routes (Flask, Django, FastAPI)
  • Creating mobile navigation patterns (hamburger, bottom nav)
  • Implementing keyboard-accessible navigation
  • Building command palettes or search-driven navigation
  • Creating multi-step wizards or steppers
  • Ensuring WCAG 2.1 AA compliance for navigation

Navigation Decision Framework

Information Architecture → Navigation Pattern

Flat (1-2 levels)      → Top Navigation
Deep (3+ levels)       → Side Navigation
E-commerce/Large       → Mega Menu
Linear Process         → Stepper/Wizard
Long Content          → Table of Contents
Power Users           → Command Palette
Multi-section Page    → Tabs
Large Data Sets       → Pagination

Frontend Navigation Components

Primary Navigation Patterns

Top Navigation (Horizontal)

  • Best for shallow hierarchies, marketing sites
  • 5-7 primary links maximum for cognitive load
  • See references/menu-patterns.md for implementation

Side Navigation (Vertical)

  • Best for deep hierarchies, admin panels, dashboards
  • Supports multi-level nesting and collapsible sections
  • See references/menu-patterns.md for sidebar patterns

Mega Menu

  • Best for e-commerce, content-heavy sites
  • Rich content with images and descriptions
  • See references/menu-patterns.md for mega menu structure

Secondary Navigation Components

Breadcrumbs

  • Shows hierarchical path and current location
  • Essential for deep sites and e-commerce
  • See references/navigation-components.md for breadcrumb patterns

Tabs

  • Content switching without page reload
  • URL synchronization for bookmarking
  • See references/navigation-components.md for tab implementation

Pagination

  • For search results, product lists, articles
  • Consider virtualization for performance
  • See references/navigation-components.md for pagination patterns

Client-Side Routing

React Router (Industry Standard)

  • Type-safe routing with loader patterns
  • Nested routes and lazy loading support
  • See references/client-routing.md for React Router patterns

Next.js App Router

  • File-based routing with RSC support
  • Parallel and intercepting routes
  • See references/client-routing.md for Next.js routing

Backend Routing Patterns

Python Web Frameworks

Flask

  • Blueprint-based organization
  • Route decorators and URL rules
  • See references/flask-routing.md for Flask patterns

Django

  • URL configuration with namespaces
  • Path converters and regex patterns
  • See references/django-urls.md for Django URL conf

FastAPI

  • Router-based organization
  • Path operations and dependencies
  • See references/fastapi-routing.md for FastAPI routers

Mobile Navigation

Patterns for Touch Devices

Hamburger Menu

  • Slide-out drawer for primary navigation
  • See references/menu-patterns.md for mobile drawer

Bottom Navigation

  • 3-5 primary actions, thumb-friendly
  • See references/menu-patterns.md for bottom nav

Tab Bar

  • Horizontal scrollable tabs with swipe
  • Natural for mobile-first applications

Accessibility Requirements

Keyboard Navigation

Tab       → Move forward through links
Shift+Tab → Move backward through links
Enter     → Activate link/button
Space     → Activate button
Arrow keys → Navigate within menus
Escape    → Close dropdowns/modals

ARIA Patterns

Essential ARIA attributes for accessible navigation:

  • See references/accessibility-navigation.md for complete ARIA patterns
  • Includes landmark roles, states, and properties
  • Screen reader optimization techniques

Focus Management

  • Visible focus indicators (2px minimum, 3:1 contrast)
  • Focus trap for modals and dropdowns
  • Skip navigation link for keyboard users
  • See references/accessibility-navigation.md for focus patterns

Implementation Utilities

Navigation Structure Management

Generate and validate navigation trees:

bash
# Validate navigation structure
node scripts/validate_navigation_tree.js nav-config.json

# Generate breadcrumb trails
node scripts/calculate_breadcrumbs.js current-path

Route Generation (Python)

Generate route configurations:

bash
# Generate Flask/Django/FastAPI routes
python scripts/generate_routes.py --framework flask --config routes.yaml

Code Examples

Frontend Examples

For working navigation implementations:

  • examples/horizontal-menu.tsx - Responsive top navigation
  • examples/tab-navigation.tsx - Tabs with URL sync
  • examples/mobile-navigation.tsx - Hamburger and drawer

Backend Examples

For routing configuration:

  • examples/flask_routes.py - Flask blueprint setup
  • examples/django_urls.py - Django URL patterns
  • examples/fastapi_routes.py - FastAPI router organization

Navigation Configuration

For complex navigation structures, use the configuration schema:

  • assets/navigation-config-schema.json - Navigation tree schema
  • assets/route-templates.json - Common route patterns

Validate configurations before implementation using the validation script.

Library Recommendations

Frontend Routing

React Router is the recommended solution for React applications:

  • Industry standard with excellent TypeScript support
  • Built-in accessibility with NavLink active states
  • See references/library-comparison.md for alternatives

Component Libraries

For rapid development, consider:

  • Headless UI libraries (Radix UI, React Aria)
  • Accessible by default
  • Work with any styling approach

Progressive Enhancement

Build navigation that works without JavaScript:

  • Server-rendered HTML navigation
  • Progressive enhancement with client-side routing
  • Fallback for JavaScript failures

Performance Considerations

  • Lazy load route components
  • Prefetch navigation targets
  • Use route-based code splitting
  • Implement loading states for navigation

Testing Navigation

Essential navigation tests:

  • Keyboard navigation flow
  • Screen reader announcements
  • Mobile touch interactions
  • Route parameter validation
  • Deep linking functionality

Next Steps

  1. Analyze the information architecture
  2. Select appropriate navigation pattern
  3. Implement with accessibility first
  4. Add progressive enhancement
  5. Test across devices and assistive technologies

For detailed implementation guides, explore the referenced documentation files based on specific requirements.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Implementing Navigation AI skill do?

Implements navigation patterns and routing for both frontend (React/TS) and backend (Python) including menus, tabs, breadcrumbs, client-side routing, and server-side route configuration. Use when building navigation systems or setting up routing.

Why use Implementing Navigation on TypingMind?

Because you install it once and use it with any model. Implementing Navigation 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 Implementing Navigation in TypingMind?

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

Which AI models can use Implementing Navigation?

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 Implementing Navigation?

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

Is the Implementing Navigation AI skill free?

Yes. It is published on GitHub by ancoleman 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.

View all

Set up your own AI workspace now

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