bb-graphql-pothos

What problem does it solve?

GraphQL endpoints often become bloated when resolvers mix business logic with data access. This skill provides rules for building GraphQL queries and mutations using Yoga and Pothos, with thin resolvers that delegate all logic to dedicated services and keep inputs and types outside the resolver code.

Core Features & Use Cases

• Thin resolvers: Resolvers only map HTTP/GQL parameters and return results; no business logic is executed here.
• Clear separation of concerns: Services handle the core logic; resolvers delegate to services, avoiding direct DB access.
• Cross-API guidance: Applies when adding or updating Queries/Mutations or Type definitions across APIs like bruno-brown-bk, internal-api, and orders-api.

Quick Start

Define your GraphQL endpoints using Pothos and Yoga while ensuring all business logic resides in services and the GraphQL layer remains thin.