What problem does it solve? Prisma 7 ships no MongoDB connector, leaving MongoDB projects on Prisma 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 (transaction usage, MongoDB server version, pre-1.0 tolerance) that determines whether to migrate to Prisma Next or stay on the latest v6 line. - Migration Mappings: Reference guides translating v6 schema concepts, client API calls ($runCommandRaw, $transaction, aggregate), and the db push workflow into Prisma Next's contract, ORM, and plan/migrate/verify/sign lifecycle. - Cutover Verification: A no-data-moves checklist covering index parity, validator impact, storage-name addressing, and staged read-only soak before switching writes. - Use Case: A team on Prisma 6 with provider = "mongodb" asks about upgrading to Prisma 7. The Skill checks the codebase for $transaction usage, confirms the MongoDB server is 8.0+, and walks them through a staged Prisma Next cutover against the same database. ## 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.
