[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-prisma-prisma-mongodb-upgrade":3,"mdc-6mmu7e-key":37,"related-org-prisma-prisma-mongodb-upgrade":620,"related-repo-prisma-prisma-mongodb-upgrade":789},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":26,"repoUrl":27,"updatedAt":28,"license":29,"forks":30,"topics":31,"repo":32,"sourceUrl":35,"mdContent":36},"prisma-mongodb-upgrade","migrate Prisma MongoDB projects to v6","Decision and migration guide for Prisma ORM MongoDB projects on v6, which have no upgrade path to v7. Use when a MongoDB project asks about upgrading Prisma, when \"upgrade to prisma 7\" comes up in a project with provider = \"mongodb\", or when evaluating a move to Prisma Next. Triggers on \"upgrade prisma mongodb\", \"prisma 7 mongodb\", \"mongodb prisma migration\", \"prisma next mongodb\".",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},"prisma","Prisma","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fprisma.png",[12,16,19,22,25],{"name":13,"slug":14,"type":15},"MongoDB","mongodb","tag",{"name":17,"slug":18,"type":15},"Database","database",{"name":20,"slug":21,"type":15},"Migration","migration",{"name":23,"slug":24,"type":15},"ORM","orm",{"name":9,"slug":8,"type":15},44,"https:\u002F\u002Fgithub.com\u002Fprisma\u002Fskills","2026-07-11T05:35:03.668013","MIT",3,[],{"repoUrl":27,"stars":26,"forks":30,"topics":33,"description":34},[],null,"https:\u002F\u002Fgithub.com\u002Fprisma\u002Fskills\u002Ftree\u002FHEAD\u002Fprisma-mongodb-upgrade","---\nname: prisma-mongodb-upgrade\ndescription: Decision and migration guide for Prisma ORM MongoDB projects on v6, which have no upgrade path to v7. Use when a MongoDB project asks about upgrading Prisma, when \"upgrade to prisma 7\" comes up in a project with provider = \"mongodb\", or when evaluating a move to Prisma Next. Triggers on \"upgrade prisma mongodb\", \"prisma 7 mongodb\", \"mongodb prisma migration\", \"prisma next mongodb\".\nlicense: MIT\nmetadata:\n  author: prisma\n  version: \"0.1.0\"\n---\n\n# Prisma MongoDB Upgrade Path\n\nMongoDB projects are the one Prisma cohort with no road into Prisma 7: **v6 is the terminal\nclassic-ORM major for MongoDB, and v7 never ships a MongoDB connector**. The successor path\nis [Prisma Next](https:\u002F\u002Fgithub.com\u002Fprisma\u002Fprisma-next), where MongoDB support is in Early\nAccess with GA planned after Postgres. This skill frames the real decision — migrate to\nPrisma Next (the encouraged path), or stay on v6 where a hard blocker applies — and carries\nthe migration mechanics.\n\n**Never do either of these:**\n\n- Never advise a MongoDB project to \"upgrade to Prisma 7\". The connector does not exist\n  there. The `prisma-upgrade-v7` guide does not apply to MongoDB projects.\n- Never solve the version question by rewriting the app onto a SQL database. Changing the\n  database engine is a separate, much larger decision that is not yours to make implicitly.\n\n## The version landscape\n\n| Version | MongoDB status |\n|---------|----------------|\n| Prisma ORM v6 | Fully supported (`mongodb` provider); latest 6.x is the current stable path; maintenance line |\n| Prisma ORM v7 | **No MongoDB connector — not an option, ever** |\n| Prisma Next | MongoDB support in **Early Access**, actively developed, GA planned after Postgres — the successor path for MongoDB projects |\n\n## The decision, up front\n\n**Migrating to Prisma Next is the encouraged path.** MongoDB support in Prisma Next is Early\nAccess: functional and moving quickly, with GA planned after Postgres — and the Prisma team\nwants MongoDB users to migrate early and share feedback. The migration mechanics are\ndetailed in the references.\n\n**Staying on the latest v6 remains a legitimate choice where a hard blocker applies** —\nstated plainly: the Next Mongo façade does not wrap transactions yet (the underlying driver\nis available directly; this is expected to change soon), and pre-1.0 minors can carry\nbreaking changes with published upgrade recipes.\n\n### Decision table\n\n| Signal | Direction |\n|--------|-----------|\n| No blockers below apply | Migrate to Next; run the `verify-cutover-checklist` and share feedback with the Prisma team |\n| Greenfield \u002F prototype \u002F internal tool | Migrate to Next |\n| Codebase uses multi-document transactions (`$transaction`) — check with grep, do not ask | Plan raw-driver session equivalents first (see `client-api-mapping`), or stay on v6 until the façade wrapper lands |\n| Team cannot absorb pre-1.0 breaking upgrades between minors | Stay on v6 until GA |\n| Risk-averse but interested | Run a staged Next round-trip on a copy (see `verify-cutover-checklist`), then migrate |\n\nNote: the transactions gap is expected to close soon — this section will be updated when\nfaçade transactions merge in Prisma Next.\n\n### If staying on v6: hygiene (a deliberate stay, not neglect)\n\n- Pin the Prisma packages to the latest 6.x line and keep taking 6.x patch releases.\n- Track Prisma release notes and security advisories for the 6.x line.\n- Keep the classic v6 MongoDB setup: `url = env(\"DATABASE_URL\")` in the schema, `db push`\n  workflow, no SQL driver adapters (see `prisma-database-setup` for the v6 MongoDB shape).\n- Re-evaluate when Prisma Next's MongoDB is GA, or when blockers for trying EA are resolved.\n\n## Reference files\n\n| Reference | What it covers |\n|-----------|----------------|\n| `references\u002Fdecision-stay-or-migrate.md` | The full decision framing, blocker checks, and stay-hygiene detail |\n| `references\u002Fschema-contract-mapping.md` | v6 schema (`mongodb` provider, `@db.ObjectId`, composite types) → Next contract concepts |\n| `references\u002Fclient-api-mapping.md` | v6 client calls → Next equivalents, incl. raw escape hatches and transactions — names map, parity does not |\n| `references\u002Fmigrations-mapping.md` | v6 `db push`-only story → Next's plan\u002Fmigrate\u002Fverify\u002Fsign flow |\n| `references\u002Fverify-cutover-checklist.md` | No-data-moves verification: same DB, index parity, staged round-trip before cutover |\n\n## Verified against\n\nBehavioral claims about Prisma Next in this skill were verified against\n[prisma\u002Fprisma-next](https:\u002F\u002Fgithub.com\u002Fprisma\u002Fprisma-next) at commit\n`a2791c5dd59d579b4b3052942ae7f8fe5e2ee852` (pre-1.0, ~v0.14\u002F0.15 line). Prisma Next moves\nquickly in Early Access: **before acting on any Next-side claim, verify it against the\nversion actually installed** (check the project's `@prisma-next\u002F*` versions and the\nprisma-next skills installed with it). Next's Mongo target requires MongoDB 8.0+ and expects\n`mongodb@^7` as a user-supplied peer dependency.\n\n## Hand-off rule\n\nThis skill is the **discovery bridge**, not a replacement for Prisma Next's own\ndocumentation. After a project switches to Prisma Next, run Prisma Next's `init`\u002Fskill\ninstallation and follow its own skills (quickstart, contract, queries, migrations, runtime)\nfor day-to-day work — do not keep working from this skill's summaries.\n",{"data":38,"body":41},{"name":4,"description":6,"license":29,"metadata":39},{"author":8,"version":40},"0.1.0",{"type":42,"children":43},"root",[44,53,78,86,110,117,200,206,216,226,233,351,356,362,409,415,544,550,594,600],{"type":45,"tag":46,"props":47,"children":49},"element","h1",{"id":48},"prisma-mongodb-upgrade-path",[50],{"type":51,"value":52},"text","Prisma MongoDB Upgrade Path",{"type":45,"tag":54,"props":55,"children":56},"p",{},[57,59,65,67,76],{"type":51,"value":58},"MongoDB projects are the one Prisma cohort with no road into Prisma 7: ",{"type":45,"tag":60,"props":61,"children":62},"strong",{},[63],{"type":51,"value":64},"v6 is the terminal\nclassic-ORM major for MongoDB, and v7 never ships a MongoDB connector",{"type":51,"value":66},". The successor path\nis ",{"type":45,"tag":68,"props":69,"children":73},"a",{"href":70,"rel":71},"https:\u002F\u002Fgithub.com\u002Fprisma\u002Fprisma-next",[72],"nofollow",[74],{"type":51,"value":75},"Prisma Next",{"type":51,"value":77},", where MongoDB support is in Early\nAccess with GA planned after Postgres. This skill frames the real decision — migrate to\nPrisma Next (the encouraged path), or stay on v6 where a hard blocker applies — and carries\nthe migration mechanics.",{"type":45,"tag":54,"props":79,"children":80},{},[81],{"type":45,"tag":60,"props":82,"children":83},{},[84],{"type":51,"value":85},"Never do either of these:",{"type":45,"tag":87,"props":88,"children":89},"ul",{},[90,105],{"type":45,"tag":91,"props":92,"children":93},"li",{},[94,96,103],{"type":51,"value":95},"Never advise a MongoDB project to \"upgrade to Prisma 7\". The connector does not exist\nthere. The ",{"type":45,"tag":97,"props":98,"children":100},"code",{"className":99},[],[101],{"type":51,"value":102},"prisma-upgrade-v7",{"type":51,"value":104}," guide does not apply to MongoDB projects.",{"type":45,"tag":91,"props":106,"children":107},{},[108],{"type":51,"value":109},"Never solve the version question by rewriting the app onto a SQL database. Changing the\ndatabase engine is a separate, much larger decision that is not yours to make implicitly.",{"type":45,"tag":111,"props":112,"children":114},"h2",{"id":113},"the-version-landscape",[115],{"type":51,"value":116},"The version landscape",{"type":45,"tag":118,"props":119,"children":120},"table",{},[121,140],{"type":45,"tag":122,"props":123,"children":124},"thead",{},[125],{"type":45,"tag":126,"props":127,"children":128},"tr",{},[129,135],{"type":45,"tag":130,"props":131,"children":132},"th",{},[133],{"type":51,"value":134},"Version",{"type":45,"tag":130,"props":136,"children":137},{},[138],{"type":51,"value":139},"MongoDB status",{"type":45,"tag":141,"props":142,"children":143},"tbody",{},[144,165,181],{"type":45,"tag":126,"props":145,"children":146},{},[147,153],{"type":45,"tag":148,"props":149,"children":150},"td",{},[151],{"type":51,"value":152},"Prisma ORM v6",{"type":45,"tag":148,"props":154,"children":155},{},[156,158,163],{"type":51,"value":157},"Fully supported (",{"type":45,"tag":97,"props":159,"children":161},{"className":160},[],[162],{"type":51,"value":14},{"type":51,"value":164}," provider); latest 6.x is the current stable path; maintenance line",{"type":45,"tag":126,"props":166,"children":167},{},[168,173],{"type":45,"tag":148,"props":169,"children":170},{},[171],{"type":51,"value":172},"Prisma ORM v7",{"type":45,"tag":148,"props":174,"children":175},{},[176],{"type":45,"tag":60,"props":177,"children":178},{},[179],{"type":51,"value":180},"No MongoDB connector — not an option, ever",{"type":45,"tag":126,"props":182,"children":183},{},[184,188],{"type":45,"tag":148,"props":185,"children":186},{},[187],{"type":51,"value":75},{"type":45,"tag":148,"props":189,"children":190},{},[191,193,198],{"type":51,"value":192},"MongoDB support in ",{"type":45,"tag":60,"props":194,"children":195},{},[196],{"type":51,"value":197},"Early Access",{"type":51,"value":199},", actively developed, GA planned after Postgres — the successor path for MongoDB projects",{"type":45,"tag":111,"props":201,"children":203},{"id":202},"the-decision-up-front",[204],{"type":51,"value":205},"The decision, up front",{"type":45,"tag":54,"props":207,"children":208},{},[209,214],{"type":45,"tag":60,"props":210,"children":211},{},[212],{"type":51,"value":213},"Migrating to Prisma Next is the encouraged path.",{"type":51,"value":215}," MongoDB support in Prisma Next is Early\nAccess: functional and moving quickly, with GA planned after Postgres — and the Prisma team\nwants MongoDB users to migrate early and share feedback. The migration mechanics are\ndetailed in the references.",{"type":45,"tag":54,"props":217,"children":218},{},[219,224],{"type":45,"tag":60,"props":220,"children":221},{},[222],{"type":51,"value":223},"Staying on the latest v6 remains a legitimate choice where a hard blocker applies",{"type":51,"value":225}," —\nstated plainly: the Next Mongo façade does not wrap transactions yet (the underlying driver\nis available directly; this is expected to change soon), and pre-1.0 minors can carry\nbreaking changes with published upgrade recipes.",{"type":45,"tag":227,"props":228,"children":230},"h3",{"id":229},"decision-table",[231],{"type":51,"value":232},"Decision table",{"type":45,"tag":118,"props":234,"children":235},{},[236,252],{"type":45,"tag":122,"props":237,"children":238},{},[239],{"type":45,"tag":126,"props":240,"children":241},{},[242,247],{"type":45,"tag":130,"props":243,"children":244},{},[245],{"type":51,"value":246},"Signal",{"type":45,"tag":130,"props":248,"children":249},{},[250],{"type":51,"value":251},"Direction",{"type":45,"tag":141,"props":253,"children":254},{},[255,276,289,318,331],{"type":45,"tag":126,"props":256,"children":257},{},[258,263],{"type":45,"tag":148,"props":259,"children":260},{},[261],{"type":51,"value":262},"No blockers below apply",{"type":45,"tag":148,"props":264,"children":265},{},[266,268,274],{"type":51,"value":267},"Migrate to Next; run the ",{"type":45,"tag":97,"props":269,"children":271},{"className":270},[],[272],{"type":51,"value":273},"verify-cutover-checklist",{"type":51,"value":275}," and share feedback with the Prisma team",{"type":45,"tag":126,"props":277,"children":278},{},[279,284],{"type":45,"tag":148,"props":280,"children":281},{},[282],{"type":51,"value":283},"Greenfield \u002F prototype \u002F internal tool",{"type":45,"tag":148,"props":285,"children":286},{},[287],{"type":51,"value":288},"Migrate to Next",{"type":45,"tag":126,"props":290,"children":291},{},[292,305],{"type":45,"tag":148,"props":293,"children":294},{},[295,297,303],{"type":51,"value":296},"Codebase uses multi-document transactions (",{"type":45,"tag":97,"props":298,"children":300},{"className":299},[],[301],{"type":51,"value":302},"$transaction",{"type":51,"value":304},") — check with grep, do not ask",{"type":45,"tag":148,"props":306,"children":307},{},[308,310,316],{"type":51,"value":309},"Plan raw-driver session equivalents first (see ",{"type":45,"tag":97,"props":311,"children":313},{"className":312},[],[314],{"type":51,"value":315},"client-api-mapping",{"type":51,"value":317},"), or stay on v6 until the façade wrapper lands",{"type":45,"tag":126,"props":319,"children":320},{},[321,326],{"type":45,"tag":148,"props":322,"children":323},{},[324],{"type":51,"value":325},"Team cannot absorb pre-1.0 breaking upgrades between minors",{"type":45,"tag":148,"props":327,"children":328},{},[329],{"type":51,"value":330},"Stay on v6 until GA",{"type":45,"tag":126,"props":332,"children":333},{},[334,339],{"type":45,"tag":148,"props":335,"children":336},{},[337],{"type":51,"value":338},"Risk-averse but interested",{"type":45,"tag":148,"props":340,"children":341},{},[342,344,349],{"type":51,"value":343},"Run a staged Next round-trip on a copy (see ",{"type":45,"tag":97,"props":345,"children":347},{"className":346},[],[348],{"type":51,"value":273},{"type":51,"value":350},"), then migrate",{"type":45,"tag":54,"props":352,"children":353},{},[354],{"type":51,"value":355},"Note: the transactions gap is expected to close soon — this section will be updated when\nfaçade transactions merge in Prisma Next.",{"type":45,"tag":227,"props":357,"children":359},{"id":358},"if-staying-on-v6-hygiene-a-deliberate-stay-not-neglect",[360],{"type":51,"value":361},"If staying on v6: hygiene (a deliberate stay, not neglect)",{"type":45,"tag":87,"props":363,"children":364},{},[365,370,375,404],{"type":45,"tag":91,"props":366,"children":367},{},[368],{"type":51,"value":369},"Pin the Prisma packages to the latest 6.x line and keep taking 6.x patch releases.",{"type":45,"tag":91,"props":371,"children":372},{},[373],{"type":51,"value":374},"Track Prisma release notes and security advisories for the 6.x line.",{"type":45,"tag":91,"props":376,"children":377},{},[378,380,386,388,394,396,402],{"type":51,"value":379},"Keep the classic v6 MongoDB setup: ",{"type":45,"tag":97,"props":381,"children":383},{"className":382},[],[384],{"type":51,"value":385},"url = env(\"DATABASE_URL\")",{"type":51,"value":387}," in the schema, ",{"type":45,"tag":97,"props":389,"children":391},{"className":390},[],[392],{"type":51,"value":393},"db push",{"type":51,"value":395},"\nworkflow, no SQL driver adapters (see ",{"type":45,"tag":97,"props":397,"children":399},{"className":398},[],[400],{"type":51,"value":401},"prisma-database-setup",{"type":51,"value":403}," for the v6 MongoDB shape).",{"type":45,"tag":91,"props":405,"children":406},{},[407],{"type":51,"value":408},"Re-evaluate when Prisma Next's MongoDB is GA, or when blockers for trying EA are resolved.",{"type":45,"tag":111,"props":410,"children":412},{"id":411},"reference-files",[413],{"type":51,"value":414},"Reference files",{"type":45,"tag":118,"props":416,"children":417},{},[418,434],{"type":45,"tag":122,"props":419,"children":420},{},[421],{"type":45,"tag":126,"props":422,"children":423},{},[424,429],{"type":45,"tag":130,"props":425,"children":426},{},[427],{"type":51,"value":428},"Reference",{"type":45,"tag":130,"props":430,"children":431},{},[432],{"type":51,"value":433},"What it covers",{"type":45,"tag":141,"props":435,"children":436},{},[437,454,486,503,527],{"type":45,"tag":126,"props":438,"children":439},{},[440,449],{"type":45,"tag":148,"props":441,"children":442},{},[443],{"type":45,"tag":97,"props":444,"children":446},{"className":445},[],[447],{"type":51,"value":448},"references\u002Fdecision-stay-or-migrate.md",{"type":45,"tag":148,"props":450,"children":451},{},[452],{"type":51,"value":453},"The full decision framing, blocker checks, and stay-hygiene detail",{"type":45,"tag":126,"props":455,"children":456},{},[457,466],{"type":45,"tag":148,"props":458,"children":459},{},[460],{"type":45,"tag":97,"props":461,"children":463},{"className":462},[],[464],{"type":51,"value":465},"references\u002Fschema-contract-mapping.md",{"type":45,"tag":148,"props":467,"children":468},{},[469,471,476,478,484],{"type":51,"value":470},"v6 schema (",{"type":45,"tag":97,"props":472,"children":474},{"className":473},[],[475],{"type":51,"value":14},{"type":51,"value":477}," provider, ",{"type":45,"tag":97,"props":479,"children":481},{"className":480},[],[482],{"type":51,"value":483},"@db.ObjectId",{"type":51,"value":485},", composite types) → Next contract concepts",{"type":45,"tag":126,"props":487,"children":488},{},[489,498],{"type":45,"tag":148,"props":490,"children":491},{},[492],{"type":45,"tag":97,"props":493,"children":495},{"className":494},[],[496],{"type":51,"value":497},"references\u002Fclient-api-mapping.md",{"type":45,"tag":148,"props":499,"children":500},{},[501],{"type":51,"value":502},"v6 client calls → Next equivalents, incl. raw escape hatches and transactions — names map, parity does not",{"type":45,"tag":126,"props":504,"children":505},{},[506,515],{"type":45,"tag":148,"props":507,"children":508},{},[509],{"type":45,"tag":97,"props":510,"children":512},{"className":511},[],[513],{"type":51,"value":514},"references\u002Fmigrations-mapping.md",{"type":45,"tag":148,"props":516,"children":517},{},[518,520,525],{"type":51,"value":519},"v6 ",{"type":45,"tag":97,"props":521,"children":523},{"className":522},[],[524],{"type":51,"value":393},{"type":51,"value":526},"-only story → Next's plan\u002Fmigrate\u002Fverify\u002Fsign flow",{"type":45,"tag":126,"props":528,"children":529},{},[530,539],{"type":45,"tag":148,"props":531,"children":532},{},[533],{"type":45,"tag":97,"props":534,"children":536},{"className":535},[],[537],{"type":51,"value":538},"references\u002Fverify-cutover-checklist.md",{"type":45,"tag":148,"props":540,"children":541},{},[542],{"type":51,"value":543},"No-data-moves verification: same DB, index parity, staged round-trip before cutover",{"type":45,"tag":111,"props":545,"children":547},{"id":546},"verified-against",[548],{"type":51,"value":549},"Verified against",{"type":45,"tag":54,"props":551,"children":552},{},[553,555,561,563,569,571,576,578,584,586,592],{"type":51,"value":554},"Behavioral claims about Prisma Next in this skill were verified against\n",{"type":45,"tag":68,"props":556,"children":558},{"href":70,"rel":557},[72],[559],{"type":51,"value":560},"prisma\u002Fprisma-next",{"type":51,"value":562}," at commit\n",{"type":45,"tag":97,"props":564,"children":566},{"className":565},[],[567],{"type":51,"value":568},"a2791c5dd59d579b4b3052942ae7f8fe5e2ee852",{"type":51,"value":570}," (pre-1.0, ~v0.14\u002F0.15 line). Prisma Next moves\nquickly in Early Access: ",{"type":45,"tag":60,"props":572,"children":573},{},[574],{"type":51,"value":575},"before acting on any Next-side claim, verify it against the\nversion actually installed",{"type":51,"value":577}," (check the project's ",{"type":45,"tag":97,"props":579,"children":581},{"className":580},[],[582],{"type":51,"value":583},"@prisma-next\u002F*",{"type":51,"value":585}," versions and the\nprisma-next skills installed with it). Next's Mongo target requires MongoDB 8.0+ and expects\n",{"type":45,"tag":97,"props":587,"children":589},{"className":588},[],[590],{"type":51,"value":591},"mongodb@^7",{"type":51,"value":593}," as a user-supplied peer dependency.",{"type":45,"tag":111,"props":595,"children":597},{"id":596},"hand-off-rule",[598],{"type":51,"value":599},"Hand-off rule",{"type":45,"tag":54,"props":601,"children":602},{},[603,605,610,612,618],{"type":51,"value":604},"This skill is the ",{"type":45,"tag":60,"props":606,"children":607},{},[608],{"type":51,"value":609},"discovery bridge",{"type":51,"value":611},", not a replacement for Prisma Next's own\ndocumentation. After a project switches to Prisma Next, run Prisma Next's ",{"type":45,"tag":97,"props":613,"children":615},{"className":614},[],[616],{"type":51,"value":617},"init",{"type":51,"value":619},"\u002Fskill\ninstallation and follow its own skills (quickstart, contract, queries, migrations, runtime)\nfor day-to-day work — do not keep working from this skill's summaries.",{"items":621,"total":788},[622,638,653,666,679,693,709,720,736,747,758,774],{"slug":623,"name":623,"fn":624,"description":625,"org":626,"tags":627,"stars":636,"repoUrl":70,"updatedAt":637},"prisma-next","guide Prisma Next project setup and usage","Route a vague Prisma Next prompt to the right specific skill. Use for \"help me with Prisma Next\", \"what is Prisma Next\", \"explain Prisma Next\", \"I'm new to PN\", \"where do I start\", \"what can I do with Prisma Next\", \"what can I do next with Prisma\", \"just ran createprisma\", \"tour of Prisma Next\", \"Prisma Next overview\", and comparison questions like \"Prisma Next vs Prisma 7\", \"PN vs Drizzle\", \"PN vs Kysely\", \"PN vs TypeORM\". Do NOT use when the prompt clearly matches a workflow skill — adoption \u002F quickstart \u002F first-touch orientation \u002F brownfield introspection, schema \u002F contract editing, migration authoring (db update \u002F migration plan \u002F migrate), migration review on deploy \u002F concurrent migrations, queries \u002F db.orm \u002F db.sql \u002F TypedSQL, Supabase \u002F RLS \u002F role binding, runtime \u002F db.ts \u002F middleware wiring, build \u002F Vite plugin \u002F Next.js plugin, debug \u002F structured error envelopes \u002F PN-* error codes, or feedback \u002F bug report \u002F feature request — load that sibling skill directly.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[628,629,632,633],{"name":17,"slug":18,"type":15},{"name":630,"slug":631,"type":15},"Next.js","next-js",{"name":9,"slug":8,"type":15},{"name":634,"slug":635,"type":15},"TypeScript","typescript",415,"2026-07-17T05:32:04.322957",{"slug":639,"name":639,"fn":640,"description":641,"org":642,"tags":643,"stars":636,"repoUrl":70,"updatedAt":652},"prisma-next-build","integrate Prisma Next into build systems","Wire Prisma Next into the project's build system with the right build-tool plugin — Vite today via @prisma-next\u002Fvite-plugin-contract-emit (Vite 7 \u002F 8); Next.js \u002F Webpack \u002F esbuild \u002F Rollup \u002F Turbopack are named as gaps rather than fabricated. Always offers the Vite plugin proactively when the project is using Vite. Use for vite plugin, vite-plugin, vite.config.ts, prismaVitePlugin, contract emit on save, HMR, hot reload contract, dev server, Next.js plugin, next plugin, withPrismaNext, webpack plugin, esbuild plugin, rollup plugin, build integration, dev server plugin, vite 7, vite 8.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[644,647,648,649],{"name":645,"slug":646,"type":15},"Deployment","deployment",{"name":630,"slug":631,"type":15},{"name":9,"slug":8,"type":15},{"name":650,"slug":651,"type":15},"Vite","vite","2026-07-02T07:31:36.108254",{"slug":654,"name":654,"fn":655,"description":656,"org":657,"tags":658,"stars":636,"repoUrl":70,"updatedAt":665},"prisma-next-contract","edit Prisma Next data contracts and models","Edit the Prisma Next data contract — add models, fields, relations, indexes, enums, value objects (composite types), type aliases, namespaces (Postgres schemas), cross-contract foreign keys (cross-space FK), polymorphic types (`@@discriminator` \u002F `@@base`), use extension namespaces (`pgvector.Vector(...)`, `cipherstash.EncryptedString(...)`), wire `prisma-next.config.ts` with `defineConfig` from the `@prisma-next\u002F\u003Ctarget>\u002Fconfig` façade, and run `prisma-next contract emit`. Use for schema, models, fields, attributes, soft delete, paranoid, scopes, validations, callbacks, prisma schema, PSL, contract.prisma, contract.ts, contract.json, contract.d.ts, `@prisma-next\u002Fpostgres\u002Fconfig`, `@prisma-next\u002Fpostgres\u002Fcontract-builder`, `@prisma-next\u002Fpostgres\u002Fcontrol`, `@prisma-next\u002Fmongo\u002Fconfig`, `@prisma-next\u002Fmongo\u002Fcontract-builder`, `extensions:`, pgvector, cipherstash, postgis, paradedb, supabase, `@prisma-next\u002Fextension-supabase`, `@@control`, control policy, managed, tolerated, external, observed.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[659,662,663,664],{"name":660,"slug":661,"type":15},"Data Modeling","data-modeling",{"name":17,"slug":18,"type":15},{"name":9,"slug":8,"type":15},{"name":634,"slug":635,"type":15},"2026-07-30T05:30:10.426962",{"slug":667,"name":667,"fn":668,"description":669,"org":670,"tags":671,"stars":636,"repoUrl":70,"updatedAt":678},"prisma-next-debug","debug and recover from Prisma Next errors","Read a Prisma Next structured error envelope and route to the right recovery — code, domain, severity, why, fix, meta. Use for error, exception, my emit failed, my query won't typecheck, my query crashed, my migration won't apply, MIGRATION.HASH_MISMATCH, BUDGET.ROWS_EXCEEDED, BUDGET.TIME_EXCEEDED, RUNTIME.ABORTED, PLAN.HASH_MISMATCH, CONTRACT.MARKER_MISSING, PN-RUN-3001, PN-RUN-3002, PN-RUN-3030, PN-MIG-2001, PN-CLI-4011, PN-SCHEMA-0001, drift, capability missing, planner conflict, prisma studio, EXPLAIN, query log, db.end, db.close, script won't exit, hangs, close connection, pool.end, client is closed.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[672,673,676,677],{"name":17,"slug":18,"type":15},{"name":674,"slug":675,"type":15},"Debugging","debugging",{"name":630,"slug":631,"type":15},{"name":9,"slug":8,"type":15},"2026-07-24T05:37:10.436314",{"slug":680,"name":680,"fn":681,"description":682,"org":683,"tags":684,"stars":636,"repoUrl":70,"updatedAt":692},"prisma-next-feedback","report Prisma Next issues and feedback","Hand a Prisma Next question or report off to the team — file a GitHub issue (bug or feature request), or route Q&A \u002F design discussion \u002F direct-team-contact to the Prisma Discord at pris.ly\u002Fdiscord. Use for bug, bug report, file an issue, report a bug, feature request, missing feature, this should be a feature, file this, this is a bug, this is broken, surprising behaviour, this doesn't work, file feedback, send feedback, capability gap, file via prisma-next-feedback, ask the team, talk to the team, talk to the Prisma team, talk to Prisma, Discord, Prisma Discord, Q&A, design feedback, is this the intended way, how should I do X, extension author question, extension author needs help.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[685,688,691],{"name":686,"slug":687,"type":15},"Documentation","documentation",{"name":689,"slug":690,"type":15},"GitHub","github",{"name":9,"slug":8,"type":15},"2026-07-02T07:31:34.870809",{"slug":694,"name":694,"fn":695,"description":696,"org":697,"tags":698,"stars":636,"repoUrl":70,"updatedAt":708},"prisma-next-migration-review","review and resolve Prisma Next migrations","Review what Prisma Next migrations will run on merge or deploy, render the migration graph, resolve concurrent \u002F diamond-convergence conflicts, and configure environment refs for CI. Use for \"what migrations are going to run\", \"what runs on deploy\", merge conflict, diamond convergence, concurrent migrations, migration status, ref management, staging, production, MIGRATION.DIVERGED, MIGRATION.NO_MARKER, MIGRATION.MARKER_NOT_IN_HISTORY, prisma migrate status, prisma migrate diff, prisma migrate resolve.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[699,702,705,706,707],{"name":700,"slug":701,"type":15},"CI\u002FCD","ci-cd",{"name":703,"slug":704,"type":15},"Code Review","code-review",{"name":17,"slug":18,"type":15},{"name":20,"slug":21,"type":15},{"name":9,"slug":8,"type":15},"2026-07-24T05:37:11.422323",{"slug":710,"name":710,"fn":711,"description":712,"org":713,"tags":714,"stars":636,"repoUrl":70,"updatedAt":719},"prisma-next-migrations","author and manage Prisma Next migrations","Author Prisma Next migrations — choose db update vs migration plan, edit the framework-rendered migration.ts (replace placeholder sentinels with dataTransform closures), recover from MIGRATION.HASH_MISMATCH or PN-MIG-2001 unfilled placeholder. Use for prisma migrate dev, prisma migrate deploy, prisma db push, db update, db update --dry-run, migration plan, migrate, migration new, migration show, db verify, db sign, data migration, this.dataTransform, dataTransform, placeholder, generated migration.ts, edit migration.ts, MIGRATION.HASH_MISMATCH, schema drift.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[715,716,717,718],{"name":17,"slug":18,"type":15},{"name":20,"slug":21,"type":15},{"name":9,"slug":8,"type":15},{"name":634,"slug":635,"type":15},"2026-07-24T05:37:13.469138",{"slug":721,"name":721,"fn":722,"description":723,"org":724,"tags":725,"stars":636,"repoUrl":70,"updatedAt":735},"prisma-next-queries","write Prisma Next queries for database operations","Write Prisma Next queries for Postgres, SQLite, or Mongo — pick a lane (Postgres\u002FSQLite `db.orm.\u003CModel>` + `db.sql.\u003Ctable>`; Mongo `db.orm.\u003Croot>` + `db.query.from(...)` pipeline builder), filter \u002F project \u002F sort \u002F paginate, eager-load with `.include(...)`, Postgres\u002FSQLite `db.transaction(...)`, Postgres\u002FSQLite ORM `.aggregate(...)`, Mongo aggregations via query builder, namespace-aware accessors (`db.orm.\u003Cns>.\u003CModel>`, `db.sql.\u003Cns>.\u003Ctable>`). Triggers: query, where, match, select, project, orderBy, take, skip, include, lookup, first, all, count, aggregate, group, create, update, delete, upsert, returning, transaction, db.close, script teardown, variant, polymorphism, drizzle-style, kysely-style. Notes: `.all()` is a Thenable (just `await` it), iterators are single-use (`RUNTIME.ITERATOR_CONSUMED`), Postgres `count` is `number` while sum\u002Favg\u002Fmin\u002Fmax are `number | null`, ranges use chained `.where()` or `and(...)` (no `.between(...)`).",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[726,727,728,731,732],{"name":17,"slug":18,"type":15},{"name":630,"slug":631,"type":15},{"name":729,"slug":730,"type":15},"PostgreSQL","postgresql",{"name":9,"slug":8,"type":15},{"name":733,"slug":734,"type":15},"SQL","sql","2026-07-17T05:32:03.35373",{"slug":737,"name":737,"fn":738,"description":739,"org":740,"tags":741,"stars":636,"repoUrl":70,"updatedAt":746},"prisma-next-quickstart","adopt Prisma Next in projects","Adopt Prisma Next into a new project, onto an existing database, or as the first move after a bootstrap tool dropped you into a scaffold. Use for \"what can I do with Prisma Next\", \"what can I do next with Prisma\", \"where do I start\", \"what should I do first\", \"just ran createprisma\", \"createprisma\", \"npx createprisma\", \"npx create-prisma\", \"first steps\", \"first query\", \"I have a scaffolded Prisma Next project what now\"; for `pnpm dlx prisma-next init` greenfield setup; and for `prisma-next contract infer` + `db sign` against an existing database. Also covers the connect-write-read first-arc orientation, the day-to-day commands (`contract emit`, `db init`, `db update`, `migration plan`, `migrate`, `db schema`, `db verify`), and routing to `prisma-next-contract` \u002F `prisma-next-queries` \u002F `prisma-next-runtime` for the next move. Flags: --target, --authoring, --schema-path, --probe-db, --output.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[742,743,744,745],{"name":17,"slug":18,"type":15},{"name":23,"slug":24,"type":15},{"name":9,"slug":8,"type":15},{"name":634,"slug":635,"type":15},"2026-07-24T05:37:12.462072",{"slug":748,"name":748,"fn":749,"description":750,"org":751,"tags":752,"stars":636,"repoUrl":70,"updatedAt":757},"prisma-next-runtime","configure Prisma Next runtime and database connections","Wire the Prisma Next runtime — `db.ts` setup using `postgres\u003CContract>(...)` from `@prisma-next\u002Fpostgres\u002Fruntime`, `sqlite\u003CContract>(...)` from `@prisma-next\u002Fsqlite\u002Fruntime`, or `mongo\u003CContract>(...)` from `@prisma-next\u002Fmongo\u002Fruntime`; middleware composition (telemetry from `@prisma-next\u002Fmiddleware-telemetry`; lints and budgets), `DATABASE_URL` config, per-environment branching, switching between Postgres, SQLite, and Mongo façades. Use for db.ts, postgres(), sqlite(), mongo(), middleware, telemetry, lints, budgets, DATABASE_URL, .env, connection pool, poolOptions, dev vs prod config, transactions, db.transaction, read replicas, multi-database, script won't exit, hangs, close connection, db.end, db.close, pool.end, [Symbol.asyncDispose], await using.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[753,754,755,756],{"name":17,"slug":18,"type":15},{"name":630,"slug":631,"type":15},{"name":729,"slug":730,"type":15},{"name":9,"slug":8,"type":15},"2026-07-17T05:32:05.347316",{"slug":759,"name":759,"fn":760,"description":761,"org":762,"tags":763,"stars":636,"repoUrl":70,"updatedAt":773},"prisma-next-supabase","integrate Prisma with Supabase","Use Prisma Next with a Supabase project via `@prisma-next\u002Fextension-supabase` — wire `extensions: [supabasePack]`, declare cross-space FKs to `supabase:auth.AuthUser`, author RLS policies (`policy_select` \u002F `policy_update` \u002F `@@rls`, `auth.uid()` predicates), build `db.ts` with the `supabase()` factory, bind roles per request (`asUser(jwt)` \u002F `asAnon()` \u002F `asServiceRole()`), query `auth.*` \u002F `storage.*` via the `db.asServiceRole().supabase` admin root, and validate JWTs (`jwksUrl` for current projects \u002F `jwtSecret` for legacy HS256). Use for supabase, RLS, row level security, policy, role binding, anon, authenticated, service_role, auth.users, auth.uid(), JWT, JWKS, SUPABASE_JWKS_URL, SUPABASE_JWT_SECRET, SUPABASE.JWT_INVALID, SUPABASE.CONFIG_INVALID, RoleBoundDb, session pooler, supabase:auth.AuthUser, @prisma-next\u002Fextension-supabase.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[764,767,768,769,770],{"name":765,"slug":766,"type":15},"Auth","auth",{"name":23,"slug":24,"type":15},{"name":729,"slug":730,"type":15},{"name":9,"slug":8,"type":15},{"name":771,"slug":772,"type":15},"Supabase","supabase","2026-07-30T05:30:11.065251",{"slug":775,"name":775,"fn":776,"description":777,"org":778,"tags":779,"stars":26,"repoUrl":27,"updatedAt":787},"prisma-cli","run Prisma CLI commands","Prisma ORM CLI commands reference covering init, generate, migrate, db, dev, studio, validate, format, debug, and mcp. Use for ORM\u002Fdatabase CLI workflows, not Prisma Compute app deployment. For Prisma Compute, `@prisma\u002Fcli app deploy`, `compute:deploy`, `create-prisma --deploy`, apps, deployments, logs, or domains, use the `prisma-compute` skill instead. Triggers on \"prisma init\", \"prisma generate\", \"prisma migrate\", \"prisma db\", \"prisma studio\", \"prisma mcp\".",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[780,783,784,785,786],{"name":781,"slug":782,"type":15},"CLI","cli",{"name":17,"slug":18,"type":15},{"name":20,"slug":21,"type":15},{"name":23,"slug":24,"type":15},{"name":9,"slug":8,"type":15},"2026-04-06T18:48:29.140467",21,{"items":790,"total":875},[791,799,813,826,839,853,861],{"slug":775,"name":775,"fn":776,"description":777,"org":792,"tags":793,"stars":26,"repoUrl":27,"updatedAt":787},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[794,795,796,797,798],{"name":781,"slug":782,"type":15},{"name":17,"slug":18,"type":15},{"name":20,"slug":21,"type":15},{"name":23,"slug":24,"type":15},{"name":9,"slug":8,"type":15},{"slug":800,"name":800,"fn":801,"description":802,"org":803,"tags":804,"stars":26,"repoUrl":27,"updatedAt":812},"prisma-client-api","write database queries with Prisma Client","Prisma Client API reference covering model queries, filters, operators, and client methods. Use when writing database queries, using CRUD operations, filtering data, or configuring Prisma Client. Triggers on \"prisma query\", \"findMany\", \"create\", \"update\", \"delete\", \"$transaction\".",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[805,808,809,810,811],{"name":806,"slug":807,"type":15},"API Development","api-development",{"name":17,"slug":18,"type":15},{"name":23,"slug":24,"type":15},{"name":9,"slug":8,"type":15},{"name":634,"slug":635,"type":15},"2026-04-06T18:48:31.666695",{"slug":814,"name":814,"fn":815,"description":816,"org":817,"tags":818,"stars":26,"repoUrl":27,"updatedAt":825},"prisma-compute","deploy and host Prisma applications","Prisma Compute deployment and hosting guide. Use whenever the user mentions Prisma Compute, `prisma.compute.ts`, `defineComputeConfig`, deploying or hosting a Prisma app, `@prisma\u002Fcli app deploy`, `compute:deploy`, `create-prisma --deploy`, `PRISMA_SERVICE_TOKEN`, `auth workspace`, Compute apps\u002Fdeployments\u002Fbuild logs\u002Fdomains, `@prisma\u002Fcli agent install`, `@prisma\u002Fcli feedback`, localhost vs `0.0.0.0`, deploy port binding, or framework deploy readiness for Hono, Elysia, Next.js, TanStack Start, Astro, Nuxt, Svelte, Nest, Turborepo, or custom\u002Fprebuilt artifacts.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[819,820,821,822],{"name":645,"slug":646,"type":15},{"name":23,"slug":24,"type":15},{"name":9,"slug":8,"type":15},{"name":823,"slug":824,"type":15},"Serverless","serverless","2026-07-17T05:31:53.370495",{"slug":401,"name":401,"fn":827,"description":828,"org":829,"tags":830,"stars":26,"repoUrl":27,"updatedAt":838},"configure Prisma with database providers","Guides for configuring Prisma with different database providers (PostgreSQL, MySQL, SQLite, MongoDB, etc.). Use when setting up a new project, changing databases, or troubleshooting connection issues. Triggers on \"configure postgres\", \"connect to mysql\", \"setup mongodb\", \"sqlite setup\".",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[831,832,835,836,837],{"name":17,"slug":18,"type":15},{"name":833,"slug":834,"type":15},"MySQL","mysql",{"name":23,"slug":24,"type":15},{"name":729,"slug":730,"type":15},{"name":9,"slug":8,"type":15},"2026-04-06T18:48:34.192852",{"slug":840,"name":840,"fn":841,"description":842,"org":843,"tags":844,"stars":26,"repoUrl":27,"updatedAt":852},"prisma-driver-adapter-implementation","implement Prisma driver adapters","Required reference for Prisma v7 driver adapter work. Use when implementing or modifying adapters, adding database drivers, or touching SqlDriverAdapter\u002FTransaction interfaces. Contains critical contract details not inferable from code examples — including the transaction lifecycle protocol, error mapping requirements, and verification checklist. Existing implementations do not replace this skill.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[845,846,849,850,851],{"name":17,"slug":18,"type":15},{"name":847,"slug":848,"type":15},"Engineering","engineering",{"name":23,"slug":24,"type":15},{"name":9,"slug":8,"type":15},{"name":634,"slug":635,"type":15},"2026-04-06T18:48:35.478693",{"slug":4,"name":4,"fn":5,"description":6,"org":854,"tags":855,"stars":26,"repoUrl":27,"updatedAt":28},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[856,857,858,859,860],{"name":17,"slug":18,"type":15},{"name":20,"slug":21,"type":15},{"name":13,"slug":14,"type":15},{"name":23,"slug":24,"type":15},{"name":9,"slug":8,"type":15},{"slug":862,"name":862,"fn":863,"description":864,"org":865,"tags":866,"stars":26,"repoUrl":27,"updatedAt":874},"prisma-postgres","manage Prisma Postgres databases","Prisma Postgres setup and operations guidance across Console, create-db CLI, Management API, and Management API SDK. Use when creating Prisma Postgres databases, working in Prisma Console, provisioning with create-db\u002Fcreate-pg\u002Fcreate-postgres, or integrating programmatic provisioning with service tokens or OAuth.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[867,868,869,870,871],{"name":781,"slug":782,"type":15},{"name":17,"slug":18,"type":15},{"name":729,"slug":730,"type":15},{"name":9,"slug":8,"type":15},{"name":872,"slug":873,"type":15},"SDK","sdk","2026-07-17T05:31:52.398028",9]