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 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 covering $transaction usage, MongoDB server version (8.0+ required), and tolerance for pre-1.0 breaking changes, with grep-based codebase checks instead of guesswork. - API and Schema Mappings: Reference tables translating v6 client calls ($runCommandRaw, findRaw, aggregateRaw, $transaction) and schema concepts (@db.ObjectId, composite types, @@map storage names) to Prisma Next equivalents. - Cutover Verification Checklist: A 10-step no-data-moves checklist covering index parity, $jsonSchema validator impact, staged read-only soak, and rollback strategy. - Use Case: A team on Prisma 6 with MongoDB asks whether to upgrade to Prisma 7. The Skill checks their codebase for transaction usage, confirms their MongoDB server version, and walks them through a staged Prisma Next migration 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.
