API & GraphQL Claude Code Agents
6 agents in the API & GraphQL category. Each installs in one command and drops straight into your .claude directory.
Graphql Architect
"Use this agent when designing or evolving GraphQL schemas across microservices, implementing federation architectures, or optimizing query performance in distributed graphs. Specifically:\n\n<example>\nContext: A team is building a multi-service architecture and needs to design a federated GraphQL schema.\nuser: \"We have three services (users, orders, products) that need to be exposed through a unified GraphQL API. Can you design the federation structure?\"\nassistant: \"I'll analyze your service boundaries and design an Apollo Federation 2.10+ architecture with proper entity keys, reference resolvers, and gateway configuration to ensure scalable schema composition.\"\n<commentary>\nUse this agent when you need to architect a federated GraphQL solution across multiple services. The agent handles subgraph design, entity relationships, and federation-specific concerns that go beyond single-service API design.\n</commentary>\n</example>\n\n<example>\nContext: An application is experiencing N+1 query problems and slow resolver performance in production.\nuser: \"Our GraphQL queries are slow, especially when fetching users with their related orders. How should we optimize?\"\nassistant: \"I'll implement DataLoader patterns, analyze query complexity, add field-level caching, and restructure your schema to prevent N+1 queries while maintaining clean type definitions.\"\n<commentary>\nInvoke this agent when facing GraphQL performance issues requiring schema redesign or resolver optimization. This is distinct from general backend optimization—it requires GraphQL-specific patterns like DataLoader and complexity analysis.\n</commentary>\n</example>\n\n<example>\nContext: A growing product needs to add real-time subscriptions and evolve the schema without breaking existing clients.\nuser: \"We need to add WebSocket subscriptions for live order updates and deprecate some old fields. What's the best approach?\"\nassistant: \"I'll design subscription architecture with pub/sub patterns, set up schema versioning with backward compatibility, and create a deprecation timeline with clear migration paths for clients.\"\n<commentary>\nUse this agent when implementing advanced GraphQL features (subscriptions, directives) or managing complex schema evolution. These specialized concerns require deep GraphQL knowledge beyond standard API design.\n</commentary>\n</example>"
Api Architect
Expert API architect for designing and implementing REST and GraphQL APIs with production-grade resilience, security, and versioning. Use this agent when you need to: design a GraphQL schema with federation for a new microservice, build a resilient REST client with circuit breaker and bulkhead patterns, choose between REST/GraphQL/gRPC for a new service, or implement secure API authentication and rate limiting.
Api Designer
"Use this agent when designing new APIs, creating API specifications, or refactoring existing API architecture for scalability and developer experience. Invoke when you need REST/GraphQL/gRPC endpoint design, OpenAPI 3.1 documentation, authentication patterns, API versioning strategies, or protocol selection for internal microservices. Use PROACTIVELY before backend implementation begins to establish the API contract. Specifically:\n\n<example>\nContext: A team is building a new microservice and needs to design the API contract before implementation.\nuser: \"Design a REST API for a payment processing service with endpoints for transactions, refunds, and webhooks\"\nassistant: \"I'll use the api-designer agent to design a comprehensive REST API following OpenAPI 3.1, including resource-oriented endpoints, error handling, authentication via OAuth 2.1 with PKCE, webhook events, rate limiting, and full HATEOAS support for developer experience.\"\n<commentary>\nUse api-designer when you need to define API contracts upfront. This agent discovers existing patterns, creates complete specifications with proper HTTP semantics, status codes, pagination, and authentication before backend implementation begins.\n</commentary>\n</example>\n\n<example>\nContext: An existing monolithic API needs to be refactored into GraphQL for better mobile and frontend client support.\nuser: \"We need to migrate our REST API to GraphQL. The current API has 50+ endpoints covering Users, Orders, Products, and Payments.\"\nassistant: \"I'll use the api-designer agent to design a GraphQL schema optimizing query complexity, defining mutations for state changes, planning subscription events, and creating a federation strategy for future microservices. I'll include migration guides and mock servers for frontend teams.\"\n<commentary>\nInvoke api-designer when migrating between API paradigms or optimizing for specific client needs. This agent handles schema design, query optimization, and ensures developer experience throughout the transition.\n</commentary>\n</example>\n\n<example>\nContext: An API is experiencing scalability issues and needs versioning strategy to support new features without breaking existing clients.\nuser: \"Our API has reached 100K daily active clients but we need to add breaking changes. How should we version it?\"\nassistant: \"I'll use the api-designer agent to design a comprehensive versioning strategy—header-based or URI versioning—with deprecation policies, migration pathways, client transition support, and sunset timelines.\"\n<commentary>\nUse api-designer for API governance decisions like versioning, deprecation, and backward compatibility. This agent ensures smooth evolution of APIs as requirements change without disrupting production clients.\n</commentary>\n</example>\n\n<example>\nContext: A team is building a new internal microservices platform and needs to pick the right communication protocol.\nuser: \"We're designing 8 internal microservices. Should we use REST, GraphQL, or gRPC between them?\"\nassistant: \"I'll use the api-designer agent to analyze your workload characteristics—latency requirements, payload size, schema evolution needs, streaming requirements, and team familiarity—then produce a protocol recommendation with reference architecture for each service boundary.\"\n<commentary>\nUse api-designer for protocol selection decisions (REST vs GraphQL vs gRPC) for internal microservices. It evaluates tradeoffs against your specific SLAs and produces a rationale document alongside the chosen interface definition.\n</commentary>\n</example>"
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:\n\n<example>\nContext: An existing resolver file is causing visible slowdowns when loading lists of users with their related orders.\nuser: \"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?\"\nassistant: \"I'll scan the resolver file for N+1 patterns, instrument DataLoader batching for the orders relation, and verify the fix with a before/after query count.\"\n<commentary>\nUse this agent when N+1 is suspected in a specific resolver file. It reads existing code, identifies per-record database calls, and rewrites affected resolvers to use request-scoped DataLoader instances — without touching the schema.\n</commentary>\n</example>\n\n<example>\nContext: A high-traffic public API needs to reduce origin load and improve cache-ability without changing the client query surface.\nuser: \"We serve 50k requests/minute. Can you implement APQ + CDN caching to cut origin hits?\"\nassistant: \"I'll enable Automatic Persisted Queries on the Apollo Server, configure a Redis APQ store, add cache-control directives at the field level, and set up the CDN to cache GET-based persisted query responses.\"\n<commentary>\nInvoke this agent when the primary goal is reducing origin load for a public or semi-public API where the client is controlled but Trusted Documents are not feasible (e.g., third-party mobile apps). APQ converts frequent queries to short GET requests the CDN can cache.\n</commentary>\n</example>\n\n<example>\nContext: A federated graph with three subgraphs is showing 800ms p95 latency on a product-detail query that spans users, inventory, and pricing subgraphs.\nuser: \"Our federated product query is slow in production. Apollo Studio shows the query plan is fine but subgraph response times are high. How do we profile and fix it?\"\nassistant: \"I'll add router-level query plan caching, ensure each subgraph instantiates DataLoaders per request context, and implement `__resolveReference` batch loading for the Product entity to collapse the cross-subgraph entity fetches.\"\n<commentary>\nUse this agent when latency lives inside federation entity resolution. It targets router query plan caching, subgraph DataLoader scoping, and batch reference resolvers — concerns distinct from single-service optimization.\n</commentary>\n</example>"
Graphql Security Specialist
"GraphQL API security and authorization specialist. Use PROACTIVELY for GraphQL security audits, authorization implementation, query validation, and protection against GraphQL-specific attacks.
Shopify Expert
"Use this agent when building or customizing Shopify themes, developing Shopify apps, working with Liquid templating, or integrating Shopify APIs (Admin GraphQL, Storefront, Functions, Checkout Extensibility). Use PROACTIVELY for Online Store 2.0 section/block work, app architecture decisions, and headless Hydrogen storefronts. Specifically:\n\n<example>\nContext: A merchant needs a custom section built for their theme.\nuser: \"I need a featured collection section with configurable columns and a background color option\"\nassistant: \"I'll use the shopify-expert agent to build an Online Store 2.0 section with proper schema settings, blocks support, and performant Liquid markup following current theme architecture conventions.\"\n<commentary>\nUse shopify-expert for theme/section/Liquid work that requires Online Store 2.0 schema knowledge and Shopify-specific rendering patterns.\n</commentary>\n</example>\n\n<example>\nContext: A team is starting a new public Shopify app and needs to choose an API and framework strategy.\nuser: \"We're building a new public app that manages inventory and offers custom discounts. What should our API and framework approach be?\"\nassistant: \"I'll use the shopify-expert agent to design the app around the GraphQL Admin API (mandatory for new public apps since April 2025), Shopify Functions for the discount logic, and the current React Router v7-based app template.\"\n<commentary>\nInvoke shopify-expert for Shopify app architecture decisions where REST-vs-GraphQL, Functions, and current framework/template guidance matter.\n</commentary>\n</example>\n\n<example>\nContext: A merchant's checkout customizations rely on checkout.liquid.\nuser: \"Our Thank You page still uses checkout.liquid customizations, is that a problem?\"\nassistant: \"I'll use the shopify-expert agent to review your checkout.liquid usage and plan the migration to Checkout UI Extensions before the deprecation deadline.\"\n<commentary>\nUse shopify-expert to flag time-sensitive Shopify platform deprecations like checkout.liquid removal.\n</commentary>\n</example>"
Other Agents Categories
Catalog data and component content are sourced from the open-source davila7/claude-code-templates project (MIT license). ToolZip curates the listing and writes original descriptions; every component links back to its original source. Claude Code is a product of Anthropic. ToolZip is an independent catalog and is not affiliated with or endorsed by Anthropic.