c4-architecture

Generate software architecture documentation using C4 model diagrams in Mermaid syntax. Select the appropriate level based on the documentation need: Key Insight: "Context + Container diagrams are sufficient for most software development teams." Only create Component/Code diagrams when they genuinely add value. Use $offsetX and $offsetY to fix overlapping relationship labels. See references/common-mistakes.md for detailed anti-patterns: Model each microservice as a container (or container group): Promote microservices to software systems when owned by separate teams: Show individual topics/queues as containers, NOT a single "Kafka" box: Write architecture documentation to docs/architecture/ with naming convention: - Understand scope - Determine which C4 level(s) are needed based on audience - Analyze codebase - Explore the system to identify components, containers, and relationships - Generate diagrams - Create Mermaid C4 diagrams at appropriate abstraction levels - Document - Write diagrams to markdown files with explanatory context - $c4ShapeInRow - Number of shapes per row (default: 4) - $c4BoundaryInRow - Number of boundaries per row (default: 2) - Every element must have : Name, Type, Technology (where applicable), and Description - Use unidirectional arrows only - Bidirectional arrows create ambiguity - Label arrows with action verbs - "Sends email using", "Reads from",...