Microservices Patterns
Microservice architecture patterns — service decomposition, inter-service communication, API gateway, saga pattern, event-driven architecture, service mesh, circuit breaker, CQRS, event sourcing. Activate on "microservices", "service decomposition", "saga pattern", "API gateway", "event-driven", "service mesh", "circuit breaker", "CQRS", "event sourcing", "bounded context", "strangler fig", "distributed transactions", "choreography vs orchestration". NOT for monolith design, serverless functions, or Kubernetes infrastructure.
Install
/plugin marketplace add curiositech/some_claude_skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add curiositech/some_claude_skills --skill microservices-patternsgit clone --depth 1 https://github.com/curiositech/some_claude_skills.git /tmp/some_claude_skills
mkdir -p ~/.claude/skills
cp -r /tmp/some_claude_skills/.claude/skills/microservices-patterns ~/.claude/skills/microservices-patternsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Microservices Patterns The craft of decomposing systems into independent services and making them work reliably together. Covers decomposition strategies, communication patterns, data ownership, and the resilience patterns that keep a distributed system from cascading into total failure. ## When to Use **Use for**: - Deciding whether to decompose a monolith and where to start - Designing service boundaries using bounded contexts and domain-driven design - Choosing between synchronous (REST/gRPC) and asynchronous (events) communication - Implementing saga pattern for distributed transactions - Designing API gateways and backend-for-frontend (BFF) layers - Applying circuit breaker, bulkhead, and retry patterns - Event sourcing and CQRS design - Service discovery and load balancing strategies **NOT for**: - Monolith internal architecture (use `database-design-patterns`, `api-architect`) - Serverless function design and deployment - Kubernetes infrastructure and deployment configuration (use `terraform-iac-expert`) - Service mesh configuration (Istio, Linkerd) — mention it, not the core focus - Single-service performance optimization (use `performance-profiling`) --- ## Core Decision: Monolith vs Microservices vs Modular Monolith
Details
- Skill name
microservices-patterns- Repository
- curiositech/some_claude_skills
- Path
.claude/skills/microservices-patterns/SKILL.md- License
- MIT
- Repo updated
- 5 November 2026
FAQ
What does the Microservices Patterns skill do?
Microservice architecture patterns — service decomposition, inter-service communication, API gateway, saga pattern, event-driven architecture, service mesh, circuit breaker, CQRS, event sourcing. Activate on "microservices", "service decomposition", "saga pattern", "API gateway", "event-driven", "service mesh", "circuit breaker", "CQRS", "event sourcing", "bounded context", "strangler fig", "distributed transactions", "choreography vs orchestration". NOT for monolith design, serverless functions, or Kubernetes infrastructure.
How do I install the Microservices Patterns skill?
Claude Code plugin: /plugin marketplace add curiositech/some_claude_skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Microservices Patterns popular?
It lives in curiositech/some_claude_skills, which has 272 GitHub stars and 46 forks.
Related skills
Email Composer
272curiositech/some_claude_skills
Draft professional emails for various contexts including business, technical, and customer communication. Use when the user needs help writing emails or composing professional messages.
2000s Visualization Expert
272curiositech/some_claude_skills
Expert in 2000s-era music visualization (Milkdrop, AVS, Geiss) and modern WebGL implementations. Specializes in Butterchurn integration, Web Audio API AnalyserNode FFT data, GLSL shaders for audio-reactive visuals, and psychedelic generative art. Activate on "Milkdrop", "music visualization", "WebGL visualizer", "Butterchurn", "audio reactive", "FFT visualization", "spectrum analyzer". NOT for simple bar charts/waveforms (use basic canvas), video editing, or non-audio visuals.
2026 Legal Research Agent
272curiositech/some_claude_skills
Expert legal research agent for finding and scraping expungement data state by state. Knows authoritative sources, URL patterns, Firecrawl configuration, and 2026 legal landscape. Activate on "find expungement data", "scrape state laws", "legal research", "court URLs", "statute sources", "Clean Slate laws", "automatic expungement research". NOT for interpreting laws (use national-expungement-expert), building UI, or legal advice.
Performance Profiling
272curiositech/some_claude_skills
Application performance profiling and bottleneck identification — Node.js profiling, Chrome DevTools, flame graphs, memory leak detection, CPU profiling, React rendering performance. Activate on "profiling", "performance bottleneck", "flame graph", "memory leak", "slow app", "CPU profiling", "heap snapshot", "React re-renders", "EXPLAIN ANALYZE", "event loop lag", "clinic.js", "Core Web Vitals". NOT for infrastructure monitoring or observability (use logging-observability), load testing (use a load-testing skill), or database schema optimization.
Logging Observability
272curiositech/some_claude_skills
Structured logging, distributed tracing, and metrics for production applications. [What: OpenTelemetry setup, log level strategy, correlation IDs, SLI/SLO alerting thresholds, Grafana dashboard design, PagerDuty integration] [When: setting up production logging, adding observability to a service, debugging distributed systems, designing alerting, implementing traces/metrics/logs] [Keywords: logging, observability, OpenTelemetry, OTel, structured logs, distributed tracing, correlation ID, metrics, Grafana, Prometheus, PagerDuty, Winston, Pino, structlog, log levels, SLI, SLO, alerting] NOT for
Port Daddy
272curiositech/some_claude_skills
Multi-agent coordination daemon for coding agents. Use for deterministic port claims, session tracking, salvage, file claims, notes, pub/sub, tuple-space coordination, background fleets, and debugging multi-agent failures across Claude Code, Codex, Gemini CLI, Cursor, or Windsurf. NOT for production deploy orchestration, Docker or Kubernetes networking, or cloud service discovery.
Browse the most popular Claude skills, all devops & cloud skills, or write your own with the skills generator.