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.4license: MIT5---67# Architecture Patterns89Master proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design to build maintainable, testable, and scalable systems.1011## Use this skill when1213- Designing new backend systems from scratch14- Refactoring monolithic applications for better maintainability15- Establishing architecture standards for your team16- Migrating from tightly coupled to loosely coupled architectures17- Implementing domain-driven design principles18- Creating testable and mockable codebases19- Planning microservices decomposition2021## Do not use this skill when2223- You only need small, localized refactors24- The system is primarily frontend with no backend architecture changes25- You need implementation details without architectural design2627## Instructions28291. Clarify domain boundaries, constraints, and scalability targets.302. Select an architecture pattern that fits the domain complexity.313. Define module boundaries, interfaces, and dependency rules.324. Provide migration steps and validation checks.335. 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.3435Refer to `resources/implementation-playbook.md` for detailed patterns, checklists, and templates.3637## Related Skills3839Works well with: `event-sourcing-architect`, `saga-orchestration`, `workflow-automation`, `dbos-*`4041## Resources4243- `resources/implementation-playbook.md` for detailed patterns, checklists, and templates.4445## Limitations46- Use this skill only when the task clearly matches the scope described above.47- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.48- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
newmindsgroup