Clean Architecture
Skill Verified ActiveStructure software around the Dependency Rule: source code dependencies point inward from frameworks to use cases to entities. Use when the user mentions "architecture layers", "dependency rule", "ports and adapters", "hexagonal architecture", "use case boundary", "onion architecture", "screaming architecture", or "framework independence". Also trigger when decoupling business logic from databases or frameworks, defining module boundaries, or debating where to put business rules. Covers component principles, boundaries, and SOLID. For code quality, see clean-code. For domain modeling, see domain-driven-design.
To help users understand and apply the principles of Clean Architecture to structure software around the Dependency Rule, promoting maintainable, testable, and independent codebases.
Features
- Explains the Dependency Rule and concentric circles model
- Details Entities and Use Cases with code examples
- Covers Interface Adapters, Frameworks, and their role as details
- Explains Component Principles (cohesion and coupling)
- Provides practical code examples and diagnostic guidance
Use Cases
- Structuring new software projects based on Clean Architecture
- Reviewing existing codebases for adherence to architectural principles
- Understanding how to decouple business logic from frameworks and databases
- Designing modular and maintainable software systems
Non-Goals
- Providing specific framework implementations (e.g., specific ORM or web framework code)
- Acting as a code generator
- Offering solutions for deployment or CI/CD pipelines
Installation
First, add the marketplace
/plugin marketplace add wondelai/skills/plugin install skills@wondelai-skillsQuality Score
VerifiedSimilar Extensions
Architecture Patterns
85Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use this skill when designing clean architecture for a new microservice, when refactoring a monolith to use bounded contexts, when implementing hexagonal or onion architecture patterns, or when debugging dependency cycles between application layers.
V3 Ddd Architecture
100Domain-Driven Design architecture for claude-flow v3. Implements modular, bounded context architecture with clean separation of concerns and microkernel pattern.
API Design Patterns
100Comprehensive API design patterns covering REST, GraphQL, gRPC, versioning, authentication, and modern API best practices
Metal
100Extract the conceptual essence of a repository as skills, agents, and teams — the project's roles, procedures, and coordination patterns expressed as agentskills.io-standard definitions. Reads an arbitrary codebase and produces generalized definitions that capture WHAT the project does and WHO operates it, without replicating HOW it does it. Use when onboarding to a new codebase and wanting to understand its conceptual architecture, when bootstrapping an agentic system from an existing project, when studying a project's organizational DNA for cross-pollination, or when creating a skill/agent/team library inspired by a reference implementation.
Dotnet Core Expert
99Use when building .NET 8 applications with minimal APIs, clean architecture, or cloud-native microservices. Invoke for Entity Framework Core, CQRS with MediatR, JWT authentication, AOT compilation.
Multi Agent Patterns
99Design multi-agent architectures for complex tasks. Use when single-agent context limits are exceeded, when tasks decompose naturally into subtasks, or when specializing agents improves quality.