Prisma Next (Prisma 8)

Edit your data contract. Prisma handles the rest.

The canonical model (one paragraph)

contract.prisma

contract.json

contract.d.ts

db.sql.<ns>.<table>

db.orm.<ns>.<Model>

db.orm.users

references/queries.md

migration.ts

1. Edit your data contract. (

   references/contract.md

   )
2. The system plans the migrations for you. (

   references/migrations.md

   )
3. If you need data migrations, you edit

   migration.ts

   and execute it. (

   references/migrations.md

   )

Routing table

references/quickstart.md

npx create-prisma

prisma-next init

contract infer

db sign

contract emit

db init

db update

migration plan

migrate

db schema

db verify

--target

--authoring

--schema-path

--probe-db

--output

references/contract.md

@@discriminator

@@base

pgvector.Vector(...)

cipherstash.EncryptedString(...)

prisma-next.config.ts

defineConfig

prisma-next contract emit

contract.prisma

contract.ts

contract.json

contract.d.ts

@internal/postgres/config

@internal/postgres/contract-builder

@internal/mongo/config

extensions:

@@control

references/migrations.md

db update

migration plan

migrate

migration new

migration show

db update --dry-run

db verify

db sign

dataTransform

migration.ts

MIGRATION.HASH_MISMATCH

references/migration-review.md

MIGRATION.DIVERGED

MIGRATION.NO_MARKER

MIGRATION.MARKER_NOT_IN_HISTORY

migrate status

migrate diff

migrate resolve

references/queries.md

db.orm

db.sql

db.query.from(...)

.all()

RUNTIME.ITERATOR_CONSUMED

count

sum

avg

number

count

sum

avg

countBigInt

sumBigInt

avgDecimal

avgDecimal

references/queries-postgres.md

references/queries-mongo.md

references/runtime.md

db.ts

postgres<Contract>(...)

sqlite<Contract>(...)

mongo<Contract>(...)

DATABASE_URL

.env

poolOptions

db.close

pool.end

await using

[Symbol.asyncDispose]

references/build.md

@internal/vite-plugin-contract-emit

vite.config.ts

references/supabase.md

@internal/extension-supabase

policy_select

policy_update

@@rls

auth.uid()

asUser(jwt)

asAnon()

asServiceRole()

auth.users

supabase:auth.AuthUser

SUPABASE_JWKS_URL

SUPABASE_JWT_SECRET

SUPABASE.JWT_INVALID

SUPABASE.CONFIG_INVALID

RoleBoundDb

references/debug.md

MIGRATION.HASH_MISMATCH

BUDGET.ROWS_EXCEEDED

BUDGET.TIME_EXCEEDED

RUNTIME.ABORTED

PLAN.HASH_MISMATCH

CONTRACT.MARKER_MISSING

references/feedback.md

Routing rules

• "Are you new to Prisma Next and asking what you can do with it, or where to start?" →

  references/quickstart.md

  (first-touch orientation path).
• "Do you want to set up a new Prisma Next project, or wire it into an existing database?" →

  references/quickstart.md

  .
• "Do you want to edit your data contract (add a model / field / relation), or work with the database (migrations, queries)?" →

  references/contract.md

  vs the others.
• "Is this about authoring a migration, or about reviewing what's going to run on deploy?" →

  references/migrations.md

  vs

  references/migration-review.md

  .
• "Is this about wiring Prisma Next into your build tool (Vite / Next.js / …), or about wiring

  db.ts

  and middleware at runtime?" →

  references/build.md

  vs

  references/runtime.md

  .
• "What error or symptom are you seeing?" →

  references/debug.md

  .
• "Do you want to report this as a bug to the Prisma Next team, or is this a feature request?" →

  references/feedback.md

  .

Checklist

• If the task matches a routing-table row, open that reference before writing code.
• If the prompt is vague, ask one disambiguating question.
• Do not attempt to answer from this file alone — the references carry the verified tool surface.
• If the user describes a missing feature or a misbehaviour they want fixed, open

  references/feedback.md

  .