tomevault-io GraphQL Schema Design
When To Use
- The main decision is about schema structure, resolver organization, N+1 prevention, or pagination strategy.
- Reviewing mutation design, subscription patterns, or authorization boundaries.
Workflow
- Identify schema structure — does the schema model business capabilities, not database tables?
- Review resolver architecture — are resolvers thin, delegating to service layers?
- Check data loading — is
DataLoaderused to batch and cache database queries? - Review pagination — is the
Connectionpattern used for list fields? - Check mutation design — do mutations follow the input-payload pattern?
- Review authorization — are authorization checks applied at the field/resolver level?
- Recommend the cleanest schema and resolver structure.
Output Format
GraphQL schema review:
- Schema structure:
- Resolver architecture:
- Data loading (DataLoader):
- Pagination:
- Mutation design:
- Authorization:
- Recommended change:
- Verification:
Source: WangYao-GoGoGo/architecture-agent-skills — distributed by TomeVault.