/architecture-patterns
Master proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design to build maintainable, testable, and scalable systems.
One skill from agentic-awesome-skills.
shell
$ npx -y skills add sickn33/agentic-awesome-skills --skill architecture-patterns --agent claude-codeInstalls just this skill. Get the whole plugin for auto-invocation.
How it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/architecture-patterns
Context preview
The summary Claude sees to decide when to auto-load this skill.
Master proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design to build maintainable, testable, and scalable systems.
Stats
Stars43,759
Forks6,464
LanguagePython
LicenseMIT
Ships with agentic-awesome-skills
SKILL.md
architecture-patterns.SKILL.md
--- name: architecture-patterns description: "Master proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design to build maintainable, testable, and scalable systems." risk: none source: community date_added: "2026-02-27" --- # Architecture Patterns 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 1. Clarify domain boundaries, constraints, and scalability targets.
