forge-graphql-design

What problem does it solve?

This Skill prevents common GraphQL schema design mistakes that cause brittle contracts, cascading nulls, slow list endpoints, and hard-to-evolve APIs once clients rely on them.

Core Features & Use Cases

• Nullability that degrades safely: default to nullable fields and apply non-null deliberately to avoid whole-query failures.
• Relay-style cursor pagination: standardize list access patterns using Connection/Edge/PageInfo to avoid offset pain.
• Typed error unions over thrown exceptions: model expected business failures as part of the schema contract.
• N+1 avoidance with DataLoader: batch “fetch-by-ID” resolver patterns for list-heavy queries.
• Production-ready schema hygiene: use ID instead of String for identifiers, structured money/date scalars, deprecate before removal, cap depth/complexity, and plan persisted queries.
• Use case: when defining a GraphQL API for orders and customers, generate a connection-paginated schema with typed mutation outcomes and DataLoader-backed list resolution that remains stable over time.

Quick Start

Use forge-graphql-design when you are about to write or refactor a GraphQL schema for a production API and want a paste-ready set of schema patterns that enforce safe nullability, Relay pagination, typed error unions, DataLoader batching, and deprecation-first evolution.