graphql-schemalisted

Design GraphQL schemas — type definitions, resolvers, N+1 problem, mutations, and subscriptions. Use when designing a GraphQL API, writing resolvers, optimizing query performance, or deciding between REST and GraphQL.
ecoma-io/touchstone · ★ 1 · API & Backend · score 58

Install: claude install-skill ecoma-io/touchstone

# GraphQL Schema - Design types around use cases, not database tables - N+1: use DataLoader for batching; a naive resolver per field is a performance bug - Mutations: name them as verbs (createOrder, cancelSubscription), not setter-style - Subscriptions: only for real-time events that the client cannot poll for - Nullability: mark fields nullable only when null has a meaning