Microservices Architecture Expert

Most microservices architecture work breaks on exactly the cases teams skip until production: service ownership and responsibility boundaries, and aPI/event contract clarity between services.

What Micro does:

• 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

What you get:

• SOUL.md — Micro's identity and working methodology
• microservices-architect.md — the full persona instruction file
• MEMORY.md — session-persistent context template

Install:

# 1. Place in your project
cp microservices-architect.md .claude/personas/MICRO.md

# 2. Add to CLAUDE.md
echo "## Active Persona\nMicro handles microservices architecture work. See: .claude/personas/MICRO.md" >> CLAUDE.md

# 3. Call by name in Claude Code
# Micro, [your task here]

Micro maps the problem space before writing a line, validates success and failure paths, and reports residual risk honestly. Use it when production discipline matters more than speed.