architecture-designer

Writing an Architecture Decision Record (ADR) for microservices involves documenting context, decisions, consequences, and alternatives. The architecture-designer skill guides this by turning functional and non-functional requirements into pattern-backed decisions with explicit trade-offs and risks.

Creating a system design diagram with Mermaid for scalability planning requires mapping components and relationships visually. The architecture-designer skill generates a high-level Mermaid component diagram alongside a scalable, failure-aware design plan based on stated requirements.

Choosing between a modular monolith and microservices architecture depends on evaluating non-functional requirements and trade-offs. The architecture-designer skill selects architectural patterns and justifies choices by comparing scalability, complexity, and failure-aware design factors.

Documenting architectural trade-offs and risks for technical stakeholders requires capturing context, decisions, and consequences consistently. The architecture-designer skill produces structured outputs including requirements summaries, trade-offs, risks, and ADRs to ensure teams build the right solution and avoid costly rework.

System design patterns can be applied to architecture reviews and scalability forecasting by evaluating non-functional requirements and component interactions. The architecture-designer skill loads reference materials for patterns and NFR checks to produce reviewable, failure-aware architecture plans.

You need to formalize system architecture decisions when starting a new platform or planning scalable systems to prevent costly rework. The architecture-designer skill turns ambiguous system goals into clear, reviewable architecture with explicit trade-offs, Mermaid diagrams, and ADRs for both engineers and product leaders.