メニュー
Use when user asks to scan architecture, check dependencies, find outdated packages, show project structure, refresh architecture, or run a health check. Navgator scan, status, and staleness check.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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.
Use when user asks to review architecture, check connections, navgator review, is this safe to merge, what did I break, or when scan detects architectural drift. Architectural integrity review of system flow and connections.
Use when user asks what breaks if I change X, impact of changing, what depends on, trace data flow, show connections, dependency graph, upstream/downstream, or safe to modify before refactoring.
Detect and analyze infrastructure components — Prisma models, env vars, queues, crons, deploy configs, field usage, and type validation
Use when user asks to install navgator, update navgator, set up navgator, launch the dashboard, or run navgator ui maintenance.
| name | architecture-scan |
| description | Use when user asks to scan architecture, check dependencies, find outdated packages, show project structure, refresh architecture, or run a health check. Navgator scan, status, and staleness check. |
| version | 0.9.1 |
| user-invocable | false |
Scan project architecture, check health, and monitor staleness using NavGator MCP tools. This skill covers scanning, status display, and health checks.
npm install, pip install, or similar dependency operationsUse the navgator scan MCP tool to detect components, connections, AI prompts, and infrastructure.
Options:
quick: true: Package files only, skip code analysis (faster)After scanning, present a smart brevity brief:
Use the navgator status MCP tool to show architecture summary without re-scanning.
Returns: component counts by type/layer, connection counts, AI routing table, last scan timestamp, and staleness indicator.
If no architecture data exists, recommend running a scan first.
Use the navgator scan MCP tool with a follow-up review of the results. Health information is included in scan output:
| User Intent | MCP Tool | Notes |
|---|---|---|
| "Scan my project" | navgator scan | Full scan |
| "Quick scan" | navgator scan (quick: true) | Packages only |
| "What's my stack?" | navgator status | No re-scan needed |
| "Any outdated packages?" | navgator scan | Check health results |
| "Is architecture data fresh?" | navgator status | Check timestamp |
Keep output concise. Do NOT dump raw CLI output. Summarize into a scannable brief.
navgator — architecture tracker