c4-architecture

Generate software architecture documentation using C4 model Mermaid diagrams. 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: - Supports all four C4 levels: System Context, Container, Component, and Deployment diagrams, plus Dynamic diagrams for request flows - Includes syntax and examples for people, systems, containers, components, boundaries, and relationships with directional and styling options - Provides microservices modeling guidance for single-team and multi-team ownership, plus event-driven architecture patterns - Recommends audience-appropriate diagram selection and best practices like staying under 20 elements per diagram and using unidirectional arrows - Understand scope - Determine which C4 level(s)...