design-navigation
Design navigation architecture including menus, breadcrumbs, and mega-menus. Generates structured navigation with accessibility.
What this skill does
# Design Navigation Command
Design a comprehensive navigation system with menus, breadcrumbs, and navigation APIs.
## Usage
```bash
/cms:design-navigation --type primary
/cms:design-navigation --type mega --format json
/cms:design-navigation --type all
```
## Navigation Types
- **primary**: Main site navigation
- **footer**: Footer link structure
- **mega**: Multi-column dropdown menus
- **breadcrumb**: Hierarchical path navigation
- **all**: Complete navigation system
## Workflow
### Step 1: Parse Arguments
Extract navigation type and output format from command.
### Step 2: Gather Requirements
Use AskUserQuestion to understand:
- What is the site's primary structure?
- How deep should navigation go?
- Are there mega-menu requirements?
- What mobile patterns should be used?
### Step 3: Invoke Skills
Invoke relevant skills for analysis:
- `navigation-architecture` - Navigation patterns
- `page-structure-design` - Page hierarchy
- `url-routing-patterns` - URL structure
### Step 4: Generate Navigation Design
**Primary Navigation:**
```yaml
navigation:
name: MainNav
type: primary
max_depth: 2
items:
- label: Home
url: /
icon: home
- label: Products
url: /products
children:
- label: All Products
url: /products
- label: Categories
url: /products/categories
- label: New Arrivals
url: /products/new
- label: About
url: /about
children:
- label: Our Story
url: /about/story
- label: Team
url: /about/team
- label: Careers
url: /about/careers
- label: Contact
url: /contact
settings:
mobile_breakpoint: 768
mobile_pattern: hamburger
sticky: true
transparent_on_home: true
```
**Mega Menu:**
```yaml
mega_menu:
name: ProductsMega
trigger: Products
layout: columns
columns:
- heading: Shop by Category
items:
- label: Electronics
url: /products/electronics
image: /images/nav/electronics.jpg
- label: Clothing
url: /products/clothing
image: /images/nav/clothing.jpg
- label: Home & Garden
url: /products/home-garden
- heading: Featured
items:
- label: Best Sellers
url: /products/best-sellers
badge: Popular
- label: Sale Items
url: /products/sale
badge: Up to 50% off
- heading: Quick Links
items:
- label: Gift Cards
url: /gift-cards
- label: Store Locator
url: /stores
promo:
title: Summer Sale
description: Up to 50% off selected items
image: /images/promo/summer-sale.jpg
url: /products/sale
cta: Shop Now
```
**Breadcrumb Configuration:**
```yaml
breadcrumbs:
separator: /
show_home: true
home_label: Home
show_current: true
max_length: 5
truncate_middle: true
schema:
enabled: true
type: BreadcrumbList
patterns:
- path: /products/:category/:product
template:
- label: Home
url: /
- label: Products
url: /products
- label: "{category.name}"
url: /products/{category.slug}
- label: "{product.name}"
url: null # Current page
- path: /blog/:year/:month/:slug
template:
- label: Home
url: /
- label: Blog
url: /blog
- label: "{year}"
url: /blog/{year}
- label: "{post.title}"
url: null
```
### Step 5: Generate Implementation
Provide EF Core model for navigation:
```csharp
public class NavigationMenu
{
public Guid Id { get; set; }
public string Name { get; set; }
public string Type { get; set; } // primary, footer, mega
public List<NavigationItem> Items { get; set; }
public NavigationSettings Settings { get; set; }
}
public class NavigationItem
{
public Guid Id { get; set; }
public string Label { get; set; }
public string Url { get; set; }
public string Icon { get; set; }
public string Target { get; set; }
public int SortOrder { get; set; }
public Guid? ParentId { get; set; }
public List<NavigationItem> Children { get; set; }
public bool IsVisible { get; set; }
public string[] Roles { get; set; } // Role-based visibility
}
public class NavigationSettings
{
public int MobileBreakpoint { get; set; }
public string MobilePattern { get; set; }
public bool Sticky { get; set; }
public bool TransparentOnHome { get; set; }
}
```
### Step 6: Generate API Endpoint
```csharp
// GET /api/navigation/{name}
[HttpGet("{name}")]
public async Task<ActionResult<NavigationDto>> GetNavigation(
string name,
[FromQuery] string locale = "en")
{
var navigation = await _navigationService
.GetByNameAsync(name, locale);
if (navigation == null)
return NotFound();
return Ok(navigation);
}
// Response structure
public class NavigationDto
{
public string Name { get; set; }
public string Type { get; set; }
public List<NavigationItemDto> Items { get; set; }
}
public class NavigationItemDto
{
public string Label { get; set; }
public string Url { get; set; }
public string Icon { get; set; }
public string Target { get; set; }
public bool IsActive { get; set; }
public List<NavigationItemDto> Children { get; set; }
}
```
## Accessibility Requirements
Navigation must meet WCAG 2.1 AA:
| Requirement | Implementation |
|-------------|----------------|
| Keyboard Navigation | Tab order, arrow keys, Enter/Space |
| ARIA Labels | `aria-label`, `aria-expanded`, `aria-current` |
| Focus Management | Visible focus indicators |
| Skip Links | "Skip to main content" link |
| Mobile Touch | Touch target minimum 44x44px |
## Related Skills
- `navigation-architecture` - Navigation patterns
- `page-structure-design` - Page hierarchy
- `url-routing-patterns` - URL patterns
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.