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 failure-sensitive workflows, compare transactions/outbox, explicit sagas and a suitable durable-execution framework. Persisted workflow state can aid recovery, but external side effects still need idempotency, reconciliation and compensation; assess operational complexity and existing infrastructure before selecting a product.
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.4metadata:5 source: https://skillmd.com/skills/sickn33/architecture-patterns6 aas-risk: none7 aas-source: community8 aas-date-added: '2026-02-27'9---1011# Architecture Patterns1213Master proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design to build maintainable, testable, and scalable systems.1415## Use this skill when1617- Designing new backend systems from scratch18- Refactoring monolithic applications for better maintainability19- Establishing architecture standards for your team20- Migrating from tightly coupled to loosely coupled architectures21- Implementing domain-driven design principles22- Creating testable and mockable codebases23- Planning microservices decomposition2425## Do not use this skill when2627- You only need small, localized refactors28- The system is primarily frontend with no backend architecture changes29- You need implementation details without architectural design3031## Instructions32331. Clarify domain boundaries, constraints, and scalability targets.342. Select an architecture pattern that fits the domain complexity.353. Define module boundaries, interfaces, and dependency rules.364. Provide migration steps and validation checks.375. For failure-sensitive workflows, compare transactions/outbox, explicit sagas and a suitable durable-execution framework. Persisted workflow state can aid recovery, but external side effects still need idempotency, reconciliation and compensation; assess operational complexity and existing infrastructure before selecting a product.3839Refer to `resources/implementation-playbook.md` for detailed patterns, checklists, and templates.4041## Related Skills4243Works well with: `event-sourcing-architect`, `saga-orchestration`, `workflow-automation`, `dbos-*`4445## Resources4647- `resources/implementation-playbook.md` for detailed patterns, checklists, and templates.4849## Limitations50- Use this skill only when the task clearly matches the scope described above.51- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.52- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.