microservices-patterns — Claude Code skill: install and use
A practical guide to service boundaries, event-driven communication, data ownership, and resilience patterns for distributed systems.
/plugin marketplace add wshobson/agents
/plugin install backend-development@claude-code-workflowsWhat microservices-patterns does
This skill covers ways to split a monolith by business capability or DDD subdomain, map bounded contexts to services, and migrate gradually with the Strangler Fig pattern. It also compares REST, gRPC, GraphQL, Kafka, RabbitMQ, SQS, and Pub/Sub for service communication.
Its patterns include Database per Service, Saga, Circuit Breaker, Retry with Backoff, and Bulkhead. Detailed explanations and worked examples are stored in references/details.md, which the skill points to when the short navigation layer is not enough.
Install it when you are shaping a distributed architecture or planning a monolith migration. A small application with no real service boundaries probably does not need this skill.
What it helps with
- split a monolith around business capabilities
- define service boundaries and contracts
- choose between request/response and events
- handle distributed transactions with Saga
- contain failures across dependent services
Example prompts for the agent
- Break this monolith into services using bounded contexts and suggest a migration order.
- Compare REST, gRPC, and Kafka for communication between these services.
- Apply Circuit Breaker, Retry with Backoff, and Bulkhead to this order architecture.
How to install microservices-patterns
1Plugin marketplace
/plugin marketplace add wshobson/agents/plugin install backend-development@claude-code-workflowsThis installs the whole backend-development plugin with all its skills
2Skills CLI (Vercel)
npx skills add wshobson/agents --skill microservices-patterns -a claude-code3Manually: put the files in place
~/.claude/skills/microservices-patterns/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/microservices-patterns/
1Skills CLI (Vercel)
npx skills add wshobson/agents --skill microservices-patterns -a codex2Manually: put the files in place
.agents/skills/microservices-patterns/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add wshobson/agents --skill microservices-patterns -a cursor2Manually: put the files in place
.cursor/skills/microservices-patterns/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install wshobson/agents microservices-patterns2Manually: put the files in place
.github/skills/microservices-patterns/SKILL.mdPlatform CLI
gemini skills install https://github.com/wshobson/agents --path plugins/backend-development/skills/microservices-patternsManually: put the files in place
.devin/skills/microservices-patterns/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set213
The whole set →Similar
Questions about microservices-patterns
How do I install microservices-patterns in Claude Code?
Run npx skills add wshobson/agents --skill microservices-patterns -a claude-code. The skill file is placed at ~/.claude/skills/microservices-patterns/SKILL.md.
What does microservices-patterns do?
It guides service decomposition, communication choices, data ownership, distributed transactions, and resilience patterns for microservice systems.
Which platforms support microservices-patterns?
The skill is available for Claude Code, Codex, and Cursor.
Source text
SKILL.md · MIT
--- name: microservices-patterns description: Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices. --- # Microservices Patterns Master microservices architecture patterns including service boundaries, inter-service communication, data management, and resilience patterns for building distributed systems. ## When to Use This Skill - 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 ## Core Concepts ### 1. Service Decomposition Strategies **By Business Capability** - Organize services around business functions - Each service owns its domain - Example: OrderService, PaymentService, InventoryService **By Subdomain (DDD)** - Core domain, supporting subdomains - Bounded contexts map to services - Clear ownership and responsibility **Strangler Fig Pattern** - Gradually extract from monolith - New functionality as microservices - Proxy routes to old/new systems ### 2. Communication Patterns **Synchronous (Request/Response)** - REST APIs - gRPC - GraphQL **Asynchronous (Events/Messages)** - Event streaming (Kafka) - Message queues (RabbitMQ, SQS) - Pub/Sub patterns ### 3. Data Management **Database Per Service** - Each service owns its data - No shared databases - Loose coupling **Saga Pattern** - Distributed transactions - Compensating actions - Eventual consistency ### 4. Resilience Patterns **Circuit Breaker** - Fail fast on repeated errors - Prevent cascade failures **Retry with Backoff** - Transient fault handling - Exponential backoff **Bulkhead** - Isolate resources - Limit impact of failures ## Detailed patterns and worked examples Detailed pattern documentation lives in `references/details.md`. Read that file when the navigation tier above is insufficient.
© Seth Hobson · MIT · wshobson/agents