Stats
Actions
Tags
From patterns
Fundamental patterns for building maintainable, scalable systems: separation of concerns, distributed orchestration, and zero-downtime migration strategies.
How this skill is triggered — by the user, by Claude, or both
Slash command
/patterns:skills/architecture-patternsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
These patterns govern how systems are structured and how components interact.
These patterns govern how systems are structured and how components interact.
Implementation Guide
This guide is part of a modular documentation set. Refer to related guides for complete context.
See the full implementation guide in the source documentation.
Single-responsibility components with clear boundaries. Orchestration separate from execution. Testability through isolation.
Use when: Building CLIs, microservices, or any system with distinct responsibilities
Key benefit: Maintainability – change one thing without breaking everything
Centralized orchestration with distributed execution. One coordinator, many workers. Event-driven task distribution.
Use when: Scaling workflows, managing distributed systems, event-driven architectures
Key benefit: Scalability – add workers without changing orchestration
Incremental migration from legacy systems. Run old and new in parallel. Gradually shift traffic. Zero downtime transitions.
Use when: Replacing monoliths, migrating to new tech, risky system rewrites
Key benefit: Risk reduction – rollback at any point, validate in production
Separate discovery, execution, and reporting phases. Workflows that fail gracefully and report completely.
Use when: Building complex CI/CD workflows, multi-step automation
Key benefit: Observability – always know what happened, even on failure
Parallel processing of multiple targets. Dynamic matrices for scalability.
Use when: Processing many targets, scaling workflows, reducing execution time
Key benefit: Performance – parallel execution instead of sequential
flowchart TD
A[System Design] --> B[Separation of Concerns]
B --> C[Clear Boundaries]
C --> D[Hub and Spoke]
D --> E[Distributed Execution]
A --> F[Legacy Migration]
F --> G[Strangler Fig]
G --> B
%% Ghostty Hardcore Theme
style A fill:#65d9ef,color:#1b1d1e
style B fill:#a7e22e,color:#1b1d1e
style C fill:#fd971e,color:#1b1d1e
style D fill:#9e6ffe,color:#1b1d1e
style E fill:#a7e22e,color:#1b1d1e
style F fill:#65d9ef,color:#1b1d1e
style G fill:#f92572,color:#1b1d1e
Separation of Concerns provides the foundation. Hub and Spoke scales it. Strangler Fig migrates to it.
These architectural patterns complement:
Build systems that scale, change, and survive.
npx claudepluginhub adaptive-enforcement-lab/claude-skills --plugin patternsReference catalog of proven architecture patterns. Know when to apply each pattern, tradeoffs, and examples. Use as reference when designing systems.
Guides applying Clean Architecture, Hexagonal Architecture, and Domain-Driven Design to build maintainable, testable backend systems. Useful when designing new systems, refactoring monoliths, or planning microservices decomposition.
Advises on architecture patterns: SOLID, DDD, CQRS, Event Sourcing, Clean/Hexagonal, microservices, Data Mesh, EDA, Service Mesh, micro-frontends, Vertical Slice, Saga/Outbox. For architectural decisions, design evaluations, refactoring.