Agent skill · design visual · aiskillstore
c4-architecture
Generate architecture documentation using C4 model Mermaid diagrams. Use when asked to create architecture diagrams, document system architecture, visualize software structure, create C4 diagrams, or generate context/container/component/deployment diagrams. Triggers include "architecture diagram", "C4 diagram", "system context", "container diagram", "component diagram", "deployment diagram", "document architecture", "visualize architecture".
Why this skill is useful
Generates specific C4 model diagrams in Mermaid syntax that the AI wouldn't reliably create on its own.
What it needs
About 5k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
C4 Architecture Documentation Generate software architecture documentation using C4 model diagrams in Mermaid syntax. Workflow 1. Understand scope - Determine which C4 level(s) are needed based on audience 2. Analyze codebase - Explore the system to identify components, containers, and relationships 3. Generate diagrams - Create Mermaid C4 diagrams at appropriate abstraction levels 4. Document - Write diagrams to markdown files with explanatory context C4 Diagram Levels Select the appropriate level based on the documentation need: Level Diagram Type Audience Shows When to Create ------- ------------- ---------- ------- ---------------- 1 C4Context Everyone System + external actors Always (required) 2 C4Container Technical Apps, databases, services Always (required) 3 C4Component Developers Internal components Only if adds value 4 C4Deployment DevOps Infrastructure nodes For production systems - C4Dynamic Technical Request flows (numbered) For complex workflows Key Insight: "Context + Container diagrams are sufficient for most software development teams." Only create Component/Code diagrams when they genuinely add value. Quick Start Examples System Context (Level 1) Container Diagram (Level 2) Component Diagram (Level 3) Dynamic Diagram (Request Flow) Deployment Diagram Element Syntax People and Systems Containers Components Boundaries Relationships Deployment Nodes Styling and Layout Layout Configuration $c4ShapeInRow - Number of shapes per row (default: 4) $c4BoundaryInRow - Number of boundaries per row (default: 2) Element Styling Relationship Styling Use $offsetX and $offsetY to fix overlapping relationship labels. Best Practices Essential Rules 1. Every element must have: Name, Type, Technology (where applicable), and Description 2. Use unidirectional arrows only - Bidirectional arrows create ambiguity 3. Label arrows with action verbs - "Sends email using", "Reads from", not just "uses" 4. Include technology labels - "JSON/HTTPS", "JDBC", "gRPC" 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/c4-architecture