What problem does it solve? Teams often start coding significant features without validating whether the chosen stack, patterns, and infrastructure will scale, leading to costly rewrites, security gaps, and undocumented decisions. This Skill performs a structured architecture review before development starts and records every significant decision as an ADR. ## Core Features & Use Cases - Architecture Validation: Reviews the existing tech stack, database schema, and API design against project requirements, identifying scalability bottlenecks, security gaps, and tech debt risks. - Architecture Decision Records (ADRs): Documents every significant decision with context, alternatives, trade-offs, and status, stored in a docs/adr/ directory. - Security & Scalability Planning: Defines authentication flows (JWT, RBAC), caching and queue strategies, threat models (STRIDE), and scaling plans for expected load. - Use Case: Before building a new multi-tenant SaaS module, activate this Skill to validate the PostgreSQL schema, compare Prisma vs Drizzle with explicit trade-offs, and produce ADRs plus a C4 system diagram for the engineering team. ## Quick Start Review the architecture for my new billing module and write ADRs for the stack and database decisions before I start coding.
