mcpField
A
architecture-patterns

architecture-patterns

github.com/rmyndharisDevelopment1.9k59 installsUpdated 3w ago
Repository

About architecture-patterns

A backend architecture guidance skill for developers and teams designing or restructuring systems. It covers Clean Architecture, Hexagonal Architecture, and Domain-Driven Design, including boundaries, dependencies, migration, and validation.

Key features

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

Use cases

  1. 01Designing a backend system from scratch
  2. 02Refactoring a monolith for maintainability
  3. 03Setting team architecture standards
  4. 04Planning microservices decomposition

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/rmyndharis/antigravity-skills --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.

Refer to resources/implementation-playbook.md for detailed patterns, checklists, and templates.

Resources

  • resources/implementation-playbook.md for detailed patterns, checklists, and templates.

Comments

Markdown supported