What problem does it solve? Choosing software architecture without a structured process leads to over-engineered systems, premature microservices, and undocumented decisions that teams later regret. This Skill provides a disciplined framework for gathering requirements, evaluating trade-offs, selecting patterns, and recording decisions as Architecture Decision Records (ADRs). ## Core Features & Use Cases - Context Discovery: A question hierarchy covering scale, team, timeline, domain, and constraints, plus a project classification matrix (MVP, SaaS, Enterprise) to calibrate architecture complexity. - Pattern Selection: Decision trees for data access, domain logic, distributed systems, and APIs, with red-flag anti-patterns and a simplicity-first principle. - Trade-off Analysis & ADRs: Templates for documenting options, rationale, accepted trade-offs, consequences, and revisit triggers, stored under docs/architecture/. - Use Case: A team starting a new SaaS product uses the classification matrix to choose a modular monolith over microservices, then writes an ADR capturing the rationale and the trigger conditions for extracting services later. ## Quick Start Ask the assistant to help design the architecture for your project by describing your expected scale, team size, timeline, and domain complexity.
