GraphQL Architect guides Claude through schema work in six steps: model the domain, design types with federation directives, validate composition, write resolvers with DataLoader, secure the graph and optimize it. Each step has a recovery note, for example what to check when composition fails or a complexity threshold is exceeded.
Six reference files cover schema design, resolvers, federation, subscriptions, security and a guide for migrating a REST API to GraphQL in phases.
What You Get
- Schema SDL with types, interfaces, unions, enums and input types, documented and deprecated where needed
- Federation subgraphs with entity keys and shared types, and a gateway configuration
- Resolvers that batch lookups with DataLoader, with error handling and cursor pagination
- Subscriptions over WebSocket with Redis pub/sub and filtering
- Depth limits, complexity rules, rate limiting, field-level authorization and query allowlisting
- A phased plan for moving a REST API to GraphQL
Common Use Cases
- Designing a schema for a new product API
- Splitting a monolithic graph into Apollo Federation subgraphs
- Removing N+1 queries from resolvers with DataLoader
- Adding live updates to a graph with subscriptions
- Hardening a public GraphQL endpoint against expensive queries
- Wrapping existing REST endpoints behind a GraphQL layer
What Makes It Unique
Most API skills treat GraphQL as one more transport. This one centers on federation: entity keys, shared value types, interface objects and query planning, with recovery steps when composition fails. It also pairs security with design, so depth and complexity limits and field-level authorization are part of the workflow, and it includes a migration guide that says when not to use GraphQL.
Under The Hood
The skill is a SKILL.md with six reference files and no scripts, and the references load by topic. The agent writes schema files, resolvers and server configuration, and the workflow asks it to check that the schema composes. The migration reference shows a wrapper that calls an existing REST API with fetch, and the examples read JWT secrets, Redis host settings and the environment mode from environment variables, verify tokens and hash passwords. The skill does not tell the agent to run shell commands or browse the web.