What problem does it solve? Choosing the right system architecture is hard: teams often pick trendy patterns without weighing tradeoffs against their actual constraints. This Skill guides structured architecture decision-making based on system requirements, producing a documented blueprint the whole team can reference. ## Core Features & Use Cases - Architecture Pattern Comparison: Compares Monolith, Modular Monolith, Microservices, Serverless, and Event-driven patterns with explicit tradeoffs across scalability, complexity, cost, and team capability. - Tech Stack & Infrastructure Decisions: Defines backend/frontend frameworks, database engines, cloud providers, CI/CD approach, and integration styles (REST/GraphQL/gRPC, sync/async messaging). - Blueprint Generation: Outputs an architecture-blueprint.md file covering component diagrams, data flow, and security boundaries, ready to hand off to the /database step. - Use Case: After running /analyze to gather system requirements, invoke this Skill to decide whether your project should use Microservices or a Modular Monolith, then receive a documented recommendation with 2-3 compared alternatives. ## Quick Start Run /architect with your system requirements from /analyze to compare architecture options and generate an architecture-blueprint.md file.
