prisma-relation-debugging

What problem does it solve?

This Skill eliminates frustrating runtime and schema generation errors caused by mismatches between explicit @relation field definitions in Prisma schemas and incorrect relation syntax in application code, as well as errors from inconsistent named relation usage when adding new relations to models with existing named relations.

Core Features & Use Cases

• Diagnose common Prisma errors: Identifies root causes for errors like Unknown argument 'X' on create/update operations, missing argument errors, prisma generate validation failures for missing opposite relation fields, and type mismatches between relation and scalar field usage.
• Fix input type mismatches: Guides correct use of Prisma's CreateInput vs UncheckedCreateInput types to resolve errors from mixing flat foreign key columns with nested relation connect syntax, and catches latent bugs from unsafe as never casts that suppress type checking.
• Resolve named relation conflicts: Fixes prisma generate errors caused by inconsistent @relation naming when adding new relations to models that already use explicit named relations, preventing downstream runtime 500 errors and broken API endpoints.
• Use Case: A developer adding a new updatedBy relation to a User model that already has a named aiConfigUpdates relation can use this Skill to quickly identify the missing matching @relation name on the opposite model and fix the schema error before it breaks the generated Prisma client and production API routes.

Quick Start

Use this skill to debug a Prisma Argument X is missing error on a model create call by checking if the code uses the correct relation connect syntax or UncheckedCreateInput cast for flat foreign key fields.