architecture-patterns

What This Skill Does

The architecture-patterns skill by wpank provides comprehensive guidance on implementing robust, industry-standard backend structures. It focuses on separating concerns to ensure that your business logic remains independent of frameworks, databases, and UI components. By leveraging Clean Architecture, Hexagonal Architecture (Ports and Adapters), and Domain-Driven Design (DDD), this skill assists developers in transforming monolithic, tightly-coupled codebases into modular, testable, and maintainable software systems. It acts as an architectural consultant that enforces the Dependency Rule, ensuring inner business layers remain pure and unaffected by infrastructure changes.

Installation

To integrate this skill into your development environment, run the following command in your terminal: clawhub install openclaw/skills/skills/wpank/architecture-patterns

Use Cases

• Refactoring existing legacy systems: Use the pattern analysis to decompose large, unmanageable monoliths into distinct layers or microservices.
• Bootstrapping new projects: Receive guidance on setting up an optimized directory structure that scales as project requirements grow.
• Unit Testing Improvement: By implementing the Ports and Adapters pattern, you can easily swap out concrete database implementations for mocks during test execution.
• Team Standardization: Use the decision framework to reach a consensus on which design pattern fits the complexity of your current team and project scope.
• Debugging and Maintenance: Apply the Dependency Rule to isolate bug locations and prevent cross-layer contamination.

Example Prompts

1. "I am starting a new project with medium complexity. Given the current requirements, explain why Clean Architecture might be better than a simple CRUD script, and provide a file structure."
2. "I have an existing database module that is tightly coupled with my business logic. Can you help me define the necessary Ports and Adapters to decouple them?"
3. "Our project is suffering from 'spaghetti code' in our controllers. How can I apply Domain-Driven Design principles to move business rules into a dedicated domain layer?"

Tips & Limitations

• Avoid Over-engineering: The skill explicitly warns that simple CRUD applications do not require complex patterns. Applying DDD to a basic app can result in unnecessary cognitive overhead.
• Follow the Dependency Rule: Always verify that your domain layer has zero dependencies on infrastructure libraries or framework-specific code.
• Evolution: Architecture should evolve; don't feel forced to implement a strict DDD approach if your project scope doesn't justify the investment. Start with Clean Architecture layers and migrate to more complex domain patterns as the business requirements become sophisticated.