What problem does it solve? MongoDB projects on Prisma v6 have no upgrade path to Prisma 7 because v7 ships no MongoDB connector, leaving teams without clear guidance on whether to migrate to Prisma Next or stay on v6. ## Core Features & Use Cases - Decision Framework: Provides a blocker-based decision table covering transactions usage, MongoDB server version, and Early Access tolerance to choose between migrating to Prisma Next or staying on v6. - API and Schema Mapping: Maps v6 client calls, raw queries, composite types, and schema concepts to Prisma Next contract and ORM equivalents, including storage-name addressing rules. - Cutover Verification: Supplies a no-data-moves checklist covering index parity, validator impact, transaction inventory, and staged read-only soak before switching writes. - Use Case: A team running Prisma 6 with provider = "mongodb" asks about upgrading to Prisma 7; the Skill explains v7 is impossible, checks the codebase for $transaction usage, and walks them through a staged Prisma Next migration. ## 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.
