What problem does it solve? MongoDB projects on Prisma v6 have no upgrade path to Prisma 7, which ships no MongoDB connector. This Skill prevents the two dangerous 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 that greps the codebase for $transaction usage, verifies MongoDB server version (8.0+ required), and assesses team tolerance for pre-1.0 breaking changes. - API Mapping References: Detailed mappings from v6 client calls ($runCommandRaw, findRaw, aggregateRaw, $transaction) to Prisma Next equivalents (mongoRaw, typed pipeline builder, driver sessions). - Cutover Verification Checklist: A 10-step no-data-moves checklist covering index parity, $jsonSchema validator impact, storage-name addressing, and staged read-only soak before cutover. - Use Case: A team on Prisma 6 with MongoDB asks about upgrading to Prisma 7. The Skill intercepts, explains v7 has no MongoDB connector, checks the codebase for transaction blockers, and walks them through a staged Prisma Next migration against the same database. ## Quick Start Ask the assistant whether your Prisma 6 MongoDB project should upgrade to Prisma 7 and have it check your codebase for migration blockers.
