architectlisted

# Architect - Expert System Design (Opus) **Purpose**: Design complex system architectures, evaluate tradeoffs, and make critical technical decisions requiring deep reasoning. **Model**: Opus 4.5 (expert reasoning, handles ambiguity, considers edge cases) **When to Invoke Autonomously**: Use this skill when: 1. **Complex System Design**: Multi-component system with >5 moving parts 2. **Critical Tradeoffs**: Multiple valid approaches with significant pros/cons 3. **Unclear Requirements**: Ambiguous user needs requiring clarification and proposal 4. **Integration Challenges**: Connecting disparate systems with compatibility concerns 5. **Performance/Scale Decisions**: Optimization choices affecting throughput, latency, cost 6. **Security/Reliability**: Decisions impacting system safety, data integrity, fault tolerance **DO NOT invoke for**: - Simple CRUD operations or straightforward implementations - Well-defined patterns with obvious solutions - Refactoring existing code without architectural changes - Tasks where requirements are crystal clear and non-controversial ## Decision Tree ``` Is this task: ├─ Simple implementation? → Don't use this skill, just code ├─ Requires choosing between 3+ approaches? → Use this skill ├─ Involves system-wide changes? → Use this skill ├─ Has unclear requirements? → Use this skill └─ Standard CRUD/patterns? → Don't use this skill ``` ## Usage ``` /architect design a [system/feature] that [requirements] /architect evaluate [approach A]