Microservices Architect
Use when designing distributed systems, decomposing a monolith, reviewing service boundaries, or choosing synchronous/asynchronous communication, data ownership, resilience, and observability patterns.
Install
npx skills add sandbaseai/workbuddy-skill --skill microservices-architectgit clone --depth 1 https://github.com/sandbaseai/workbuddy-skill.git /tmp/workbuddy-skill
mkdir -p ~/.claude/skills
cp -r /tmp/workbuddy-skill/skills/microservices-architect ~/.claude/skills/microservices-architectPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Microservices Architect ## Purpose and boundary Design independently evolvable services only when the operational and domain benefits justify their complexity. Do not split a system because a diagram looks cleaner. An architecture proposal does not authorize creating services, changing schemas, routing traffic, or migrating production data. ## Inputs and decision criteria Gather domain vocabulary, change ownership, user journeys, current modules, API/event contracts, data stores, traffic/latency, failure history, deployment topology, team ownership, compliance, and recovery requirements. Make these explicit: - bounded contexts, invariants, aggregate and transaction boundaries; - synchronous latency/deadline requirements and asynchronous delivery/ordering needs; - data ownership, consistency model, idempotency, replay, deletion, and migration compatibility; - failure domains, retries, timeouts, rate limits, circuit breakers, bulkheads, fallbacks, and load shedding; - trace/log/metric correlation, health/readiness, rollout, rollback, capacity, and on-call ownership; - the cost of network hops, serialization, duplication, operational tooling, and eventual consistency. Mark assumptions and unresolved evidence. “Database per service” and “always async” are useful patterns, not universal laws; justify exceptions against invariants and failure behavior. ## Core workflow
Details
- Skill name
microservices-architect- Repository
- sandbaseai/workbuddy-skill
- Path
skills/microservices-architect/SKILL.md- License
- MIT
- Repo updated
- 8 September 2026
FAQ
What does the Microservices Architect skill do?
Use when designing distributed systems, decomposing a monolith, reviewing service boundaries, or choosing synchronous/asynchronous communication, data ownership, resilience, and observability patterns.
How do I install the Microservices Architect skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add sandbaseai/workbuddy-skill --skill microservices-architect. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Microservices Architect popular?
It lives in sandbaseai/workbuddy-skill, which has 9 GitHub stars and 3 forks.
Related skills
Access Control Security Best Practices
9sandbaseai/workbuddy-skill
Design, review, implement, and verify least-privilege access controls across users, services, tenants, resources, and administrative workflows.
Accessibility Review
9sandbaseai/workbuddy-skill
Use when reviewing a web interface or interaction for semantic, keyboard, focus, screen-reader, ARIA, and contrast accessibility risks.
Acquire Codebase Knowledge
9sandbaseai/workbuddy-skill
Use when the user asks to map, document, or onboard into an existing codebase and needs evidence-backed architecture, structure, conventions, integrations, testing, and concerns documentation.
Monitoring Observability
9sandbaseai/workbuddy-skill
Use when defining service objectives, instrumenting metrics, logs, or traces, designing dashboards and alerts, or auditing whether telemetry supports reliable diagnosis; ground every signal in a user journey and an operational response.
Kubernetes Operations
9sandbaseai/workbuddy-skill
Use when designing, reviewing, deploying, or diagnosing Kubernetes manifests, Helm charts, Kustomize overlays, policies, workloads, or cluster behavior; establish the real cluster context and require a reviewed diff before production mutation.
Multi Stage Dockerfile
9sandbaseai/workbuddy-skill
Use when creating or reviewing reproducible, minimal, and secure multi-stage Dockerfiles for an application or service.
Browse the most popular Claude skills, all devops & cloud skills, or write your own with the skills generator.