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 enprojectnment-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---56# Architecture Patterns78Master proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design to build maintainable, testable, and scalable systems.910## Use this skill when1112- Designing new backend systems from scratch13- Refactoring monolithic applications for better maintainability14- Establishing architecture standards for your team15- Migrating from tightly coupled to loosely coupled architectures16- Implementing domain-driven design principles17- Creating testable and mockable codebases18- Planning microservices decomposition1920## Do not use this skill when2122- You only need small, localized refactors23- The system is primarily frontend with no backend architecture changes24- You need implementation details without architectural design2526## Instructions27281. 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.3334Refer to `resources/implementation-playbook.md` for detailed patterns, checklists, and templates.3536## Related Skills3738Works well with: `event-sourcing-architect`, `saga-orchestration`, `workflow-automation`, `dbos-*`3940## Resources4142- `resources/implementation-playbook.md` for detailed patterns, checklists, and templates.4344## Limitations45- Use this skill only when the task clearly matches the scope described above.46- Do not treat the output as a substitute for enprojectnment-specific validation, testing, or expert review.47- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
phoroth