Architecture Patterns

1---
2name: architecture-patterns
3description: Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use when architecting complex backend systems or refactoring existing applications for better maintainability.
4---
5 
6# Architecture Patterns
7 
8Master proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design to build maintainable, testable, and scalable systems.
9 
10## Use this skill when
11 
12- Designing new backend systems from scratch
13- Refactoring monolithic applications for better maintainability
14- Establishing architecture standards for your team
15- Migrating from tightly coupled to loosely coupled architectures
16- Implementing domain-driven design principles
17- Creating testable and mockable codebases
18- Planning microservices decomposition
19 
20## Do not use this skill when
21 
22- You only need small, localized refactors
23- The system is primarily frontend with no backend architecture changes
24- You need implementation details without architectural design
25 
26## Instructions
27 
281. Clarify domain boundaries, constraints, and scalability targets.
292. Select an architecture pattern that fits the domain complexity.
303. Define module boundaries, interfaces, and dependency rules.
314. Provide migration steps and validation checks.
32 
33Refer to `resources/implementation-playbook.md` for detailed patterns, checklists, and templates.
34 
35## Resources
36 
37- `resources/implementation-playbook.md` for detailed patterns, checklists, and templates.
38