Microservices
Use when the user asks about microservices, splitting a monolith, service boundaries, database per service, sagas, service discovery or strangler fig migration. Produces a decomposition and communication plan (or a monolith verdict). Not for DDD modeling (use architecture-domain-driven-design) or Kubernetes setup (use kubernetes).
Install
npx skills add j4flmao/agent-skills --skill microservicesgit clone --depth 1 https://github.com/j4flmao/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/backend/universal/microservices ~/.claude/skills/microservicesPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Microservices Architecture ## Purpose Guide microservices decomposition, communication patterns, data ownership, and migration strategies. ## Agent Protocol ### Trigger User request includes: `microservice`, `micro-services`, `service decomposition`, `distributed system`, `saga`, `cqrs`, `event sourcing`, `service mesh`. ### Input Context - Business domain description / bounded context map - Current monolith architecture (if migrating) - Team topology (Conway's Law) - Non-functional requirements (latency, throughput, consistency, availability) - Technology preferences (message broker, container platform, language) ### Output Artifact A markdown document containing: - Service decomposition model (bounded contexts with responsibilities) - Communication pattern selection (sync/async/event) per service pair - Data ownership strategy (database per service, shared nothing) - Infrastructure recommendations (service mesh, API gateway, message broker) - Migration strategy (strangler fig, parallel run) ### Response Format Produce the artifact directly. No preamble, no postamble, no explanations. No filler, no hedging, no transitions. Strip articles a/an/the where unambiguous. Compress output — why use many token when few do trick. If monolith is appropriate, output `Monolith recommended. Reason: [reason].` and stop. ### Completion Criteria - Decomposition bounded contexts explicitly mapped to business capabilities
Details
- Skill name
microservices- Repository
- j4flmao/agent-skills
- Path
skills/backend/universal/microservices/SKILL.md- License
- MIT
- Repo updated
- 17 November 2026
FAQ
What does the Microservices skill do?
Use when the user asks about microservices, splitting a monolith, service boundaries, database per service, sagas, service discovery or strangler fig migration. Produces a decomposition and communication plan (or a monolith verdict). Not for DDD modeling (use architecture-domain-driven-design) or Kubernetes setup (use kubernetes).
How do I install the Microservices skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add j4flmao/agent-skills --skill microservices. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Microservices popular?
It lives in j4flmao/agent-skills, which has 45 GitHub stars and 6 forks.
Related skills
Agent Observability
45j4flmao/agent-skills
Use when the user asks about agent observability, tracing agent reasoning, debugging an agent loop, OpenTelemetry GenAI spans for LLM calls, LLM cost tracking per agent, agent audit logs or hallucination/eval monitoring in production. Produces instrumentation config, trace schema, dashboards, alerts and cost attribution. Not for generic service tracing without LLMs (use devops-opentelemetry).
AI Agent Architectures
45j4flmao/agent-skills
Use when the user asks to build an AI agent, design an agent that calls tools and keeps memory, write an agent system prompt or pick an agent framework (Claude Agent SDK, OpenAI Agents SDK, LangGraph). Produces an architecture brief covering loop, tools, memory, guardrails and evals, routing depth to child skills. Not for workflow patterns (use ai-agentic-workflows).
AI Agent Core Loop
45j4flmao/agent-skills
Use when the user asks about the agent loop, ReAct vs plan-and-solve, re-planning, Reflexion, an agent stuck in a loop, max iterations or termination conditions. Produces a loop spec or patch with state, success predicate, caps and no-progress detection. Not for overall agent design (use ai-agent-architectures) or tool schemas (use tool-calling-principles).
Monitoring
45j4flmao/agent-skills
Use when the user asks about infrastructure monitoring with Prometheus, Grafana, Loki or ELK, scrape configs and relabeling, Alertmanager routing by severity, Loki label strategy, or node and host metrics. Produces monitoring stack configs and alert routes. Not for Kubernetes ServiceMonitor setup (use prometheus-grafana) or TSDB scaling (use sre-observability-scaling).
Microfrontend
45j4flmao/agent-skills
Use when the user asks to split the web app into independently deployed micro frontends, Module Federation, remoteEntry/mf-manifest, import maps, single-spa, Native Federation, shared singletons or cross-app communication. Produces the composition choice, host/remote config and deployment rules. Not for a single-team monorepo (use monorepo).
Monorepo
45j4flmao/agent-skills
Use when the user asks about monorepos, Nx, Turborepo, nx affected, pnpm/yarn/npm workspaces, remote caching, task pipelines, project graphs, or module boundary rules. Produces workspace layout and build orchestration configs. Not for dependency update bots (use dependency-management) or Git submodules (use advanced-workflows).
Browse the most popular Claude skills, all devops & cloud skills, or write your own with the skills generator.