What problem does it solve? Prisma 7 ships no MongoDB connector, so MongoDB projects on Prisma v6 have no standard upgrade path. This Skill prevents the two common failure modes — advising an impossible Prisma 7 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 8.0+ server floor, tolerance for pre-1.0 breaking changes) that determines whether to migrate to Prisma Next or stay on the latest v6 line. - Mapping References: Detailed v6-to-Next mappings for schema contracts, client API calls (including raw query and transaction equivalents), and the shift from db push to plan/migrate/verify/sign migrations. - 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 intercepts the question, greps the codebase for $transaction usage, checks the MongoDB server version, and produces a staged migration plan to Prisma Next — or a justified stay-on-v6 hygiene plan. ## 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.
