Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
davila7 avatar

Architecture Patterns

  • 23 installs
  • 30.1k repo stars
  • Updated August 4, 2026
  • davila7/claude-code-templates

Apply backend architecture patterns like Clean Architecture, Hexagonal Architecture, and Domain-Driven Design to build maintainable, testable, scalable systems.

About

Guides selecting and applying proven backend architecture patterns, defining module boundaries, dependency rules, and migration steps. A developer uses it when designing new systems, decoupling monoliths, or planning microservices decomposition.

  • Covers Clean, Hexagonal, and DDD architecture selection
  • Notes durable execution frameworks for failure-surviving workflows

Architecture Patterns by the numbers

  • 23 all-time installs (skills.sh)
  • Ranked #3,434 of 4,347 Backend & APIs skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/davila7/claude-code-templates --skill architecture-patterns

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs23
repo stars30.1k
Last updatedAugust 4, 2026
Repositorydavila7/claude-code-templates

What it does

Apply backend architecture patterns like Clean Architecture, Hexagonal Architecture, and Domain-Driven Design to build maintainable, testable, scalable systems.

Files

SKILL.mdMarkdownGitHub ↗

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 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.md for detailed patterns, checklists, and templates.

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.