From navgator
Use when user asks to show or generate an architecture diagram, visualize dependencies, export architecture docs, create architecture documentation, save architecture output, or create a mermaid diagram of their project.
How this skill is triggered — by the user, by Claude, or both
Slash command
/navgator:architecture-export [diagram|export] [options][diagram|export] [options]The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Generate architecture diagrams and export architecture summaries using the real NavGator MCP and CLI surfaces.
Generate architecture diagrams and export architecture summaries using the real NavGator MCP and CLI surfaces.
Before generating output, check whether architecture data exists. If the MCP tool or CLI reports missing data, run or recommend navgator scan first. Do not fabricate architecture from raw source when scan data is unavailable.
For in-chat diagrams, use the navgator diagram MCP tool.
MCP modes:
summary: top connected components only (default)focus: center on a specific component; pass focus: "<component-name>"layer: show one layer; pass focus: "<layer-name>" such as frontend, backend, database, queue, infra, or externalThe MCP tool returns Mermaid markdown that can be rendered in any Mermaid-compatible viewer.
For file output, use the CLI diagram command. NavGator does not have an export command.
# Raw Mermaid
npx @tyroneross/navgator diagram --summary --output architecture.mmd
# Markdown-wrapped Mermaid
npx @tyroneross/navgator diagram --summary --markdown --output ARCHITECTURE.md
# Focused component diagram
npx @tyroneross/navgator diagram --focus "component-name" --markdown --output component-architecture.md
# Layer diagram
npx @tyroneross/navgator diagram --layer backend --markdown --output backend-architecture.md
For an in-chat executive summary, use the navgator summary MCP tool.
For a JSON file, use the CLI summary command and shell redirection:
npx @tyroneross/navgator summary > architecture-summary.json
If the user asks for machine-readable graph data, point them to the generated scan artifacts rather than inventing an export command:
.navgator/architecture/index.json.navgator/architecture/graph.json.navgator/architecture/file_map.json| User Intent | Tool | Notes |
|---|---|---|
| "Show architecture diagram" | MCP navgator diagram | Summary mode |
| "Diagram of X component" | MCP navgator diagram with mode: "focus" | Component-focused |
| "Show backend layer" | MCP navgator diagram with mode: "layer" | Pass layer name as focus |
| "Save a Mermaid diagram" | CLI npx @tyroneross/navgator diagram --output <file> | Add --markdown for Markdown docs |
| "Export architecture summary" | CLI npx @tyroneross/navgator summary > <file>.json | JSON file output |
| "Architecture summary in chat" | MCP navgator summary | Executive summary |
| "Export full graph JSON" | Existing .navgator/architecture/*.json files | No CLI export command exists |
navgator export; that command is not registered.focus for complex diagrams so the output stays readable.navgator - architecture tracker
npx claudepluginhub tyroneross/navgator --plugin gatorOffers UI/UX design guidance for web and mobile with 50+ styles, 161 color palettes, 57 font pairings, and 99 UX guidelines across 10 stacks. Use for designing pages, components, color systems, or reviewing UI code.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.