arch-diagram
Use when the user wants evidence-grounded Mermaid architecture or UML diagrams for a codebase or system, including context, container, component, code, sequence, state-machine, or deployment diagrams. Trigger on “画架构图”, “画 C4 图”, “生成时序图”, “状态机图”, “部署图”, “组件依赖图”, “diagram this codebase”, or “draw a sequence or deployment diagram”. Follow the fact-first flow: define scope, acquire L0–L3 source evidence, select high-value diagram types, draft Mermaid, then validate and repair. Every node and edge must trace to file and line evidence; never fabricate architecture. Output Mermaid source in text fences with Name and Slug metadata. Do not use for learning materials or generic prose explanations.
Pinned to revision 8f0e044a5934, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/arch-diagram/SKILL.md
- skills/arch-diagram/agents/openai.yaml
- skills/arch-diagram/references/architecture-methodology.md
- skills/arch-diagram/references/code-diagram.md
- skills/arch-diagram/references/component-diagram.md
- skills/arch-diagram/references/container-diagram.md
- skills/arch-diagram/references/context-diagram.md
- skills/arch-diagram/references/deployment-diagram.md
- skills/arch-diagram/references/domain-acquisition.md
- skills/arch-diagram/references/sequence-diagram.md
- skills/arch-diagram/references/state-machine-diagram.md
- skills/arch-diagram/scripts/validate_diagram.py
Every link opens the file at its source, pinned to the revision this page describes.