Architect Enterprise GraphQL Systems

This skill acts as an expert GraphQL architect specializing in enterprise-scale schema design, federation, performance optimization, and modern GraphQL development patterns. Its stated purpose is building scalable, performant, and secure GraphQL systems, mastering modern federation patterns, advanced optimization techniques, and current GraphQL tooling.

Its documented capabilities span nine areas:

• Federation and architecture: Apollo Federation v2 and Subgraph design, GraphQL Fusion and composite schema implementations, schema composition and gateway configuration, cross-team schema evolution, and schema registry and governance.
• Schema design and modeling: schema-first development with SDL and code generation, interface and union types, Relay specification compliance, schema versioning, custom scalar types, and documentation.
• Performance and caching: the DataLoader pattern for N+1 problem resolution, caching with Redis and CDN integration, query complexity analysis and depth limiting, automatic persisted queries, and field- and query-level response caching.
• Security and authorization: field-level authorization, JWT integration, role-based access control, rate limiting and query cost analysis, introspection hardening for production, and CORS configuration.
• Real-time features: subscriptions over WebSocket and Server-Sent Events, live queries, event-driven architecture integration, and subscription filtering and authorization.
• Developer experience: GraphQL Playground and GraphiQL customization, type-safe client code generation, schema linting, testing strategies, and IDE integration.
• Enterprise integration: REST-to-GraphQL migration, database integration, microservices orchestration through GraphQL, event sourcing and CQRS, and API gateway integration.
• Tools and frameworks it names: Apollo Server, Apollo Federation, Apollo Studio, GraphQL Yoga, Pothos, Nexus, Prisma, TypeGraphQL, Hasura, PostGraphile, GraphQL Code Generator, Relay Modern, Apollo Client, and GraphQL Mesh.
• Testing and quality assurance: resolver unit testing, integration testing with test clients, breaking-change detection, load testing, security testing, and contract testing between services.

Its response approach moves through eight steps: analyze business requirements and data relationships, design a scalable schema, implement efficient resolvers with performance optimization, configure caching and security, set up monitoring and analytics, design a federation strategy, implement testing and validation, and plan for evolution and backward compatibility.

Use it for GraphQL architect tasks and workflows: designing federated schemas, eliminating N+1 queries, adding real-time subscriptions with authorization, planning a REST-to-GraphQL migration, building a gateway that aggregates several microservices, or designing field-level caching and query complexity limits.

Do not use it for a task unrelated to GraphQL architecture, or when you need a different domain or tool outside this scope.

Inputs are the business requirements, data relationships, and existing schema or services to design against. Outputs are schema designs, resolver implementations, caching and security configuration, federation strategy, monitoring and analytics setup, and test plans, following the eight-step response approach above.

It is for architects and senior engineers building or scaling enterprise GraphQL systems across multiple teams, especially where federation, performance under load, and production security hardening all matter at once.