Architecture Designer

This walks you through system design decisions with the structure of a senior architect who's been burned before. It pushes you to write ADRs for major choices, evaluate trade-offs instead of just benefits, and explicitly consider failure modes and operational complexity. The workflow is prescriptive: gather requirements, match patterns, design with diagrams, document decisions, review with stakeholders. It includes reference guides for common decision points like monolith versus microservices or database selection. The constraint list is opinionated in useful ways, like "don't over-engineer for hypothetical scale" and "don't skip security considerations." If you tend to jump straight to coding or pick technologies based on hype, this adds the discipline of documenting why before you commit.