What problem does it solve? Rewriting a production REST API as GraphQL in one shot is risky and disruptive. This Skill guides an incremental migration that wraps existing REST endpoints behind a GraphQL layer, so existing clients keep working while new consumers adopt GraphQL. ## Core Features & Use Cases - REST Data Source Wrapping: Implements Apollo RESTDataSource classes with auth headers, caching, and cache invalidation on mutations. - Schema and Resolver Generation: Maps REST endpoints to GraphQL types, queries, and mutations, including data transformers between snake_case REST payloads and camelCase GraphQL fields. - N+1 Prevention and Error Mapping: Uses DataLoader for batched resolution and maps HTTP status codes to GraphQL error codes like UNAUTHENTICATED and NOT_FOUND. - Use Case: A team with a large Express REST API wants GraphQL for a new mobile app. They wrap users, posts, and comments endpoints with RESTDataSource, stitch subschemas into a gateway, then migrate hot paths to direct database access phase by phase. ## Quick Start Ask the assistant to migrate your REST API to GraphQL incrementally, starting by wrapping your existing endpoints with Apollo RESTDataSource and generating the corresponding schema and resolvers.
