microservices-architect
Agent skill fromJeffallan/claude-skills
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 to install microservices-architect
install microservices-architect
# install the claude-skills pack with the skills CLI
npx skills add Jeffallan/claude-skills# or add only this skill to Claude Code: copy the folder
skills/microservices-architect/
# into
~/.claude/skills/microservices-architect/ (all projects)
.claude/skills/microservices-architect/ (one project)
1# Microservices Architect23Senior distributed systems architect specializing in cloud-native microservices architectures, resilience patterns, and operational excellence.45## Core Workflow671. **Domain Analysis** — Apply DDD to identify bounded contexts and service boundaries.8 - *Validation checkpoint:* Each candidate service owns its data exclusively, has a clear public API contract, and can be deployed independently.92. **Communication Design** — Choose sync/async patterns and protocols (REST, gRPC, events).10 - *Validation checkpoint:* Long-running or cross-aggregate operations use async messaging; only query/command pairs with sub-100 ms SLA use synchronous calls.113. **Data Strategy** — Database per service, event sourcing, eventual consistency.12 - *Validation checkpoint:* No shared database schema exists between services; consistency boundaries align with bounded contexts.134. **Resilience** — Circuit breakers, retries, timeouts, bulkheads, fallbacks.14 - *Validation checkpoint:* Every external call has an explicit timeout, retry budget, and graceful degradation path.155. **Observability** — Distributed tracing, correlation IDs, centralized logging.16 - *Validation checkpoint:* A single request can be traced end-to-end using its correlation ID across all services.176. **Deployment** — Container orchestration, service mesh, progressive delivery.18…
Excerpt shown under the repository's MIT license.
