Architecture Patterns
Master proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design to build maintainable, testable, and scalable systems.
Use this skill when
- Designing new backend systems from scratch
- Refactoring monolithic applications for better maintainability
- Establishing architecture standards for your team
- Migrating from tightly coupled to loosely coupled architectures
- Implementing domain-driven design principles
- Creating testable and mockable codebases
- Planning microservices decomposition
Do not use this skill when
- You only need small, localized refactors
- The system is primarily frontend with no backend architecture changes
- You need implementation details without architectural design
Instructions
- Clarify domain boundaries, constraints, and scalability targets.
- Select an architecture pattern that fits the domain complexity.
- Define module boundaries, interfaces, and dependency rules.
- Provide migration steps and validation checks.
- For workflows that must survive failures (payments, order fulfillment, multi-step processes), use durable execution at the infrastructure layer — frameworks like DBOS persist workflow state, providing crash recovery without adding architectural complexity.
Refer to resources/implementation-playbook.md for detailed patterns, checklists, and templates.
Related Skills
Works well with: event-sourcing-architect, saga-orchestration, workflow-automation, dbos-*
Resources
resources/implementation-playbook.md for detailed patterns, checklists, and templates.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
1---2name: architecture-patterns3description: Master proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design to build maintainable, testable, and scalable systems.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.
325. For workflows that must survive failures (payments, order fulfillment, multi-step processes), use durable execution at the infrastructure layer — frameworks like DBOS persist workflow state, providing crash recovery without adding architectural complexity.
33
34Refer to `resources/implementation-playbook.md` for detailed patterns, checklists, and templates.
35
36## Related Skills
37
38Works well with: `event-sourcing-architect`, `saga-orchestration`, `workflow-automation`, `dbos-*`
39
40## Resources
41
42- `resources/implementation-playbook.md` for detailed patterns, checklists, and templates.
43
44## Limitations
45- Use this skill only when the task clearly matches the scope described above.
46- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
47- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
sickn33