메뉴
Detect and analyze infrastructure components — Prisma models, env vars, queues, crons, deploy configs, field usage, and type validation
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 scan architecture, check dependencies, find outdated packages, show project structure, refresh architecture, or run a health check. Navgator scan, status, and staleness check.
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.
Use when user asks to install navgator, update navgator, set up navgator, launch the dashboard, or run navgator ui maintenance.
| name | infrastructure-scanning |
| description | Detect and analyze infrastructure components — Prisma models, env vars, queues, crons, deploy configs, field usage, and type validation |
| version | 0.9.1 |
| user-invocable | false |
NavGator detects infrastructure components beyond packages and services.
| Command | What it does |
|---|---|
navgator scan | Detect all infrastructure (Prisma, env vars, queues, crons, deploy) |
navgator scan --field-usage | Analyze which Prisma model fields are actually used in code |
navgator scan --typespec | Compare Prisma model types against TypeScript interfaces |
navgator coverage --fields | Standalone field usage report |
navgator coverage --typespec | Standalone type validation report |
navgator status | Shows INFRASTRUCTURE and RUNTIME TOPOLOGY sections with counts |
Prisma — Models, fields, relations, indexes, table mappings. Field usage analysis identifies unused, read-only, and write-only fields across the codebase.
Environment Variables — From .env files and process.env references. Categorized as database, auth, api-key, service, infra, or app-config.
Queues — BullMQ/Bull queue definitions with producer/consumer topology and concurrency settings.
Cron Jobs — From vercel.json, railway.json, and node-cron patterns with human-readable schedule descriptions.
Deploy Configs — Vercel, Railway, Heroku, Procfile, and nixpacks configurations with service definitions.
TypeSpec Validation — Compares Prisma model field types against TypeScript interface definitions, flagging mismatches (e.g., DateTime vs string instead of Date).
Runtime Topology — Annotates components with runtime identity extracted from code and config:
DATABASE_URL and Prisma datasource blocksRun navgator status to see the RUNTIME TOPOLOGY section. Enables backward tracing: "which code produces to queue X?" or "what database engine does this schema connect to?"