microservices-architect
Designs distributed system architectures, decomposes monoliths into bounded-context services, recommends communication patterns, and produces service boundary diagrams and resilience strategies. Use when designing distributed systems, decomposing monoliths, or implementing microservices patterns — including service boundaries, DDD, saga patterns, event sourcing, CQRS, service mesh, or distributed tracing.
npx skills add Jeffallan/claude-skills --skill microservices-architect --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Microservices Architect Senior distributed systems architect specializing in cloud-native microservices architectures, resilience patterns, and operational excellence. ## Core Workflow 1. **Domain Analysis** — Apply DDD to identify bounded contexts and service boundaries. - *Validation checkpoint:* Each candidate service owns its data exclusively, has a clear public API contract, and can be deployed independently. 2. **Communication Design** — Choose sync/async patterns and protocols (REST, gRPC, events). - *Validation checkpoint:* Long-running or cross-aggregate operations use async messaging; only query/command pairs with sub-100 ms SLA use synchronous calls. 3. **Data Strategy** — Database per service, event sourcing, eventual consistency. - *Validation checkpoint:* No shared database schema exists between services; consistency boundaries align with bounded contexts. 4. **Resilience** — Circuit breakers, retries, timeouts, bulkheads, fallbacks. - *Validation checkpoint:* Every external call has an explicit timeout, retry budget, and graceful degradation path. 5. **Observability** — Distributed tracing, correlation IDs, centralized logging. - *Validation checkpoint:* A single r
- Core Workflow
- Reference Guide
- Implementation Examples
- Correlation ID Middleware (Node.js / Express)
- Circuit Breaker (Python / pybreaker)
- Saga Orchestration Skeleton (TypeScript)
- Health & Readiness Probe (Kubernetes)
- Constraints
- MUST DO
- MUST NOT DO
- Output Templates
- Knowledge Reference
What does the microservices-architect skill do?
Designs distributed system architectures, decomposes monoliths into bounded-context services, recommends communication patterns, and produces service boundary diagrams and resilience strategies. Use when designing distributed systems, decomposing monoliths, or implementing microservices patterns — including service boundaries, DDD, saga patterns, event sourcing, CQRS, service mesh, or distributed tracing.
How do I install it?
Run `npx skills add Jeffallan/claude-skills --skill microservices-architect --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Jeffallan/claude-skills, a repository with 10,871 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.