Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From communication
Create C4 context, container, component, and code diagrams. Visualize architecture at different abstraction levels. Use when communicating system structure to diverse audiences.
npx claudepluginhub sethdford/claude-skills --plugin architect-communicationHow this skill is triggered — by the user, by Claude, or both
Slash command
/communication:c4-model-diagramThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Create C4 diagrams to communicate architecture at multiple abstraction levels.
Generates C4 model architecture diagrams and documentation using Mermaid syntax for system context, containers, components, and code levels.
Generates C4 models and Structurizr DSL workspaces from codebases for system context, container, component, and deployment diagrams; renders as images.
Reference for Mermaid syntax (flowchart, sequence, class, ER, state), C4 model levels, diagram types, and examples for technical diagrams.
Share bugs, ideas, or general feedback.
Create C4 diagrams to communicate architecture at multiple abstraction levels.
You are creating architecture diagrams. Use C4 model for consistent representation. Start at highest level (context), zoom in progressively (container, component, code). Read architecture decisions and system structure.
Based on Simon Brown's C4 model:
Draw Context Diagram: Rectangle for your system. External systems (payment provider, email service). Actors (user, admin). Label data flows. Answers "What does this system do?"
Draw Container Diagram: Inside system rectangle, show containers (web app, API, database, cache). Interfaces between containers. Technology choices (PostgreSQL, Redis). Answers "What technology?"
Draw Component Diagram: Pick one container (API). Inside, show components (auth service, payment service, order service). Responsibilities, communication patterns.
Draw Code Diagram: For complex component, show classes, methods. Use standard UML or pseudo-code. Limit to critical logic; don't over-document.
Keep Diagrams Current: As architecture evolves, update diagrams. Outdated diagrams mislead teams. Use tools (draw.io, Structurizr, Miro) that allow collaboration and versioning.