What problem does it solve? Prisma ORM v7 ships no MongoDB connector, leaving MongoDB projects on v6 with no standard upgrade path. This Skill prevents the two common failure modes — advising an impossible v7 upgrade or silently rewriting the app onto SQL — and frames the real decision: migrate to Prisma Next (Early Access MongoDB support) or deliberately stay on v6. ## Core Features & Use Cases - Decision Framework: A blocker-check table (transactions usage, MongoDB server version, tolerance for pre-1.0 breaking changes) that determines whether to migrate to Prisma Next or stay on the latest v6 line. - Concept Mappings: Reference guides translating v6 schema concepts (@db.ObjectId, composite types, @@map storage names), client API calls ($runCommandRaw, findRaw, $transaction), and the db push workflow into Prisma Next's contract, query, and migration models. - Cutover Verification: A 10-step checklist for a no-data-moves migration — same database, index parity, validator impact, staged read-only soak, and a code-only rollback path. - Use Case: A team on Prisma 6 with provider = "mongodb" asks about upgrading to Prisma 7. The Skill intercepts the impossible request, greps the codebase for $transaction usage, checks the MongoDB server version, and produces a staged migration plan to Prisma Next. ## Quick Start Ask the assistant to evaluate whether your Prisma v6 MongoDB project should migrate to Prisma Next and to check the codebase for migration blockers.
