Architecture Patterns

Decision guide for choosing architectural approaches by project complexity, team size, and context. Orchestrates architectural thinking without coupling to specific patterns.

When to Use

• Deciding WHEN to apply architecture vs keeping it simple
• Choosing architectural approach by project complexity
• Planning strategic refactoring (module boundaries, layers)
• Understanding frontend vs backend architectural differences
• Evaluating architecture trade-offs

Don't use for:

• Learning specific patterns → use pattern-specific skills (solid, domain-driven-design, clean-architecture)
• Tactical refactoring (rename, extract, inline) → use code-refactoring skill
• Code review → use critical-partner skill