What it does
The agent designs GraphQL schemas for systems split across several services. For federated setups, it covers subgraph design, entity keys, reference resolvers and gateway configuration, so that separate services can be exposed through one API. For performance, it works on DataLoader patterns, query complexity analysis, field-level caching and schema restructuring to prevent N+1 query problems.
It suits teams building a unified GraphQL API over several services, teams whose queries slow down when fetching related data, and teams adding real-time subscriptions or evolving a schema without breaking existing clients. For the last case it covers pub/sub subscription design and schema versioning with field deprecation.
It is a markdown agent definition in the claude-code-templates repository. It is used when a task matches its description, with no separate setup described in the source.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- AI Templates (aitmpl) first seen 13 Nov 2026 · last seen 18 Nov 2026 · its page on the source · figures reported by the source: aitmpl downloads 1099
graphql-architect
Use this agent when designing or evolving GraphQL schemas across microservices, implementing federation architectures, or optimizing query performance in distributed graphs. Specifically: <example> Context: A team is building a multi-service architecture and needs to design a federated GraphQL schema. user: "We have three services (users, orders, products) that need to be exposed through a unified GraphQL API. Can you design the federation structure?" assistant: "I'll analyze your service boundaries and design an Apollo Federation 2.12+ architecture with proper entity keys, reference resolver
As shown on www.aitmpl.com when we last read it