Microservices Skills¶
Composable AI skills that hold your coding assistant to microservices engineering standards — boundary-aware, failure-aware, contract-first. Works with Claude Code, Cursor, Codex and any Agent Skills host.
Ask an AI assistant to "add a call to the pricing service" and you get a working call. You usually do not get a timeout, a circuit breaker, an idempotency key, an authorisation check scoped to the caller, or a test for the path where pricing times out. Nothing is wrong with the code — it is just missing everything that separates a demo from a service someone gets paged about.
Before and after¶
The same prompt — "call the pricing service when an order is placed" — without and with the skills installed. Illustrative, in the style of the worked example's Java stack.
public Order place(PlaceOrder cmd, Caller caller) {
authz.requireCanOrderFor(caller, cmd.customerId()); // secure-service
return idempotency.once(cmd.idempotencyKey(), () -> { // idempotency-and-immutability
Price price = pricing.quote(cmd.sku(), cmd.quantity()); // adapter: 800 ms timeout,
// retry budget, breaker,
// fails closed — resilience-patterns
return orders.save(Order.place(cmd, price)); // invariant lives on Order — domain-modelling
});
}
// + component test for "pricing times out → 503, no order written" — test-strategy
Every comment on the right is a check one of the skills ran before the code was shown to you.
Install in one line¶
claude plugin marketplace add parvez3019/ai-coding-microservices-skills && \
claude plugin install microservices-skills@ai-coding-microservices-skills --yes
Cursor, Codex and other hosts: see Getting Started.
What you get¶
-
16 principles
Guardrails that load automatically: service boundaries, resilience, API contracts, security, testing and more.
-
4 workflows
/design-service→/implement-service→/review-service, plus/refactor-safely. -
1 profile
/stack-profilerecords your language, framework and broker, so every check speaks your team's actual libraries. -
Independent reviewer
A subagent that audits code with no memory of having written it.
Browse all skills See the worked example
Design principles¶
- Checks over advice. "Services should be resilient" changes nothing. "Does this call have an explicit timeout shorter than the caller's deadline? If not, set one derived from the latency budget" changes the output.
- Composability over one big document. Small single-purpose skills load only when relevant; workflows compose them.
- Judgment handed back, not hidden. Sync or async, strong or eventual consistency, split or keep together — every skill lists the calls it must not make silently and routes them back to you with options and a recommendation.