From navgator
Detect and analyze infrastructure components — Prisma models, env vars, queues, crons, deploy configs, field usage, and type validation
How this skill is triggered — by the user, by Claude, or both
Slash command
/navgator:infrastructure-scanningThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
NavGator detects infrastructure components beyond packages and services.
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?"
Guides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.
Dispatches multiple subagents concurrently for independent tasks without shared state. Use when facing 2+ unrelated failures or subsystems that can be investigated in parallel.
npx claudepluginhub tyroneross/navgator --plugin navgator