Architecture Patterns
Skill ActiveImplement 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.
Implement proven backend architecture patterns to build maintainable, testable, and scalable systems.
Features
- Implement Clean Architecture layers and principles
- Implement Hexagonal Architecture ports and adapters
- Implement Domain-Driven Design strategic and tactical patterns
- Provide directory structure examples
- Illustrate core implementation with Python code snippets
- Guide on testing with in-memory adapters
- Troubleshoot common architectural issues
Use Cases
- Designing new backend services or microservices from scratch
- Refactoring monolithic applications
- Establishing bounded contexts before splitting a system
- Debugging dependency cycles between application layers
- Creating testable codebases independent of external services
Non-Goals
- Providing a full framework or library
- Handling deployment or infrastructure setup
- Covering frontend or mobile architecture patterns
Workflow
- Understand core architectural concepts (Clean, Hexagonal, DDD)
- Review directory structure and implementation examples
- Apply patterns to new or existing projects
- Use provided troubleshooting guidance for common issues
Practices
- Clean Architecture
- Hexagonal Architecture
- Domain-Driven Design
- Dependency Injection
- Testability
Versioning
- warning:Release ManagementThere is no explicit versioning information (like semver in frontmatter or GitHub releases) for this skill, and installation instructions in the README reference 'main', making version pinning difficult.
Execution
- warning:Pinned dependenciesWhile the `plugins/backend-development/skills/architecture-patterns/SKILL.md` and related files do not explicitly list dependencies, the root `README.md` mentions a lockfile (`poetry.lock` or similar implied by `Pipfile.lock` for Python). However, specific interpreter versions or side-effect headers are not declared for bundled scripts.
Installation
First, add the marketplace
/plugin marketplace add wshobson/agents/plugin install backend-development@claude-code-workflowsQuality Score
Trust Signals
Similar Extensions
Clean Architecture
99Structure 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.
Domain Driven Design
98Model software around the business domain using bounded contexts, aggregates, and ubiquitous language. Use when the user mentions "domain modeling", "bounded context", "aggregate root", "ubiquitous language", "anti-corruption layer", "context mapping", "domain events", or "strategic design". Also trigger when splitting a monolith into services, defining microservice boundaries, or aligning code structure with business processes. Covers entities vs value objects, domain events, and context mapping strategies. For architecture layers, see clean-architecture. For complexity, see software-design-philosophy.
Event Store Design
90Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
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.