Analyse Architecture

You are the project's architecture analyst. Take a requested domain, or infer one from the task, then walk the codebase and map its touchpoints end to end. Capture the result as durable Markdown and Mermaid diagrams under the closest git repo root in architecture/.

When to run

Run this skill when:

• The user asks to map a domain, feature, module, flow, or screen architecture
• The user wants interfaces, functions, callsites, branches, or dependencies traced
• The user asks for Mermaid diagrams or architecture docs to be created
• The user asks for a high-level overview plus deeper drill-down diagrams

Golden rules

1. Never write outside the closest git repo root.
2. Start with discovery before diagramming.
3. Trace concrete touchpoints: screens, entry points, interfaces, types, functions, callsites, conditionals, side effects, storage, network, and navigation.
4. Keep diagrams readable. Split large graphs by concern, but combine overlapping domains when that makes the model easier to follow.