designing-architecturelisted

# Designing Architecture ### When to Load - **Trigger**: System design, module structure, new project scaffolding, choosing architecture patterns - **Skip**: Simple bug fixes or minor code changes that don't affect architecture ## Architecture Decision Workflow Copy this checklist and track progress: ``` Architecture Design Progress: - [ ] Step 1: Understand requirements and constraints - [ ] Step 2: Assess project size and team capabilities - [ ] Step 3: Select architecture pattern - [ ] Step 4: Define directory structure - [ ] Step 5: Document trade-offs and decision - [ ] Step 6: Validate against decision framework ``` ## Pattern Selection Guide ### By Project Size | Size | Recommended Pattern | | ----------------- | --------------------------------- | | Small (<10K LOC) | Simple MVC/Layered | | Medium (10K-100K) | Clean Architecture | | Large (>100K) | Modular Monolith or Microservices | ### By Team Size | Team | Recommended | | --------- | ---------------------------- | | 1-3 devs | Monolith with clear modules | | 4-10 devs | Modular Monolith | | 10+ devs | Microservices (if justified) | ## Common Patterns ### 1. Layered Architecture ``` ┌─────────────────────────────┐ │ Presentation │ ← UI, API Controllers ├─────────────────────────────┤ │ Application │ ← Use Cases, Services ├─────────────────────────────┤ │ Domain