What problem does it solve? Design decisions made without structured review lead to hidden coupling, unclear ownership, missing failure handling, and costly rework after implementation. This Skill applies a refined 100-rule system design checklist to architecture proposals, ADRs, API contracts, and data models before code is written, scaling review depth to the decision's risk and blast radius. ## Core Features & Use Cases - Risk-scaled design review: Applies light, standard, or deep review depth based on reversibility, blast radius, and uncertainty instead of forcing all 100 rules onto every change. - Trade-off-driven option comparison: Compares design options by what each improves, worsens, costs, and when to revisit, covering data ownership, APIs, reliability, security, observability, and cost. - Structured decision output: Produces a decision summary, checklist findings, recommended design, validation plan, and open questions. - Use Case: Before committing to an event-driven architecture for an order system, use this Skill to evaluate consistency requirements, idempotency, schema evolution, and team ownership, then receive a concrete recommendation with risks and validation steps. ## Quick Start Use $system-design-rules to review my proposed architecture for the new billing service and compare it against a synchronous API approach.
