nexus-architecturelisted

# Nexus Architecture Mapper Map internal structure, identify bounded contexts, score coupling, and produce an extraction plan or deployment safety verdict. --- ## Compatibility - Sub-skills: `skills/architecture/deployment-safety.md` - Supporting files: `checklists/architecture-checklist.md`, `heuristics/architecture-heuristics.md`, `anti-patterns/common-mistakes.md`, `validation/output-validation.md` - Required tools: Read, Grep, Glob, Bash - Output: Mermaid C4 diagram + coupling matrix + extraction candidates + risk assessment - Hands off to: `nexus:planning` when user approves extraction plan --- ## Routing | User Intent | Track | |-------------|-------| | "Map this codebase", "what calls what", "bounded contexts", "architecture review" | Architecture Mapping (Steps 1–5) | | "Is this deployment safe", "what breaks if I deploy", "pre-deployment check" | Route to `deployment-safety.md` | | Both | Run Architecture Mapping first, then deployment-safety.md | --- ## Context Acquisition | Signal | Where to look | |--------|--------------| | Directory structure | `find . -type d -not -path '*/.*' -not -path '*/node_modules/*' -not -path '*/__pycache__/*'` | | Entry points | Main application bootstrap files (e.g. `main.*`, `app.*`, `server.*`, `index.*`) | | Import graph | Language-appropriate grep for import/require statements across source files | | API surface | Route/handler definitions — look for patterns matching the framework's routing convention | | Database schema