domains / families / software-engineering / architecture-patterns

architecture-patterns

combined

Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use when architecting complex backend systems or refactoring existing applications for better maintainability. Master proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design to build maintainable, testable, and scalable systems.

When to use

• 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

When not to use

• You only need small, localized refactors
• The system is primarily frontend with no backend architecture changes
• You need implementation details without architectural design
• 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.

Skill page

Conflict

The copies split into two distinct procedural styles. The Vibe-Skills and openclaw-master-skills copies are identical, detailed reference documents that embed the core concepts (Clean, Hexagonal, DDD) and a full Python implementation example directly in the skill. The antigravity-skills and agentic-awesome-skills copies are shorter, procedural wrappers that define a 4-step workflow (clarify, select, define, migrate) and defer the details to an external resource file. The agentic-awesome-skills copy adds a specific constraint regarding durable execution (DBOS) for failure-prone workflows. Because one set contains the actual implementation patterns while the other contains the workflow steps and a specific infrastructure constraint, crowning one would hide the other's material content.