What problem does it solve? Teams often start coding before defining system boundaries, leading to tangled services, duplicated business rules, and undocumented decisions. This Skill forces structural thinking first: it produces C4 diagrams, Architecture Decision Records, data-flow audits, and failure mode registries before any implementation begins. ## Core Features & Use Cases - System Design with C4 Models: Generates Level 1 Context and Level 2 Container diagrams (Mermaid or ASCII) so a new developer can understand system topology in minutes. - Architecture Decision Records: Records every major stack, database, or framework choice in a standardized ADR template capturing context, alternatives, and consequences. - Data-Flow and Drift Audits: Traces business rules across layers, flags rules duplicated in multiple places, and produces a drift-risk ranking with a single-source-of-truth recommendation. - Failure Mode Registry: Maps every codepath through Happy, Nil, Empty, and Error paths to eliminate silent failures before they reach production. - Use Case: When decomposing a monolith into services, use this Skill to draw the target container diagram, define bounded contexts with ubiquitous language, and write ADRs for each service boundary decision. ## Quick Start Ask the architect to design the system architecture for your multi-tenant SaaS app, producing C4 context and container diagrams plus an ADR for the decomposition decision.
