mcpField
A
architecture-patterns

architecture-patterns

github.com/sickn33Development48.9k908 installsUpdated today
Repository

About architecture-patterns

architecture-patterns is a development skill for planning and evolving backend architectures. It guides pattern selection, boundaries, dependency rules, migration, and validation, with guidance for failure-sensitive workflows.

Key features

  1. 01Clean, Hexagonal, and Domain-Driven Design patterns
  2. 02Guidance on domain boundaries and constraints
  3. 03Module, interface, and dependency design
  4. 04Migration steps and validation checks
  5. 05Failure-sensitive workflow trade-offs

Use cases

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

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sickn33/agentic-awesome-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.
  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.

Comments

Markdown supported