Design microservices architectures with service boundaries, event-driven communication, and resilience patterns.
NewMaintained
Automatic
◆Coding pack
Last verified 8/29/2026
What it changes
Passed 21 of 22 test cases with the skill, and 21 of 22 without it.
Without skill95%
With skill95%
0 fixed21 passed either way1 still failing0 broke
Pass-rate lift
0 pp
Tokens
+20%
Agent turns
0%
Response time
+11%
Model gemini-3.6-flashMeasured 8/29/2026v121 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
What's inside
The instructions your model reads when the skill loads.
SKILL.md35 linessingle file
Microservices Patterns
Master microservices architecture patterns including service boundaries, inter-service communication, data management, and resilience patterns for building distributed systems.
Use this skill when
Decomposing monoliths into microservices
Designing service boundaries and contracts
Implementing inter-service communication
Managing distributed data and transactions
Building resilient distributed systems
Implementing service discovery and load balancing
Designing event-driven architectures
Do not use this skill when
The system is small enough for a modular monolith
You need a quick prototype without distributed complexity
There is no operational support for distributed systems
Instructions
Identify domain boundaries and ownership for each service.
Define contracts, data ownership, and communication patterns.
Plan resilience, observability, and deployment strategy.
Provide migration steps and operational guardrails.
Resources
resources/implementation-playbook.md for detailed patterns and examples.