diagrams
Installation
SKILL.md
Architecture Overview Diagrams
Create diagrams that show interactions and dependencies between components, groupings, and external services at a high level of abstraction. This skill routes the request: it detects the architecture, scope, and format, then delegates rendering to the mermaid or drawio skill, which owns the shape mapping and palette.
Workflow
- Detect the architecture — resolve which shape mapping applies:
- the user names it explicitly ("BCE diagram", "layered view", "feature map")
AGENTS.md## SDD4Jdeclares ansdd4j-*architecture adapter- codebase scan (see Information Gathering)
- still ambiguous → include it as an extra question in step 3
- Gather information — identify components, groupings, external services, and interactions to visualize, per the detected architecture.
- Choose scope and format — ask the user using a single AskUserQuestion call with two questions:
- Scope: "System view" (each component is a single opaque node — default) or "Inside a component" (expand one component's internal structure)
- Format: "Mermaid (Recommended)" (text-based, version-control friendly, renders natively in GitHub/GitLab — default for README.md in GitHub projects) or "draw.io" (visual editor, richer styling, exportable to PNG/SVG)
- Invoke the chosen skill — use the Skill tool to invoke
mermaidordrawiowith the detected architecture, scope, identified elements, and interactions. When the diagram is destined for a README.md in a GitHub project, default to Mermaid without asking.