adding-entity-types

Automate entity setup by defining a Zod schema for validation, creating GraphQL operations with gql.tada, building a repository layer for data access, implementing a service layer, adding bulk mutations for large-scale operations, and writing Vitest tests with MSW mocks. The Skill guides you through all seven steps end-to-end, from schema to deployment integration.

Structure GraphQL operations using gql.tada for type safety and typed queries/mutations. Pair these with a repository pattern that provides a clear data access layer. This separation ensures your operations stay independent from business logic, making tests and maintenance straightforward while supporting bulk mutations and chunked processing.

Bulk mutations in this workflow handle large-scale operations through chunked processing—dividing requests into manageable batches. The Skill covers how to structure these mutations within your service layer, integrate them with your repository pattern, and test them using Vitest and MSW to ensure reliability at scale.

Yes. Zod schemas provide runtime and type-safe validation for entities, while GraphQL operations remain independent. Both validate at different layers—Zod at the data boundary and GraphQL at the API contract—giving you dual protection. The Skill shows how to combine them in a cohesive workflow.

Use Vitest for unit and integration tests paired with MSW for mocking GraphQL requests. This combination lets you test entity creation, repository queries, service logic, and bulk mutation behavior in isolation without hitting a live API, ensuring your new entities work correctly before deployment.

The Skill includes deployment pipeline steps that let you add new entities as part of your release process. This ensures schema migrations, GraphQL operation registration, and service initialization happen consistently across environments.