MITBackend

Microservices Patterns

Name: Microservices Patterns
Author: wshobson

By wshobson· wshobson/agents· 0

Reference for service boundaries, inter-service communication, and resilience patterns.

Installation

1
Make sure Claude is on your device and in your terminal.
Skills load from ~/.claude/skills/ when Claude Code starts up — so you need it on your machine first. If you don't have it yet, install it once with the command below, then run claude in any terminal to verify.
One-time setup
```
npm i -g @anthropic-ai/claude-code
```
Already have it? Skip ahead.

Paste into Claude Code or into your terminal.

Install

git clone ht•••••••••••••••••••••••••••••••••••• ••••••••••••••••••••• •• ••••• •• •••••••••••••••••••••••••••••••••••••••••••••••• •• •• •• ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• •••••••••••••••••••••••••••••••••••••••••••••••••

This copies the whole skill folder into ~/.claude/skills/microservices-patterns-wshobson/ — the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Safe default: works for every skill.

Faster alternative (instruction-only skills)

Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates — they won't be downloaded and the skill will fail when it tries to load them.

Quick install (SKILL.md only)

mkdir -p ~/.••••••••••••••••••••••••••••••••••••••••••••• •• •••• ••••• ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• •• •••••••••••••••••••••••••••••••••••••••••••••••••••••••••

Restart Claude Code.
Quit and reopen Claude Code (or any other agent that loads from ~/.claude/skills/). New skills are picked up on startup.
Just ask Claude.
Skills auto-activate when your request matches the skill's description — no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the “What this skill does” section above.

Prefer to read the source first? Open on GitHub.

When Claude uses it

Gives Claude a working reference for designing microservices architectures: service decomposition strategies (business capability, DDD subdomains, strangler fig), synchronous and asynchronous communication, per-service data and saga transactions, and resilience patterns like circuit breaker, retry with backoff, and bulkhead. Reach for it when decomposing a monolith, drawing service boundaries, or making distributed systems fault-tolerant. Detailed worked examples live in a referenced details file the skill loads on demand.

What this skill does

What it does: Loads microservices architecture patterns so Claude can design and decompose distributed systems with sound boundaries and failure handling.

Covers service decomposition by business capability, DDD subdomain/bounded context, and the strangler fig pattern for incremental monolith extraction.
Compares synchronous communication (REST, gRPC, GraphQL) against asynchronous events and messaging (Kafka, RabbitMQ, SQS, pub/sub).
Lays out distributed data management: database-per-service ownership and the saga pattern for distributed transactions with compensating actions and eventual consistency.
Documents resilience patterns including circuit breaker, retry with exponential backoff, and bulkhead isolation to prevent cascading failures.
Points to a references/details.md file with detailed patterns and worked examples that the skill reads when the summary tier is not enough.