Back to catalog
Human reviewedData & analysis

Skill dossier

microservices-architect

Source declaration

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.

The author's original description, preserved in English. It describes intent, not verified performance.

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.

datareferences

Research summary

Human reviewed

Skill Atlas editorial review · editorial-preview-1.0.0

An architecture Skill for decomposing systems into bounded-context services, choosing communication patterns, and planning resilience, observability and deployment.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Applies domain-driven design to find service boundaries.
  • Chooses synchronous or asynchronous communication per interaction.
  • Plans database-per-service data ownership and consistency.
  • Specifies circuit breakers, correlation IDs and health probes.

Limitations & scope

  • Outputs are design guidance; no running system is built or tested.
  • The 100 ms synchronous-call threshold is a stated rule of thumb, not validated.
  • Distributed designs add operational overhead the skill does not quantify.

Relevant for

  • Architects decomposing monoliths
  • Teams designing event-driven systems
  • Engineers adding resilience patterns

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
6
Markdown files
6
scripts
0
references
5
Size
71.2 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/microservices-architect/references/communication.mdReference9.9 KB
skills/microservices-architect/references/data.mdReference15.3 KB
skills/microservices-architect/references/decomposition.mdReference8.1 KB
skills/microservices-architect/references/observability.mdReference17.2 KB
skills/microservices-architect/references/patterns.mdReference13.8 KB
skills/microservices-architect/SKILL.mdInstruction6.9 KB

SKILL.md frontmatter

{
  "name": "microservices-architect",
  "description": "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.",
  "license": "MIT",
  "metadata": {
    "author": "https://github.com/Jeffallan",
    "company": "https://synergetic.solutions",
    "version": "1.1.0",
    "domain": "api-architecture",
    "triggers": "microservices, service mesh, distributed systems, service boundaries, domain-driven design, event sourcing, CQRS, saga pattern, Kubernetes microservices, Istio, distributed tracing",
    "role": "architect",
    "scope": "system-design",
    "output-format": "architecture",
    "related-skills": "devops-engineer, kubernetes-specialist, graphql-architect, architecture-designer, monitoring-expert"
  }
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Input

    Analyze the domain

    Apply DDD to identify bounded contexts and service boundaries.

  2. 02
    Action

    Design data strategy

    Use database per service and eventual consistency; ensure no shared schema.

  3. 03
    Decision

    Check communication fit

    Use async messaging for long-running or cross-aggregate operations.

  4. 04
    Output

    Deliver the design

    Provide boundary diagram, communication patterns, data ownership, resilience and deployment needs.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Items warrant review

34 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useNot observed
Note

File modification is described or implemented

28 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 28 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Medium

Network access is mentioned

6 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 6 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Editorial security note

Check that proposed inter-service calls, message headers and probes do not expose sensitive data or unauthenticated endpoints.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
git clone https://github.com/Jeffallan/claude-skills.git cd claude-skills # Copy this skill directory into one of: # ~/.claude/skills/microservices-architect # .claude/skills/microservices-architect
  1. Open the pinned source at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/microservices-architect/SKILL.md.
  2. Review the license, prerequisites and all bundled reference files.
  3. Copy the skill directory into a personal or project-level Claude Code skills directory.
  4. Restart or refresh Claude Code so the skill can be discovered.
Verify installation

Ask Claude Code to design a service split and confirm it covers data ownership, timeouts, circuit breakers and tracing.

Prerequisites

  • Outputs are design guidance; no running system is built or tested.
  • The 100 ms synchronous-call threshold is a stated rule of thumb, not validated.
  • Distributed designs add operational overhead the skill does not quantify.

Example prompts

Representative task

Using the microservices-architect skill, decompose our order, inventory and payment monolith into services: show boundaries, sync versus async calls, a saga for checkout and resilience per integration.

Inspect before use

Read the microservices-architect skill at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/microservices-architect/SKILL.md and its reference files. Explain its workflow, any commands it tells the agent to run, and the main risks before I decide whether to install it.

A decision, with its limits attached

Strengths

  • Each design step has an explicit validation checkpoint.
  • Includes short examples for circuit breaker, saga and correlation ID.

Considerations

  • Microservices may be unnecessary for small teams or simple domains.
  • Examples span several languages and need adapting.
Research conclusion

A structured checklist for distributed design that guards against distributed-monolith pitfalls.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

Jeffallanclaude-skillsskills/microservices-architect
Source type
Community
Commit
67c1961b180dc92cf08983344627109e983e8f51
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
MIT
Repository stars
12,464
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.