Architecture Designer

**Verdict:** A strong, well-structured architecture advisory skill that is particularly suitable for system design, architecture reviews, and ADR-driven decision-making, especially in distributed and cloud environments. **Strengths** - Focused on **system and software architecture** with explicit coverage of distributed systems, cloud, and scalability trade-offs. - Enforces good practice via **ADRs, NFR checklists, and trade-off analysis**, which is critical for real-world architecture work. - Clear “when to use” guidance and **output templates** (requirements summary, diagram description, ADRs, risks/mitigations) improve consistency and usability. - Local reference docs (patterns, system-design, database-selection, NFR checklist) suggest **good breadth** across common architecture concerns. **Key Risks / Limitations** - Architecture recommendations are **general-purpose** and may not fully account for organization-specific constraints, legacy systems, or compliance requirements unless clearly described by the user. - Security is mentioned as a must-not-ignore area, but **deep security/complaince architecture** may require a dedicated security skill or human review. - High-level diagrams will be **textual descriptions**, not formal diagrams; users must still translate into tools like C4, UML, or cloud-specific diagramming. - Potential for **overengineering** or overly modern patterns if requirements and constraints are not specified concretely. **Best-Fit Scenarios** - Early-stage **system design and re-design** (e.g., new service, platform, or migration from monolith to microservices). - Teams needing structured **ADR documentation** and clearer rationale for technology and architectural choices. - Architecture reviews focused on **scalability, reliability, and operational concerns** in cloud-based or distributed systems. - Helping less-experienced engineers think in terms of **NFRs, trade-offs, and failure modes**, under the supervision of an experienced architect.