Skip to content
SkillModel-led1,352 tokens in use

Microservices Architect

Designs microservice architectures: bounded contexts from DDD, sync and async communication, sagas and CQRS, resilience patterns and distributed tracing.

12,471 stars on the repository MIT LicenseJeffallan/claude-skills · skills/microservices-architect
/plugin marketplace add jeffallan/claude-skills /plugin install fullstack-dev-skills@fullstack-dev-skills
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing Microservices Architect costs

76tokens idle
1,352tokens in use
17,124tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

networkdetected

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Excellent
  • Frontmatter15/15
  • Structure23/25
  • Examples12/15
  • Output10/15
  • Size15/15
  • Resources15/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent
  • Reaches the network−10

    does this on the machine, and the frontmatter does not say so

    SKILL.md, line 73

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Excellent
  • Development activity100
  • Maintenance100
  • Community60
  • Maturity36
  • Momentum40

Microservices Architect guides Claude through distributed system design in six steps: domain analysis, communication design, data strategy, resilience, observability and deployment. Each step has a validation checkpoint, for example that every service owns its data, every external call has a timeout and retry budget, and one request can be traced end to end by its correlation ID.

Five reference files cover decomposition, communication, resilience patterns, data management and observability.

What You Get

  • A service boundary diagram with bounded contexts
  • Communication patterns and a REST, gRPC and event decision matrix
  • A data ownership and consistency model with sagas, event sourcing and CQRS
  • Resilience settings for each integration: circuit breaker, retry, bulkhead and timeout
  • Observability design with tracing, correlation IDs, SLOs and alert levels
  • Deployment requirements with probes and a canary or blue-green plan

Common Use Cases

  • Splitting a monolith into services along domain boundaries
  • Choosing between REST, gRPC and messaging for service calls
  • Designing a saga for an order, payment and shipment flow
  • Adding circuit breakers and graceful degradation to service calls
  • Setting up distributed tracing and SLO-based alerting

What Makes It Unique

The checkpoints make the design testable: no shared database schema, async messaging for long-running or cross-aggregate work, an explicit timeout and fallback on every external call, and end-to-end tracing. The constraints name the distributed monolith and chatty interfaces as things to avoid, and the references add Conway’s law, SLO and error budget guidance.

Under The Hood

The skill is a SKILL.md with five reference files and no scripts, and the references load by topic. It is a design skill: the agent produces diagrams, documents and sample code and does not need to run commands in the workflow. The examples call an inventory service over HTTP with a timeout, set response headers, run saga steps against services and database tables, and set up tracing. It names Kafka, RabbitMQ, Istio, Jaeger and Zipkin as options but installs nothing and fetches no web pages.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers