Use when working in a project that depends on @prisma/orm-postgres, @prisma/orm-sqlite, or @prisma/orm-mongo (Prisma 8, formerly Prisma Next): editing contract.prisma or a contract.ts builder, running `prisma contract emit`, planning or applying migrations, editing migration.ts, writing db.orm / db.

Prisma 8 (Prisma 8) Edit your data contract. Prisma handles the rest. Prisma 8 moves fast, and your training data about it is very likely outdated. This skill ships inside the installed Prisma packages, so it describes the exact version this project has — treat it and its reference files as the source of truth, over anything you remember about Prisma. Pre conditions Check these before acting on anything below. Halt on the first one that fails and tell the user what is missing. 1. The project is on Prisma 8. prisma.config.ts exports definePrismaConfig({ orm: ... }) , and package.json depends on @prisma/orm postgres , @prisma/orm sqlite , or @prisma/orm mongo . A project with schema.prisma and @prisma/client is Prisma 7 or earlier; this skill does not apply to it, and its instructions will break such a project. 2. The skill matches the installed version. Compare metadata.library version in this file's frontmatter with the installed @prisma/orm version in package.json . If they differ, run prisma skills sync and re read this file before continuing. 3. The contract artefacts exist. contract.json and contract.d.ts sit next to the contract source named by prisma.config.ts . If they are missing or older than the source, run prisma contract emit first; every query and migration instruction below assumes current artefacts. Import paths in the references. The reference files spell façade imports as @internal/<target /<subpath and @internal/extension <name /<subpath . In an application those packages are published as @prisma/orm <target /<subpath ( @prisma/orm postgres/runtime , @prisma/orm mongo/config , @prisma/orm sqlite/runtime ) and @prisma/orm extension <name /<subpath ( @prisma/orm extension pgvector/control ). Write the @prisma/orm name in user code; the two spellings are the same package. Paths already written as @prisma/orm in the references are exact. The metadata.library version in this file's frontmatter is the version it was published with; if it does not match the project's installed Prisma packages, run prisma skills sync and re read. Prisma 8 is a contract first data layer. This skill routes every Prisma 8 task to the right reference file — open the reference before writing code; do not answer from this file alone. The canonical model (one paragraph) You author a data contract (a contract.prisma file, or a TypeScript builder). The framework emits machine readable artifacts ( contract.json , contract.d.ts ) and gives you two runtime surfaces on SQL targets: a typed SQL query builder ( db.sql.<ns .<table ) and a typed ORM client ( db.orm.<ns .<Model ). On MongoDB targets only the ORM lane exists, and its keys are collection storage names ( db.orm.users ) rather than PSL model names — [ references/queries.md ](references/queries.md) § MongoDB ORM addressing covers the rule. Migrations are planned from the contract diff; you review them, optionally edit the migration.ts for data transforms, and apply. Three steps the user does: 1. Edit your data contract. ([ references/contract.md ](references/contract.md)) 2. The system plans the migrations for you. ([ references/migrations.md ](references/migrations.md)) 3. If you need data migrations, you edit migration.ts and execute it. ([ references/migrations.md ](references/migrations.md)) Everything else — queries, runtime wiring, build integration, debugging, feedback — sits on top of those three. One cross cutting migration fact: migration plan does not chain from the newest migration on disk. Its origin is from , else the db ref, else an empty database — so a project with no ref keeps planning from scratch. Over existing migrations the CLI refuses that ( MIGRATION.PLAN ORIGIN UNKNOWN ) instead of writing a full create package; choose the exit that matches your intent rather than reflexively passing from @empty . [ references/migration model.md ](references/migration model.md) § The trap explains which to choose. Routing table Open the reference whose triggers match the task. If more than one matches, open each — they are written to compose. Task Reference Triggers Adopt / set up / first steps [ references/quickstart.md ](references/quickstart.md) new project, existing database, "what can I do with Prisma 8", "where do I start", "just ran createprisma", npx create prisma , first steps, first query, prisma orm init greenfield setup, contract infer + db sign brownfield adoption, connect write read first arc, day to day commands ( contract emit , db init , db update , migration plan , db migrate , db schema , db verify ), flags target / authoring / schema path / probe db / output Edit the data contract [ references/contract.md ](references/contract.md) schema, models, fields, attributes, relations, indexes, enums, value objects (composite types), type aliases, namespaces (Postgres schemas), cross contract foreign keys (cross space FK), polymorphic types ( @@discriminator / @@base ), extension namespaces ( pgvector.Vector(...) , postgis.Geometry(...) ), prisma.config.ts / definePrismaConfig / ormConfig , prisma contract emit , PSL, contract.prisma , contract.ts , contract.json , contract.d.ts , @internal/postgres/config , @internal/postgres/contract builder , @internal/mongo/config , extensions: , pgvector, postgis, paradedb, Temporal / temporal polyfill / RUNTIME.TEMPORAL UNAVAILABLE , @@control , control policy (managed / tolerated / external / observed), soft delete, validations, callbacks Author migrations [ references/migrations.md ](references/migrations.md) db update vs migration plan , db migrate , migration new , migration show , db update dry run , db verify , db sign , data migration, dataTransform , placeholder sentinels in framework rendered migration.ts , MIGRATION.HASH MISMATCH , MIGRATION.UNFILLED PLACEHOLDER , MIGRATION.DESTRUCTIVE CHANGES / confirm <database , schema drift Migration graph, refs, plan origin [ references/migration model.md ](references/migration model.md) migration graph, refs, migration ref set / list / delete , the db ref, advance ref , no advance ref , migration plan from , from: (baseline) in plan output, greenfield / from scratch plan, baseline, first migration before deploy (Composer / CD managed databases), chaining migrations, retrofitting migrations onto an existing database, MIGRATION.HASH NOT IN GRAPH , MIGRATION.PATH UNREACHABLE at plan/chain time Review migrations on deploy [ references/migration review.md ](references/migration review.md) "what migrations are going to run", "what runs on deploy / merge", merge conflict, diamond convergence, concurrent migrations, migration status, ref management for CI, staging / production environment refs, MIGRATION.MARKER NOT IN HISTORY , MIGRATION.MISSING INVARIANTS , MIGRATION.AMBIGUOUS TARGET , db migrate show Write queries [ references/queries.md ](references/queries.md) query, where, select, project, orderBy, limit, offset, take, skip, include, lookup, first, all, count, aggregate, groupBy, create, update, delete, upsert, returning, transaction, db.orm , db.sql , runtime.query(plan) vs runtime.execute(plan) , db.prepare / prepared statements, streaming / for await , many to many include and nested connect , and / or / not from @prisma/orm postgres/orm client , db.query.from(...) (Mongo pipeline), namespace aware accessors, .all() Thenable, single use iterators ( RUNTIME.ITERATOR CONSUMED ), target declared aggregate types ( count , integer sum , and integer avg are number ; count and integer sum throw outside ±(2^53 − 1) rather than round, while avg is a fraction already and carries no guard; countBigInt / sumBigInt / avgDecimal are the lossless forms, avgDecimal on PostgreSQL only), drizzle style, kysely style. Naming types (§ Naming model and result types ): "type of my model", "return type of a query", ResultType , Scalars , Shape , models / Models namespace in contract.d.ts , Models.public User , Prisma 7 Prisma.User / GetPayload / UserGetPayload equivalents. Postgres/SQLite specifics: [ references/queries postgres.md ](references/queries postgres.md); Mongo specifics: [ references/queries mongo.md ](references/queries mongo.md) Wire the runtime [ references/runtime.md ](references/runtime.md) db.ts , postgres<Contract (...) / sqlite<Contract (...) / mongo<Contract (...) façades, middleware composition (lints, budgets, cache via @prisma/orm extension middleware cache , custom afterQuery middleware, @prisma/orm postgres/family runtime ), DATABASE URL , .env , connection pool / poolOptions , dev vs prod config, transactions, read replicas, multi database, script won't exit / hangs, db.close / pool.end , await using / [Symbol.asyncDispose] Build tool integration [ references/build.md ](references/build.md) Vite plugin ( @internal/vite plugin contract emit , Vite 7/8), vite.config.ts , contract emit on save, HMR / dev server, Next.js / Webpack / esbuild / Rollup / Turbopack (named gaps, not fabricated) Supabase [ references/supabase.md ](references/supabase.md) @internal/extension supabase , RLS, row level security, policies ( policy select / policy update / @@rls , auth.uid() ), role binding ( asUser(jwt) / asAnon() / asServiceRole() ), auth.users , cross space FKs to supabase:auth.AuthUser , JWT / JWKS ( SUPABASE JWKS URL , SUPABASE JWT SECRET ), SUPABASE.JWT INVALID , SUPABASE.CONFIG INVALID , RoleBoundDb , session pooler Debug an error [ references/debug.md ](references/debug.md) any structured error envelope (code, severity, why, fix, nextActions, meta), emit failed, query won't typecheck, query crashed, migration won't apply, MIGRATION.HASH MISMATCH , MIGRATION.RUNNER FAILED , BUDGET.ROWS EXCEEDED , BUDGET.TIME EXCEEDED , RUNTIME.ABORTED , RUNTIME.TEMPORAL UNAVAILABLE , PLAN.HASH MISMATCH , CONTRACT.MARKER MISSING , CONFIG. / CLI. / CONTRACT. / MIGRATION. / ORM. / RUNTIME. codes, legacy PN codes, exit code 4 findings, drift, capability missing, planner conflict, EXPLAIN, query log, script won't exit / close connection Upgrade Prisma in an app [ references/upgrade app.md ](references/upgrade app.md) "upgrade Prisma", "upgrade Prisma 8", "bump Prisma 8", "move to Prisma 8 X.Y", @internal/ version bump in an application, per transition upgrade instructions in [ upgrading/app/upgrades/ ](upgrading/app/upgrades/), extension pin pre flight, PN UPGRADE Upgrade Prisma in an extension [ references/upgrade extension.md ](references/upgrade extension.md) the same request in a package that is a Prisma extension ( @internal/contract / SPI dependency, ^@. /extension name), prisma 8 check pins , exact pin rule, per transition instructions in [ upgrading/extension/upgrades/ ](upgrading/extension/upgrades/) File feedback / ask the team [ references/feedback.md ](references/feedback.md) bug report, file an issue, feature request, missing feature, capability gap, "this is broken", surprising behaviour, Q&A / design discussion, ask the Prisma team, Prisma Discord (pris.ly/discord), extension author questions Routing rules If the task clearly matches a row, open that reference directly without asking. For a vague prompt, ask one disambiguating question. Pick from: "Are you new to Prisma 8 and asking what you can do with it, or where to start?" → [ references/quickstart.md ](references/quickstart.md) (first touch orientation path). "Do you want to set up a new Prisma 8 project, or wire it into an existing database?" → [ references/quickstart.md ](references/quickstart.md). "Do you want to edit your data contract (add a model / field / relation), or work with the database (migrations, queries)?" → [ ref

prisma-8