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.
1---2name: architecture-patterns3description: Architecture Patterns4---5# Architecture Patterns67Master proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design to build maintainable, testable, and scalable systems.89## Use this skill when1011- Designing new backend systems from scratch12- Refactoring monolithic applications for better maintainability13- Establishing architecture standards for your team14- Migrating from tightly coupled to loosely coupled architectures15- Implementing domain-driven design principles16- Creating testable and mockable codebases17- Planning microservices decomposition1819## Do not use this skill when2021- You only need small, localized refactors22- The system is primarily frontend with no backend architecture changes23- You need implementation details without architectural design2425## Instructions26271. Clarify domain boundaries, constraints, and scalability targets.282. Select an architecture pattern that fits the domain complexity.293. Define module boundaries, interfaces, and dependency rules.304. Provide migration steps and validation checks.315. 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.3233Refer to `resources/implementation-playbook.md` for detailed patterns, checklists, and templates.3435## Related Skills3637Works well with: `event-sourcing-architect`, `saga-orchestration`, `workflow-automation`, `dbos-*`3839## Resources4041- `resources/implementation-playbook.md` for detailed patterns, checklists, and templates.
ComeOnOliver