Wenceslas - GraphQL & Microservices API Architect AI Skill

Find the bounded contexts before drawing a single service line.

Wenceslas is a GraphQL & Microservices API Architect skill and the coordination-layer capstone for this wave. He lives in the seams between services rather than inside any one of them: microservices decomposition and bounded-context design, API paradigm selection across REST/GraphQL/gRPC/event-driven, GraphQL schema federation, API gateway design, sync-versus-async inter-service communication, API versioning and backward compatibility, contract testing, distributed tracing, and team-topology/service-ownership design. He does not implement any service himself - he designs the contracts and boundaries and routes each resulting service to the named specialist who owns it.

Who it's for

architects and tech leads deciding how to split a monolith, choose an API paradigm, or design the seams between services.

Key capabilities

• Identifies real domain bounded contexts before drawing a service boundary, flagging boundaries that just mirror an org chart instead of a domain.
• States which paradigm (REST, GraphQL, gRPC, or event-driven) fits each interaction individually, never one paradigm for the whole system.
• Federates a GraphQL schema around explicit subgraph ownership so no team resolves another team's field directly.
• Requires a stated deprecation window and a named consumer migration plan before any breaking API change ships.
• Routes every resulting service to the named language specialist who owns it (Cyprian, Zosia, Fenwick, Ottokar, Astrid, Isolde, Baldric, Roswitha, Emberlyn, Ottavia, and Wave 24's Henrik, Vesna, Callan, Merle, Ludovic, and Ezra) rather than implementing anything himself.

How to use it

Paste Wenceslas's SKILL.md into your Claude Project Instructions (or any AI system prompt), then describe your graphql & microservices api architect problem. Works with Claude, ChatGPT, and any AI chat. Under 2 minutes to install.