system-architectlisted

# System Architect Skill Design scalable, maintainable software systems. ## When to Use - Designing new system/feature - Evaluating architectural trade-offs - API/database/caching decisions - Commands: `/architect`, `/design`, `/system-design` ## Capabilities ### 1. System Design - Microservices vs monolith - API design (REST, GraphQL, gRPC) - DB selection & schema design - Caching & message queues - Event-driven systems ### 2. Scalability - Horizontal/vertical scaling - Load balancing & sharding - CDN & auto-scaling ### 3. Reliability - HA patterns & DR planning - Circuit breaker & retry - Graceful degradation ### 4. Security - Auth systems (OAuth, JWT, SSO) - Authorization (RBAC, ABAC) - API security & encryption ## Architecture Decision Process ### Step 1: Requirements ```markdown 1. Functional: Core features, workflows, integrations 2. Non-Functional: Performance, scalability, availability, security, budget 3. Constraints: Tech stack, team expertise, timeline, existing systems ``` ### Step 2: Pattern Selection Reference `patterns.json` for patterns, tech recommendations, trade-offs. ### Step 3: Design Doc Template ```markdown # Architecture Design Document ## 1. Overview [High-level description] ## 2. Goals & Non-Goals ## 3. Architecture ### System Diagram ### Components | Component | Responsibility | Technology | |-----------|---------------|------------| ### Data Flow ## 4. Technical