What problem does it solve? Choosing the wrong system architecture leads to over-engineered systems, scaling bottlenecks, and teams unable to maintain their codebase. This Skill provides a structured decision workflow for selecting the right architecture pattern based on actual requirements. ## Core Features & Use Cases - Pattern Comparison: Side-by-side trade-off tables for monolith vs microservices, layered architecture, event-driven systems, and CQRS. - Phased Decision Workflow: A three-phase checklist covering requirements analysis, complexity assessment, and pattern selection with verification checkpoints. - Scope Disambiguation: Clear boundary rules distinguishing system architecture decisions from UI/UX design patterns. - Use Case: A startup team debating whether to split their growing application into microservices can follow the workflow to determine that a modular monolith fits their team size and scale, avoiding a distributed monolith. ## Quick Start Ask the agent to evaluate whether your project should use a monolith or microservices architecture given your team size and scaling requirements.