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 (transactions usage, MongoDB server version, pre-1.0 tolerance) that determines whether to migrate to Prisma Next or stay on the latest v6 with proper hygiene. - Migration Mappings: Reference guides translating v6 schema concepts (@db.ObjectId, composite types), client API calls ($runCommandRaw, $transaction, aggregations), and the db push workflow into Prisma Next's contract, client, and plan/migrate/verify/sign lifecycle. - Cutover Verification: A 10-step checklist for a no-data-moves cutover — same database, index parity, validator impact, staged read-only soak, and code-only rollback. - Use Case: A team on Prisma 6 with MongoDB asks about upgrading. The Skill greps the codebase for $transaction, checks the MongoDB server version (8.0+ required), then walks them through a staged Prisma Next migration or a pinned v6 stay. ## Quick Start Ask the assistant to evaluate whether your Prisma 6 MongoDB project should migrate to Prisma Next and to check the codebase for migration blockers.
