architecture-patterns · sickn33 — Claude Code skill: how to install
Guides backend system design using Clean Architecture, Hexagonal Architecture, and DDD, and assists with monolith decomposition.
npx skills add sickn33/agentic-awesome-skills --skill architecture-patterns -a claude-codeWhat architecture-patterns does
The skill structures backend architecture planning. It organizes the workflow into five concrete steps: clarifying domain boundaries and scaling goals, choosing an architectural pattern, defining module boundaries with dependency rules, providing migration steps, and evaluating failure-sensitive workflows. For templates and checklists, it references resources/implementation-playbook.md.
For failure-handling logic, the instructions compare transactional outbox patterns, explicit sagas, and durable-execution frameworks. External side effects still require idempotency and compensation mechanisms, so the agent must evaluate your existing operational overhead before suggesting tools. If boundaries or permissions are missing, the skill halts and requests clarification.
What it helps with
- design new backend architectures from scratch
- plan monolithic decomposition into loosely coupled modules
- implement domain-driven design principles
- structure failure-sensitive workflows using Outbox or sagas
Example prompts for the agent
- Help me design a new order service using hexagonal architecture principles.
- Plan the decomposition of our billing monolith into modular services using the Outbox pattern.
How to install architecture-patterns
1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill architecture-patterns -a claude-code2Manually: put the files in place
~/.claude/skills/architecture-patterns/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/architecture-patterns/
1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill architecture-patterns -a codex2Manually: put the files in place
.agents/skills/architecture-patterns/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill architecture-patterns -a cursor2Manually: put the files in place
.cursor/skills/architecture-patterns/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install sickn33/agentic-awesome-skills architecture-patterns2Manually: put the files in place
.github/skills/architecture-patterns/SKILL.md1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill architecture-patterns -a gemini-cli2Platform CLI
gemini skills install https://github.com/sickn33/agentic-awesome-skills --path skills/architecture-patternsManually: put the files in place
.devin/skills/architecture-patterns/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill architecture-patterns -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set80
The whole set →Other versions of architecture-patterns
Similar
Questions about architecture-patterns
How do I install architecture-patterns in Claude Code?
Run npx skills add sickn33/agentic-awesome-skills --skill architecture-patterns -a claude-code.
What does the architecture-patterns skill do?
It guides backend pattern selection, defines module boundaries, and structures migrations from monolithic systems to loosely coupled services.
When should this skill be avoided?
The skill instructions explicitly exclude localized refactoring and tasks limited strictly to frontend code without backend changes.
Source text
SKILL.md · MIT
--- 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. 2. Select an architecture pattern that fits the domain complexity. 3. Define module boundaries, interfaces, and dependency rules. 4. Provide migration steps and validation checks. 5. For failure-sensitive workflows, compare transactions/outbox, explicit sagas and a suitable durable-execution framework. Persisted workflow state can aid recovery, but external side effects still need idempotency, reconciliation and compensation; assess operational complexity and existing infrastructure before selecting a product. 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.md` for detailed patterns, checklists, and templates. ## Limitations - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
© sickn33 · MIT · sickn33/agentic-awesome-skills