mcpField
A
architecture-patterns

architecture-patterns

github.com/davila7Development33.0k38 installsUpdated 1d ago
Repository

About architecture-patterns

A skill for selecting and applying backend architecture patterns, including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. It helps teams define boundaries, interfaces, dependencies, and migration checks for maintainable systems.

Key features

  1. 01Clean and Hexagonal Architecture guidance
  2. 02Domain-Driven Design principles
  3. 03Module boundaries and interfaces
  4. 04Dependency rules and migration steps
  5. 05Validation checks
  6. 06Durable workflow guidance for failure-prone processes

Use cases

  1. 01Designing a backend system
  2. 02Refactoring a monolith
  3. 03Planning microservices decomposition
  4. 04Making a codebase more testable

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/davila7/claude-code-templates --skill architecture-patterns

After installing, type/architecture-patternsin Claude Code to confirm it loaded.

Bundled filesresources/implementation-playbook.md

Details

From the project README

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.

Comments

Markdown supported