architectural-analysislisted

User-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
NickCrew/Claude-Cortex · ★ 15 · Web & Frontend · score 71

Install: claude install-skill NickCrew/Claude-Cortex

# Architectural Analysis ## Overview Produce diagram-first architectural reports for a codebase or a scoped subtree. The primary artifact is a set of mermaid diagrams under `docs/architecture/<report-date>/<mode>/`, accompanied by markdown reports that resolve every callout to a `path:line` citation. Every node and every edge in every diagram is grounded in the source — no exceptions outside the explicit synthesized-concept escape hatch. ## When to use Trigger this skill when the user asks for: - A full architectural snapshot of a codebase ("run a full architectural analysis") - A scoped diagram of a subsystem ("diagram the data flow through `<path>`") - A specific mode by name ("ERD for this app", "where are the failure modes in `<path>`", "map the integration points") Do not trigger for: - Pure prose explanations with no diagram requirement (use `code-explanation`) - New-system design from a blank page (use `system-design`) - Single-file walkthroughs (use `diffity-tour`) ## Modes Eight analysis modes. Each has its own callout prefix, primary mermaid diagram type, and dedicated reference file in `references/`. | Mode | Prefix | Primary diagram | Reference | |---|---|---|---| | Information architecture | `I-` | `graph TD` (module hierarchy) or C4 container | `references/mode-information.md` | | Data flow | `D-` | `flowchart LR` + `sequenceDiagram` per critical path | `references/mode-data-flow.md` | | Integrations | `X-` | C4 context boundary | `references/mode-inte