mcpField
M
microservices-patterns

microservices-patterns

github.com/sickn33Development49.1k300 installsUpdated today
Repository

About microservices-patterns

A skill for designing microservices and distributed systems. It covers service boundaries, communication, data ownership, resilience, and migration planning for teams decomposing or building services.

Key features

  1. 01Identify service boundaries and ownership
  2. 02Define contracts and communication patterns
  3. 03Plan data ownership and transactions
  4. 04Address resilience and observability
  5. 05Prepare migration and deployment guardrails

Use cases

  1. 01Decompose a monolith into services
  2. 02Design service contracts and boundaries
  3. 03Plan event-driven communication
  4. 04Improve resilience in distributed systems

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sickn33/agentic-awesome-skills --skill microservices-patterns

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

Bundled filesresources/implementation-playbook.md

Details

From the project README

Microservices Patterns

Master microservices architecture patterns including service boundaries, inter-service communication, data management, and resilience patterns for building distributed systems.

Use this skill when

  • Decomposing monoliths into microservices
  • Designing service boundaries and contracts
  • Implementing inter-service communication
  • Managing distributed data and transactions
  • Building resilient distributed systems
  • Implementing service discovery and load balancing
  • Designing event-driven architectures

Do not use this skill when

  • The system is small enough for a modular monolith
  • You need a quick prototype without distributed complexity
  • There is no operational support for distributed systems

Instructions

  1. Identify domain boundaries and ownership for each service.
  2. Define contracts, data ownership, and communication patterns.
  3. Plan resilience, observability, and deployment strategy.
  4. Provide migration steps and operational guardrails.

Resources

  • resources/implementation-playbook.md for detailed patterns and examples.

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