Guides contract-first data layer development with Prisma Next across contracts, migrations, queries, and runtime wiring.
npx skills add https://github.com/prisma/prisma --skill prisma-8
Please help me install this Agent Skill. Skill: prisma-8 Source: https://github.com/prisma/prisma/tree/main/skills/prisma-8 Command: npx skills add https://github.com/prisma/prisma --skill prisma-8
Prisma Next (Prisma 8) is a new contract-first data layer whose APIs evolve quickly, so AI agents and developers relying on outdated training knowledge produce broken code. This Skill ships version-accurate guidance inside the installed Prisma packages and routes every Prisma Next task to the correct reference file.
Ask your AI agent to help with any Prisma Next task, such as adding a model to your data contract or planning a migration, and it will consult the matching reference file before writing code.
High-intent search queries and answers about installing and using this skill.
Edit the contract source file referenced by prisma.config.ts — contract.prisma (PSL) or contract.ts (TypeScript builder) — then run prisma contract emit to regenerate contract.json and contract.d.ts. Never edit the emitted artifacts directly.
The system plans migrations from the contract diff via migration plan, and you review or edit the generated migration.ts for data transforms before applying with db migrate. Plan origin resolves from --from, then the db ref, then an empty database.
No. This guidance applies only to Prisma Next (Prisma 8) projects using contract.prisma, prisma.config.ts, and @internal/* imports. Projects using schema.prisma with @prisma/client on ORM 7 or earlier are explicitly out of scope.
Prisma Next supports PostgreSQL and SQLite with both a typed SQL query builder (db.sql) and an ORM client (db.orm), plus MongoDB with only the ORM lane addressed by collection storage names. Extensions add pgvector, PostGIS, and Supabase support.
migration plan never chains from the newest migration on disk; without --from or a db ref it plans from an empty database. The CLI refuses this with MIGRATION.PLAN_ORIGIN_UNKNOWN — set a ref with migration ref set or pass --from explicitly.
Read the structured error envelope's code, severity, why, fix, and meta fields, then route on the code — for example PN-CLI-4011 means missing extension packs in the config. For PN-RUN-3000 wrappers, check meta.code for the real underlying error.
nthplusioQuery and mutate data via Prisma Client with type-safe operations.
mattbutlerengineeringAutomate Prisma schema migrations with version-controlled change management.
Impertio-StudioDiagnose and optimize slow MariaDB queries using logs, EXPLAIN, and performance schema.
Sake-TeamAutomate database schema changes and data migrations across PostgreSQL and MySQL.
