Architecture Patterns
SkillMediaThis is an architecture claude skill that teaches an AI agent established backend architecture patterns such as Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. With it, the agent can help design systems that are maintainable, testable, and scalable.
Available today. Use it from your connected AI after setup.
No other account needed.
Have an AI agent that supports loading skills.
Then ask your AI: use the Architecture Patterns skill
What your AI can do with it
- Applies Clean Architecture when structuring backend systems
- Uses Hexagonal Architecture to separate core logic from external concerns
- Applies Domain-Driven Design to model business domains
- Guides designs aimed at maintainable, testable, and scalable systems
Getting started
- Have an AI agent that supports loading skills.
- Add the architecture-patterns skill to the agent's available skills.
- Ask the agent to apply Clean Architecture, Hexagonal Architecture, or Domain-Driven Design to a backend design or codebase.
What this skill tells your AI
The instructions your AI receives, as published by davila7/claude-code-templates in cli-tool/components/skills/development/architecture-patterns/SKILL.md and read by ahel’s review.
Master proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design to build maintainable, testable, and scalable systems.
Use this skill when
- 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
Do not use this skill when
- You only need small, localized refactors
- The system is primarily frontend with no backend architecture changes
- You need implementation details without architectural design
Instructions
- Clarify domain boundaries, constraints, and scalability targets.
- Select an architecture pattern that fits the domain complexity.
- Define module boundaries, interfaces, and dependency rules.
- Provide migration steps and validation checks.
- For workflows that must survive failures (payments, order fulfillment, multi-step processes), use durable execution at the infrastructure layer — frameworks like DBOS persist workflow state, providing crash recovery without adding architectural complexity.
Refer to resources/implementation-playbook.md for detailed patterns, checklists, and templates.
Related Skills
Works well with: event-sourcing-architect, saga-orchestration, workflow-automation, dbos-*
Resources
resources/implementation-playbook.mdfor detailed patterns, checklists, and templates.
Signals
- GitHub stars
- 32k
- Forks
- 4k
- Last commit
- Sep 2026
Questions
- What architecture patterns does this skill cover?
- It covers Clean Architecture, Hexagonal Architecture, and Domain-Driven Design for backend systems.
- What is the goal of using these patterns?
- The patterns help build systems that are maintainable, testable, and scalable.
Advanced
- Item type
- skill
- Key
architecture-patterns-davila7- Source
- github.com/davila7/claude-code-templates