What problem does it solve? Designing a new system without clear requirements leads to over-engineered or fragile architectures. This Skill guides a structured architecture workflow: gathering functional and non-functional requirements, selecting the right architecture pattern, choosing data stores, planning for scale and failure, and documenting every significant decision as an Architecture Decision Record (ADR). ## Core Features & Use Cases - Requirements-Driven Design: Collects functional requirements, NFRs (performance, availability, security, cost), and constraints before any design work begins, using a structured NFR checklist. - Pattern & Database Selection: Matches requirements to architecture patterns (monolith, modular monolith, microservices, serverless, event-driven, CQRS) and database types (relational, document, key-value, time-series, graph, search) with explicit trade-off analysis. - ADR Documentation: Produces Architecture Decision Records for every significant choice, including alternatives considered and consequences. - Use Case: You are building an e-commerce platform and need to decide between a modular monolith and microservices, pick a primary database, and justify the choices to stakeholders. The Skill produces a full design document with component breakdown, scaling plan, failure modes, and ADRs. ## Quick Start Ask the agent to design the architecture for your system, for example: "Design the architecture for a multi-tenant SaaS billing platform expecting 10K concurrent users, and write ADRs for the database and messaging choices."
