[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A03CSV3ARE0T192ASN9G2Y":3,"skill-same:01M7A03CSV3ARE0T192ASN9G2Y":71},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7A03CSV3ARE0T192ASN9G2Y","prisma-mongodb-upgrade",null,"Decision and migration guide for Prisma ORM MongoDB projects on v6, which have no upgrade path to v7. Use when a MongoDB project asks about upgrading Prisma, when \"upgrade to prisma 7\" comes up in a project with provider = \"mongodb\", or when evaluating a move to Prisma Next. Triggers on \"upgrade prisma mongodb\", \"prisma 7 mongodb\", \"mongodb prisma migration\", \"prisma next mongodb\".","Yousuf-Wizdan\u002Fexpense-flow","Yousuf-Wizdan","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F139041819?v=4","01M7A01QGA9T4VSH6ZSS903K18","yousuf_wizdan","01M7A01QGX8XKH0X9KZJVDM9VN",0,"MIT","https:\u002F\u002Fgithub.com\u002FYousuf-Wizdan\u002Fexpense-flow\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fprisma-mongodb-upgrade\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: prisma-mongodb-upgrade\ndescription: Decision and migration guide for Prisma ORM MongoDB projects on v6, which have no upgrade path to v7. Use when a MongoDB project asks about upgrading Prisma, when \"upgrade to prisma 7\" comes up in a project with provider = \"mongodb\", or when evaluating a move to Prisma Next. Triggers on \"upgrade prisma mongodb\", \"prisma 7 mongodb\", \"mongodb prisma migration\", \"prisma next mongodb\".\nlicense: MIT\nmetadata:\n  author: prisma\n  version: \"0.1.0\"\n---\n\n# Prisma MongoDB Upgrade Path\n\nMongoDB projects are the one Prisma cohort with no road into Prisma 7: **v6 is the terminal\nclassic-ORM major for MongoDB, and v7 never ships a MongoDB connector**. The successor path\nis [Prisma Next](https:\u002F\u002Fgithub.com\u002Fprisma\u002Fprisma-next), where MongoDB support is in Early\nAccess with GA planned after Postgres. This skill frames the real decision — migrate to\nPrisma Next (the encouraged path), or stay on v6 where a hard blocker applies — and carries\nthe migration mechanics.\n\n**Never do either of these:**\n\n- Never advise a MongoDB project to \"upgrade to Prisma 7\". The connector does not exist\n  there. The `prisma-upgrade-v7` guide does not apply to MongoDB projects.\n- Never solve the version question by rewriting the app onto a SQL database. Changing the\n  database engine is a separate, much larger decision that is not yours to make implicitly.\n\n## The version landscape\n\n| Version | MongoDB status |\n|---------|----------------|\n| Prisma ORM v6 | Fully supported (`mongodb` provider); latest 6.x is the current stable path; maintenance line |\n| Prisma ORM v7 | **No MongoDB connector — not an option, ever** |\n| Prisma Next | MongoDB support in **Early Access**, actively developed, GA planned after Postgres — the successor path for MongoDB projects |\n\n## The decision, up front\n\n**Migrating to Prisma Next is the encouraged path.** MongoDB support in Prisma Next is Early\nAccess: functional and moving quickly, with GA planned after Postgres — and the Prisma team\nwants MongoDB users to migrate early and share feedback. The migration mechanics are\ndetailed in the references.\n\n**Staying on the latest v6 remains a legitimate choice where a hard blocker applies** —\nstated plainly: the Next Mongo façade does not wrap transactions yet (the underlying driver\nis available directly; this is expected to change soon), and pre-1.0 minors can carry\nbreaking changes with published upgrade recipes.\n\n### Decision table\n\n| Signal | Direction |\n|--------|-----------|\n| No blockers below apply | Migrate to Next; run the `verify-cutover-checklist` and share feedback with the Prisma team |\n| Greenfield \u002F prototype \u002F internal tool | Migrate to Next |\n| Codebase uses multi-document transactions (`$transaction`) — check with grep, do not ask | Plan raw-driver session equivalents first (see `client-api-mapping`), or stay on v6 until the façade wrapper lands |\n| Team cannot absorb pre-1.0 breaking upgrades between minors | Stay on v6 until GA |\n| Risk-averse but interested | Run a staged Next round-trip on a copy (see `verify-cutover-checklist`), then migrate |\n\nNote: the transactions gap is expected to close soon — this section will be updated when\nfaçade transactions merge in Prisma Next.\n\n### If staying on v6: hygiene (a deliberate stay, not neglect)\n\n- Pin the Prisma packages to the latest 6.x line and keep taking 6.x patch releases.\n- Track Prisma release notes and security advisories for the 6.x line.\n- Keep the classic v6 MongoDB setup: `url = env(\"DATABASE_URL\")` in the schema, `db push`\n  workflow, no SQL driver adapters (see `prisma-database-setup` for the v6 MongoDB shape).\n- Re-evaluate when Prisma Next's MongoDB is GA, or when blockers for trying EA are resolved.\n\n## Reference files\n\n| Reference | What it covers |\n|-----------|----------------|\n| `references\u002Fdecision-stay-or-migrate.md` | The full decision framing, blocker checks, and stay-hygiene detail |\n| `references\u002Fschema-contract-mapping.md` | v6 schema (`mongodb` provider, `@db.ObjectId`, composite types) → Next contract concepts |\n| `references\u002Fclient-api-mapping.md` | v6 client calls → Next equivalents, incl. raw escape hatches and transactions — names map, parity does not |\n| `references\u002Fmigrations-mapping.md` | v6 `db push`-only story → Next's plan\u002Fmigrate\u002Fverify\u002Fsign flow |\n| `references\u002Fverify-cutover-checklist.md` | No-data-moves verification: same DB, index parity, staged round-trip before cutover |\n\n## Verified against\n\nBehavioral claims about Prisma Next in this skill were verified against\n[prisma\u002Fprisma-next](https:\u002F\u002Fgithub.com\u002Fprisma\u002Fprisma-next) at commit\n`a2791c5dd59d579b4b3052942ae7f8fe5e2ee852` (pre-1.0, ~v0.14\u002F0.15 line). Prisma Next moves\nquickly in Early Access: **before acting on any Next-side claim, verify it against the\nversion actually installed** (check the project's `@prisma-next\u002F*` versions and the\nprisma-next skills installed with it). Next's Mongo target requires MongoDB 8.0+ and expects\n`mongodb@^7` as a user-supplied peer dependency.\n\n## Hand-off rule\n\nThis skill is the **discovery bridge**, not a replacement for Prisma Next's own\ndocumentation. After a project switches to Prisma Next, run Prisma Next's `init`\u002Fskill\ninstallation and follow its own skills (quickstart, contract, queries, migrations, runtime)\nfor day-to-day work — do not keep working from this skill's summaries.\n","# Prisma MongoDB Upgrade Path\n\nMongoDB projects are the one Prisma cohort with no road into Prisma 7: **v6 is the terminal\nclassic-ORM major for MongoDB, and v7 never ships a MongoDB connector**. The successor path\nis [Prisma Next](https:\u002F\u002Fgithub.com\u002Fprisma\u002Fprisma-next), where MongoDB support is in Early\nAccess with GA planned after Postgres. This skill frames the real decision — migrate to\nPrisma Next (the encouraged path), or stay on v6 where a hard blocker applies — and carries\nthe migration mechanics.\n\n**Never do either of these:**\n\n- Never advise a MongoDB project to \"upgrade to Prisma 7\". The connector does not exist\n  there. The `prisma-upgrade-v7` guide does not apply to MongoDB projects.\n- Never solve the version question by rewriting the app onto a SQL database. Changing the\n  database engine is a separate, much larger decision that is not yours to make implicitly.\n\n## The version landscape\n\n| Version | MongoDB status |\n|---------|----------------|\n| Prisma ORM v6 | Fully supported (`mongodb` provider); latest 6.x is the current stable path; maintenance line |\n| Prisma ORM v7 | **No MongoDB connector — not an option, ever** |\n| Prisma Next | MongoDB support in **Early Access**, actively developed, GA planned after Postgres — the successor path for MongoDB projects |\n\n## The decision, up front\n\n**Migrating to Prisma Next is the encouraged path.** MongoDB support in Prisma Next is Early\nAccess: functional and moving quickly, with GA planned after Postgres — and the Prisma team\nwants MongoDB users to migrate early and share feedback. The migration mechanics are\ndetailed in the references.\n\n**Staying on the latest v6 remains a legitimate choice where a hard blocker applies** —\nstated plainly: the Next Mongo façade does not wrap transactions yet (the underlying driver\nis available directly; this is expected to change soon), and pre-1.0 minors can carry\nbreaking changes with published upgrade recipes.\n\n### Decision table\n\n| Signal | Direction |\n|--------|-----------|\n| No blockers below apply | Migrate to Next; run the `verify-cutover-checklist` and share feedback with the Prisma team |\n| Greenfield \u002F prototype \u002F internal tool | Migrate to Next |\n| Codebase uses multi-document transactions (`$transaction`) — check with grep, do not ask | Plan raw-driver session equivalents first (see `client-api-mapping`), or stay on v6 until the façade wrapper lands |\n| Team cannot absorb pre-1.0 breaking upgrades between minors | Stay on v6 until GA |\n| Risk-averse but interested | Run a staged Next round-trip on a copy (see `verify-cutover-checklist`), then migrate |\n\nNote: the transactions gap is expected to close soon — this section will be updated when\nfaçade transactions merge in Prisma Next.\n\n### If staying on v6: hygiene (a deliberate stay, not neglect)\n\n- Pin the Prisma packages to the latest 6.x line and keep taking 6.x patch releases.\n- Track Prisma release notes and security advisories for the 6.x line.\n- Keep the classic v6 MongoDB setup: `url = env(\"DATABASE_URL\")` in the schema, `db push`\n  workflow, no SQL driver adapters (see `prisma-database-setup` for the v6 MongoDB shape).\n- Re-evaluate when Prisma Next's MongoDB is GA, or when blockers for trying EA are resolved.\n\n## Reference files\n\n| Reference | What it covers |\n|-----------|----------------|\n| `references\u002Fdecision-stay-or-migrate.md` | The full decision framing, blocker checks, and stay-hygiene detail |\n| `references\u002Fschema-contract-mapping.md` | v6 schema (`mongodb` provider, `@db.ObjectId`, composite types) → Next contract concepts |\n| `references\u002Fclient-api-mapping.md` | v6 client calls → Next equivalents, incl. raw escape hatches and transactions — names map, parity does not |\n| `references\u002Fmigrations-mapping.md` | v6 `db push`-only story → Next's plan\u002Fmigrate\u002Fverify\u002Fsign flow |\n| `references\u002Fverify-cutover-checklist.md` | No-data-moves verification: same DB, index parity, staged round-trip before cutover |\n\n## Verified against\n\nBehavioral claims about Prisma Next in this skill were verified against\n[prisma\u002Fprisma-next](https:\u002F\u002Fgithub.com\u002Fprisma\u002Fprisma-next) at commit\n`a2791c5dd59d579b4b3052942ae7f8fe5e2ee852` (pre-1.0, ~v0.14\u002F0.15 line). Prisma Next moves\nquickly in Early Access: **before acting on any Next-side claim, verify it against the\nversion actually installed** (check the project's `@prisma-next\u002F*` versions and the\nprisma-next skills installed with it). Next's Mongo target requires MongoDB 8.0+ and expects\n`mongodb@^7` as a user-supplied peer dependency.\n\n## Hand-off rule\n\nThis skill is the **discovery bridge**, not a replacement for Prisma Next's own\ndocumentation. After a project switches to Prisma Next, run Prisma Next's `init`\u002Fskill\ninstallation and follow its own skills (quickstart, contract, queries, migrations, runtime)\nfor day-to-day work — do not keep working from this skill's summaries.\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"version":26},"prisma","0.1.0","master","adb57b1d89278a8bae59a14ab31c7d6f35d0a7a2",".agents\u002Fskills\u002Fprisma-mongodb-upgrade","https:\u002F\u002Fgithub.com\u002FYousuf-Wizdan\u002Fexpense-flow","https:\u002F\u002Fexpense-flow-one-bay.vercel.app","https:\u002F\u002Fgithub.com\u002FYousuf-Wizdan","🚀 Developer | 💻 Tech Enthusiast | 📍 India\r\nBuilding cool things with code.","2026-08-13 02:21:34",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add Yousuf-Wizdan\u002Fexpense-flow --skill prisma-mongodb-upgrade",{"tool":41,"command":42},"bunx","bunx skills add Yousuf-Wizdan\u002Fexpense-flow --skill prisma-mongodb-upgrade",{"tool":44,"command":45},"pnpm","pnpm dlx skills add Yousuf-Wizdan\u002Fexpense-flow --skill prisma-mongodb-upgrade","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYousuf-Wizdan\u002Fexpense-flow\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fprisma-mongodb-upgrade\u002FSKILL.md",true,[49,55,59,63,67],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fclient-api-mapping.md","REFERENCE","参考文档",4085,"https:\u002F\u002Fgithub.com\u002FYousuf-Wizdan\u002Fexpense-flow\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fprisma-mongodb-upgrade\u002Freferences\u002Fclient-api-mapping.md",{"path":56,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fdecision-stay-or-migrate.md",4196,"https:\u002F\u002Fgithub.com\u002FYousuf-Wizdan\u002Fexpense-flow\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fprisma-mongodb-upgrade\u002Freferences\u002Fdecision-stay-or-migrate.md",{"path":60,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Fmigrations-mapping.md",3194,"https:\u002F\u002Fgithub.com\u002FYousuf-Wizdan\u002Fexpense-flow\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fprisma-mongodb-upgrade\u002Freferences\u002Fmigrations-mapping.md",{"path":64,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Fschema-contract-mapping.md",3416,"https:\u002F\u002Fgithub.com\u002FYousuf-Wizdan\u002Fexpense-flow\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fprisma-mongodb-upgrade\u002Freferences\u002Fschema-contract-mapping.md",{"path":68,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Fverify-cutover-checklist.md",3241,"https:\u002F\u002Fgithub.com\u002FYousuf-Wizdan\u002Fexpense-flow\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fprisma-mongodb-upgrade\u002Freferences\u002Fverify-cutover-checklist.md",[72,79,86,93,98,105],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7A09WT35ZKK9Y6DFK68TCDD","prisma-upgrade-v7","Complete migration guide from Prisma ORM v6 to v7 covering all breaking changes. Use when upgrading Prisma versions, encountering v7 errors, or migrating existing projects. Triggers on \"upgrade to prisma 7\", \"prisma 7 migration\", \"prisma-client generator\", \"driver adapter required\".","https:\u002F\u002Fgithub.com\u002FYousuf-Wizdan\u002Fexpense-flow\u002Fblob\u002Fmaster\u002F.windsurf\u002Fskills\u002Fprisma-upgrade-v7\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7A09RRSVYQJJ7CEAFKPJ3SN","prisma-postgres","Prisma Postgres setup and operations guidance across Console, create-db CLI, Management API, and Management API SDK. Use when creating Prisma Postgres databases, working in Prisma Console, provisioning with create-db\u002Fcreate-pg\u002Fcreate-postgres, or integrating programmatic provisioning with service tokens or OAuth.","https:\u002F\u002Fgithub.com\u002FYousuf-Wizdan\u002Fexpense-flow\u002Fblob\u002Fmaster\u002F.windsurf\u002Fskills\u002Fprisma-postgres\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7A09NAQ8JFAPJ842CAD9NCT","prisma-postgres-setup","Set up a new Prisma Postgres database and connect it to a local project using the Management API. Use when asked to \"set up a database\", \"create a Prisma Postgres project\", \"get a connection string\", \"connect my app to Prisma Postgres\", or \"provision a database\".","https:\u002F\u002Fgithub.com\u002FYousuf-Wizdan\u002Fexpense-flow\u002Fblob\u002Fmaster\u002F.windsurf\u002Fskills\u002Fprisma-postgres-setup\u002FSKILL.md",[],[],{"skillNo":94,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M7A09HM0FGFNMS1DA7QTZ68W","https:\u002F\u002Fgithub.com\u002FYousuf-Wizdan\u002Fexpense-flow\u002Fblob\u002Fmaster\u002F.windsurf\u002Fskills\u002Fprisma-mongodb-upgrade\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M7A09C2QXYTE4ET144PP4B2C","prisma-driver-adapter-implementation","Required reference for Prisma v7 driver adapter work. Use when implementing or modifying adapters, adding database drivers, or touching SqlDriverAdapter\u002FTransaction interfaces. Contains critical contract details not inferable from code examples — including the transaction lifecycle protocol, error mapping requirements, and verification checklist. Existing implementations do not replace this skill.","https:\u002F\u002Fgithub.com\u002FYousuf-Wizdan\u002Fexpense-flow\u002Fblob\u002Fmaster\u002F.windsurf\u002Fskills\u002Fprisma-driver-adapter-implementation\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":19},"01M7A0984E48KXWM16BH6D9AGC","prisma-database-setup","Guides for configuring Prisma with different database providers (PostgreSQL, MySQL, SQLite, MongoDB, etc.). Use when setting up a new project, changing databases, or troubleshooting connection issues. Triggers on \"configure postgres\", \"connect to mysql\", \"setup mongodb\", \"sqlite setup\".","https:\u002F\u002Fgithub.com\u002FYousuf-Wizdan\u002Fexpense-flow\u002Fblob\u002Fmaster\u002F.windsurf\u002Fskills\u002Fprisma-database-setup\u002FSKILL.md",[],[]]