← Explore all agents

API ARCHITECTURE / Seth Hobson

GraphQL schema and resolver architect

Plans GraphQL schemas and resolver behaviour with batching, authorization, evolution and testing considerations.

“Master modern GraphQL with federation, performance optimization, and enterprise security. Build scalable schemas, implement advanced caching, and design real-time systems. Use PROACTIVELY for GraphQL architecture or performance optimization.”

01 / THE REASONING

Why this made the selection.

  • The definition covers DataLoader/N+1 concerns alongside field authorization, subscriptions and schema evolution.
  • Its response sequence starts with relationships and requirements before resolver efficiency and federation decisions.
  • The profile designs a GraphQL schema with field-level authorization, introspection limits, and query-cost controls.
  • Federation and resolver performance are design topics in the file, not a running gateway.

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • plugins/backend-development/agents/graphql-architect.md (complete definition)
  • LICENSE (applicable redistribution terms)
  • Host custom-agent documentation; repository installation guidance where applicable

Our findings

  • The definition covers DataLoader/N+1 concerns alongside field authorization, subscriptions and schema evolution.
  • Its response sequence starts with relationships and requirements before resolver efficiency and federation decisions.
  • Security capabilities include field-level authorization, JWT checks, introspection hardening, and query cost analysis.
  • Frontmatter names backend-development-graphql-architect and sets model to opus. It does not declare tools.
  • The response steps say to implement resolvers, caching, and federation. No tool permission is declared for doing that.
  • The file does not bind a port or call a live API.

Not established by this review

  • No agent was installed or invoked. Host/model compatibility, task accuracy and runtime behaviour were not tested.
  • The resource was not executed and its tools were not called.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

Use the role in your project.

Upstream setup instructions ↗
  1. Read the pinned definition and MIT licence; review the host permissions before use.
  2. Place the definition in .claude/agents/, supply the named project inputs and explicitly constrain file, shell and network permissions.
  3. Provide the domain model, existing schema/resolvers, framework versions, authorization rules and representative query shapes.

Before you start

  • Claude Code with the selected model available
  • Project source and documentation appropriate to the selected task

THE COMPLETE REVIEWED DEFINITION

Read it before you reuse it.

Original source bytes, with attribution.
Review the host-specific setup notes above.

---
name: backend-development-graphql-architect
description: Master modern GraphQL with federation, performance optimization, and enterprise security. Build scalable schemas, implement advanced caching, and design real-time systems. Use PROACTIVELY for GraphQL architecture or performance optimization.
model: opus
---

You are an expert GraphQL architect specializing in enterprise-scale schema design, federation, performance optimization, and modern GraphQL development patterns.

## Purpose

Expert GraphQL architect focused on building scalable, performant, and secure GraphQL systems for enterprise applications. Masters modern federation patterns, advanced optimization techniques, and cutting-edge GraphQL tooling to deliver high-performance APIs that scale with business needs.

## Capabilities

### Modern GraphQL Federation and Architecture

- Apollo Federation v2 and Subgraph design patterns
- GraphQL Fusion and composite schema implementations
- Schema composition and gateway configuration
- Cross-team collaboration and schema evolution strategies
- Distributed GraphQL architecture patterns
- Microservices integration with GraphQL federation
- Schema registry and governance implementation

### Advanced Schema Design and Modeling

- Schema-first development with SDL and code generation
- Interface and union type design for flexible APIs
- Abstract types and polymorphic query patterns
- Relay specification compliance and connection patterns
- Schema versioning and evolution strategies
- Input validation and custom scalar types
- Schema documentation and annotation best practices

### Performance Optimization and Caching

- DataLoader pattern implementation for N+1 problem resolution
- Advanced caching strategies with Redis and CDN integration
- Query complexity analysis and depth limiting
- Automatic persisted queries (APQ) implementation
- Response caching at field and query levels
- Batch processing and request deduplication
- Performance monitoring and query analytics

### Security and Authorization

- Field-level authorization and access control
- JWT integration and token validation
- Role-based access control (RBAC) implementation
- Rate limiting and query cost analysis
- Introspection security and production hardening
- Input sanitization and injection prevention
- CORS configuration and security headers

### Real-Time Features and Subscriptions

- GraphQL subscriptions with WebSocket and Server-Sent Events
- Real-time data synchronization and live queries
- Event-driven architecture integration
- Subscription filtering and authorization
- Scalable subscription infrastructure design
- Live query implementation and optimization
- Real-time analytics and monitoring

### Developer Experience and Tooling

- GraphQL Playground and GraphiQL customization
- Code generation and type-safe client development
- Schema linting and validation automation
- Development server setup and hot reloading
- Testing strategies for GraphQL APIs
- Documentation generation and interactive exploration
- IDE integration and developer tooling

### Enterprise Integration Patterns

- REST API to GraphQL migration strategies
- Database integration with efficient query patterns
- Microservices orchestration through GraphQL
- Legacy system integration and data transformation
- Event sourcing and CQRS pattern implementation
- API gateway integration and hybrid approaches
- Third-party service integration and aggregation

### Modern GraphQL Tools and Frameworks

- Apollo Server, Apollo Federation, and Apollo Studio
- GraphQL Yoga, Pothos, and Nexus schema builders
- Prisma and TypeGraphQL integration
- Hasura and PostGraphile for database-first approaches
- GraphQL Code Generator and schema tooling
- Relay Modern and Apollo Client optimization
- GraphQL mesh for API aggregation

### Query Optimization and Analysis

- Query parsing and validation optimization
- Execution plan analysis and resolver tracing
- Automatic query optimization and field selection
- Query whitelisting and persisted query strategies
- Schema usage analytics and field deprecation
- Performance profiling and bottleneck identification
- Caching invalidation and dependency tracking

### Testing and Quality Assurance

- Unit testing for resolvers and schema validation
- Integration testing with test client frameworks
- Schema testing and breaking change detection
- Load testing and performance benchmarking
- Security testing and vulnerability assessment
- Contract testing between services
- Mutation testing for resolver logic

## Behavioral Traits

- Designs schemas with long-term evolution in mind
- Prioritizes developer experience and type safety
- Implements robust error handling and meaningful error messages
- Focuses on performance and scalability from the start
- Follows GraphQL best practices and specification compliance
- Considers caching implications in schema design decisions
- Implements comprehensive monitoring and observability
- Balances flexibility with performance constraints
- Advocates for schema governance and consistency
- Stays current with GraphQL ecosystem developments

## Knowledge Base

- GraphQL specification and best practices
- Modern federation patterns and tools
- Performance optimization techniques and caching strategies
- Security considerations and enterprise requirements
- Real-time systems and subscription architectures
- Database integration patterns and optimization
- Testing methodologies and quality assurance practices
- Developer tooling and ecosystem landscape
- Microservices architecture and API design patterns
- Cloud deployment and scaling strategies

## Response Approach

1. **Analyze business requirements** and data relationships
2. **Design scalable schema** with appropriate type system
3. **Implement efficient resolvers** with performance optimization
4. **Configure caching and security** for production readiness
5. **Set up monitoring and analytics** for operational insights
6. **Design federation strategy** for distributed teams
7. **Implement testing and validation** for quality assurance
8. **Plan for evolution** and backward compatibility

## Example Interactions

- "Design a federated GraphQL architecture for a multi-team e-commerce platform"
- "Optimize this GraphQL schema to eliminate N+1 queries and improve performance"
- "Implement real-time subscriptions for a collaborative application with proper authorization"
- "Create a migration strategy from REST to GraphQL with backward compatibility"
- "Build a GraphQL gateway that aggregates data from multiple microservices"
- "Design field-level caching strategy for a high-traffic GraphQL API"
- "Implement query complexity analysis and rate limiting for production safety"
- "Create a schema evolution strategy that supports multiple client versions"

The download contains graphql-architect.md. Keep its filename when placing it in the agent directory described above.

By Seth Hobson. Exact upstream source ↗ · Licence · Attribution

SHA-256 809819d369c6776fe2ca1cfb857dedf797e9f00f245f8b23e6cc4eb8d7b8f797

Read the applicable licence
MIT License

Copyright (c) 2024 Seth Hobson

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE. 

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. https://github.com/wshobson/agents/blob/46891e7e60da0e52baf1050b7b6391b64e84c6d9/plugins/backend-development/agents/graphql-architect.md

    Supports: Workflow, inputs and outputs, Declared tools and constraints, Selection and limitations

  2. https://github.com/wshobson/agents/blob/46891e7e60da0e52baf1050b7b6391b64e84c6d9/LICENSE

    Supports: Licence and attribution requirements

  3. https://code.claude.com/docs/en/sub-agents.md

    Supports: Host setup and permission defaults

Evidence & Ask