Architecture Diagram
Use this built-in skill when the user needs a system, data-flow, or component diagram that should stay faithful to the real implementation.
Core rules
- Start from the actual repo, API contract, or product behavior before drawing.
- Pick the simplest editable format that fits the request: Mermaid, SVG, or code-native graphics.
- Keep labels sparse and information hierarchy obvious.
- Optimize for explanation, not visual noise.
Default workflow
- Identify the audience and the level of abstraction.
- Extract the canonical components, boundaries, and flows.
- Produce one clear diagram with consistent naming and direction.
- Verify that the diagram matches the implementation or stated architecture.
Guardrails
- Do not invent systems or edges that are not grounded in source truth.
- Do not overload one frame with too many concepts.
- Do not hide uncertainty; mark assumptions when architecture is inferred.
