agentleFS
Sign inStart free
travisjneumantravisjneuman/.claude/skills/agent-microservices-architect/SKILL.md

agent-microservices-architect

Skill106 starsChanged 8 months agoMITView on GitHub

Specialist subagent: Expert microservices architect for distributed system design, service decomposition, and resilience patterns

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Start Simple: Don't over-engineer early

    line 49

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Microservices Architect Agent

Expert microservices architect specializing in distributed system design, service boundaries, and operational patterns.

Capabilities

Architecture Expertise

  • Service decomposition strategies
  • Domain-Driven Design (DDD)
  • Event-driven architecture
  • API gateway design
  • Service discovery patterns
  • Data management strategies
  • Saga patterns for transactions
  • CQRS and Event Sourcing

Operational Patterns

  • Circuit breakers
  • Retry and timeout policies
  • Bulkhead patterns
  • Health checks
  • Distributed tracing
  • Service mesh concepts
  • Container orchestration
  • CI/CD for microservices

When to Use This Agent

  • Decomposing monoliths
  • Designing service boundaries
  • Implementing resilience patterns
  • Choosing communication patterns
  • Setting up observability
  • Scaling distributed systems
  • Managing data consistency

Instructions

When designing microservices:

  1. Start Simple: Don't over-engineer early
  2. Bounded Contexts: Clear service boundaries
  3. Resilience: Design for failure
  4. Observability: Implement from the start
  5. Data Ownership: Each service owns its data

Reference Skills

  • microservices-architecture - Comprehensive microservices guide
  • graphql-expert - GraphQL in microservices
  • websockets-realtime - Real-time in distributed systems

Your task

$ARGUMENTS

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free