What it does
The agent analyses GraphQL query performance and proposes optimizations for production APIs. It reads existing resolver code to find N+1 patterns, where a separate database call is made for each record, and rewrites the affected resolvers to use request-scoped DataLoader batching without changing the schema. It also covers caching strategies, such as Automatic Persisted Queries (APQ) combined with CDN caching and field-level cache-control directives.
It suits slow list pages caused by per-record fetches of related data, and high-traffic public or semi-public APIs that need to reduce origin load. APQ turns frequent queries into short GET requests that a CDN can cache, which is useful where Trusted Documents are not feasible, for example with third-party mobile apps. It can also profile slow queries in federated graphs that span several subgraphs, comparing query plans with subgraph response times.
The agent works on the code in your project and checks its changes, for example with before-and-after query counts. The examples in its documentation assume Apollo Server, a Redis store for APQ and a CDN that caches GET responses.
Limitations and requirements
The caching approach assumes a client-controlled API where Trusted Documents are not feasible. The documented examples assume Apollo Server, a Redis APQ store and a CDN able to cache GET-based persisted query responses. The DataLoader changes are made without touching the schema.
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 16 Nov 2026 · its page on the source · figures reported by the source: aitmpl downloads 631
graphql-performance-optimizer
GraphQL performance analysis and optimization specialist. Use PROACTIVELY for query performance issues, N+1 problems, caching strategies, and production GraphQL API optimization. Specifically: <example> Context: An existing resolver file is causing visible slowdowns when loading lists of users with their related orders. user: "Our user list page takes 3–4 seconds to load. Each user has related orders fetched in a separate resolver. Can you diagnose and fix it?" assistant: "I'll scan the resolver file for N+1 patterns, instrument DataLoader batching for the orders relation, and verify the fix
As shown on www.aitmpl.com when we last read it