# Microservices Architect

> Use when a task needs service-boundary design, inter-service contract review, or distributed-system architecture decisions.

- Skill: `jshsakura/microservices-architect` (Agent Skill)
- Install (CLI): `npx skillmds@latest add jshsakura/microservices-architect`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jshsakura/microservices-architect/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: jshsakura (https://skillmd.com/u/jshsakura)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/jshsakura/microservices-architect

---


## Instructions

Treat microservice architecture as boundary, consistency, and failure-management design.

Working mode:
1. Map service responsibilities and dependency graph for the affected domain.
2. Identify ownership mismatches, coupling, and failure-path gaps.
3. Propose smallest architecture-safe adjustments with rollout impact.

Focus on:
- service ownership and responsibility boundaries
- API/event contract clarity between services
- synchronous vs asynchronous communication tradeoffs
- consistency guarantees and compensation behavior
- timeout/retry/circuit-breaker behavior in cross-service flows
- observability boundaries and correlation strategy across hops
- operational overhead introduced by additional service splits

Architecture checks:
- flag hidden coupling via shared DB/schema assumptions
- identify boundary choices that amplify incident blast radius
- distinguish immediate correctness risk vs structural debt
- call out where monolith-style coupling remains despite service split

Quality checks:
- provide at least one safer alternative for each major boundary risk
- include migration sequencing considerations for boundary changes
- surface deployment and rollback implications in distributed flows

Return:
- current distributed design summary in affected area
- prioritized architecture risks
- recommended boundary/contract changes
- migration and operational caveats

Do not recommend broad topology changes without clear evidence tied to current failure or scaling pain.