跳到主内容
智客 ZICQ

技能库 智客分类:Agent 工作流 prisma-mongodb-upgrade

Prisma Mongodb Upgrade

V6上的Prisma ORM MongoDB项目的决定和迁移指南,没有升级到v7的路径. 当一个MongoDB项目询问提升Prisma时使用,当"升级到棱镜 7"出现在一个有提供者="mongodb"的项目中时使用,或者当评价一个移动到Prisma Next时使用. 出自"上等棱镜·蒙哥德","出等棱镜","出等棱镜","出等棱镜","出等棱镜"等.

290225 安装量

官方网址:skills.sh

技能介绍

先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。

做什么

关于 v6 的 Prisma ORM MongoDB 项目的决定和迁移指南, 这些项目没有升级到 v7 的路径

何时用

a 蒙戈语 DB项目询问Prisma的升级,当"升级到棱镜7"出现在一个有提供者="mongodb"的项目中,或者当评估一个移动到Prisma Next时. 触发的"上等棱镜·蒙哥德","出等棱镜","出等棱镜","出等棱镜","出等棱镜","出等棱镜","出等棱镜","出等棱镜"

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:Prisma MongoDB Upgrade Path、The version landscape、The decision, up front、Decision table、If staying on v6: hygiene (a deliberate stay, not neglect)、Reference files。

文件分析

文件分析:除 SKILL.md 外,正文引用了 references/decision-stay-or-migrate.md、references/schema-contract-mapping.md、references/client-api-mapping.md、references/migrations-mapping.md、references/verify-cutover-checklist.md,属于带资源的技能包,这些文件按需再读。

官方 description(原文)

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".

Prisma MongoDB Upgrade PathThe version landscapeThe decision, up frontDecision tableIf staying on v6: hygiene (a deliberate stay, not neglect)Reference filesVerified againstHand-off rule

· 许可:MIT

来源分类:skills.sh agent-skill

SKILL.md 与 Agent 调用

官方规范 ↗
name
prisma-mongodb-upgrade
description
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".
许可
MIT
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。
指令中引用的文件 · 5
  • references/decision-stay-or-migrate.md
  • references/schema-contract-mapping.md
  • references/client-api-mapping.md
  • references/migrations-mapping.md
  • references/verify-cutover-checklist.md

以下路径提取自原文;文件是否齐全请以来源仓库中的完整目录为准。

具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。

该技能引用了附属文件,请从来源获取完整目录;仅复制 SKILL.md 可能缺少依赖。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。

把 Agent Skill「prisma-mongodb-upgrade」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-6df07d9890f9d459-%E6%99%AE%E9%87%8C%E6%96%AF%E7%8E%9B%C2%B7%E8%92%99%E6%88%88%E5%BE%B7%E5%B8%83-%E5%8D%87%E7%BA%A7.html
请存为 .cursor/skills/prisma-mongodb-upgrade/SKILL.md 或 .claude/skills/prisma-mongodb-upgrade/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。
该技能还带 scripts/、references/、assets/ 等文件,请从 https://github.com/prisma/skills 取完整目录,不要只建一个 SKILL.md。

GitHub 完整包 ↗

终端安装 · Skills CLI

需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。

npx skills add 'https://github.com/prisma/skills' --list

npx skills add 'https://github.com/prisma/skills' --skill 'prisma-mongodb-upgrade'

CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。

阅读排版

name: prisma-mongodb-upgrade description: 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". license: MIT metadata: author: prisma version: "0.1.0"

Prisma MongoDB Upgrade Path

MongoDB projects are the one Prisma cohort with no road into Prisma 7: v6 is the terminal classic-ORM major for MongoDB, and v7 never ships a MongoDB connector. The successor path is Prisma Next, where MongoDB support is in Early Access with GA planned after Postgres. This skill frames the real decision — migrate to Prisma Next (the encouraged path), or stay on v6 where a hard blocker applies — and carries the migration mechanics.

Never do either of these:

  • Never advise a MongoDB project to "upgrade to Prisma 7". The connector does not exist there. The prisma-upgrade-v7 guide does not apply to MongoDB projects.
  • Never solve the version question by rewriting the app onto a SQL database. Changing the database engine is a separate, much larger decision that is not yours to make implicitly.

The version landscape

| Version | MongoDB status | |---------|----------------| | Prisma ORM v6 | Fully supported (mongodb provider); latest 6.x is the current stable path; maintenance line | | Prisma ORM v7 | No MongoDB connector — not an option, ever | | Prisma Next | MongoDB support in Early Access, actively developed, GA planned after Postgres — the successor path for MongoDB projects |

The decision, up front

Migrating to Prisma Next is the encouraged path. MongoDB support in Prisma Next is Early Access: functional and moving quickly, with GA planned after Postgres — and the Prisma team wants MongoDB users to migrate early and share feedback. The migration mechanics are detailed in the references.

Staying on the latest v6 remains a legitimate choice where a hard blocker applies — stated plainly: the Next Mongo façade does not wrap transactions yet (the underlying driver is available directly; this is expected to change soon), and pre-1.0 minors can carry breaking changes with published upgrade recipes.

Decision table

| Signal | Direction | |--------|-----------| | No blockers below apply | Migrate to Next; run the verify-cutover-checklist and share feedback with the Prisma team | | Greenfield / prototype / internal tool | Migrate to Next | | 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 | | Team cannot absorb pre-1.0 breaking upgrades between minors | Stay on v6 until GA | | Risk-averse but interested | Run a staged Next round-trip on a copy (see verify-cutover-checklist), then migrate |

Note: the transactions gap is expected to close soon — this section will be updated when façade transactions merge in Prisma Next.

If staying on v6: hygiene (a deliberate stay, not neglect)

  • Pin the Prisma packages to the latest 6.x line and keep taking 6.x patch releases.
  • Track Prisma release notes and security advisories for the 6.x line.
  • Keep the classic v6 MongoDB setup: url = env("DATABASE_URL") in the schema, db push workflow, no SQL driver adapters (see prisma-database-setup for the v6 MongoDB shape).
  • Re-evaluate when Prisma Next's MongoDB is GA, or when blockers for trying EA are resolved.

Reference files

| Reference | What it covers | |-----------|----------------| | references/decision-stay-or-migrate.md | The full decision framing, blocker checks, and stay-hygiene detail | | references/schema-contract-mapping.md | v6 schema (mongodb provider, @db.ObjectId, composite types) → Next contract concepts | | references/client-api-mapping.md | v6 client calls → Next equivalents, incl. raw escape hatches and transactions — names map, parity does not | | references/migrations-mapping.md | v6 db push-only story → Next's plan/migrate/verify/sign flow | | references/verify-cutover-checklist.md | No-data-moves verification: same DB, index parity, staged round-trip before cutover |

Verified against

Behavioral claims about Prisma Next in this skill were verified against prisma/prisma-next at commit a2791c5dd59d579b4b3052942ae7f8fe5e2ee852 (pre-1.0, ~v0.14/0.15 line). Prisma Next moves quickly in Early Access: before acting on any Next-side claim, verify it against the version actually installed (check the project's @prisma-next/* versions and the prisma-next skills installed with it). Next's Mongo target requires MongoDB 8.0+ and expects mongodb@^7 as a user-supplied peer dependency.

Hand-off rule

This skill is the discovery bridge, not a replacement for Prisma Next's own documentation. After a project switches to Prisma Next, run Prisma Next's init/skill installation and follow its own skills (quickstart, contract, queries, migrations, runtime) for day-to-day work — do not keep working from this skill's summaries.

相关技能

Agent 工作流

Skill Creator

创造有效技能指南。 当用户想创造出新的技能(或更新现有的技能),以专业知识,工作流程,或工具集成来扩展克洛德的能力时,应该使用这种技能.

Agent 工作流

Clawdhub

使用ClawdHub CLI搜索,安装,更新并发布从taladhub.com的代理技能. 需要获取苍蝇上的新技能时使用,将安装的技能同步到最新版本或特定版本,或者发布 npm-instainddhub CLI 的新/更新的技能文件夹.

Agent 工作流

Agent Team Orchestration

管弦乐团多代理团队,任务设定周期,交接协议,审查工作流程. 使用时间: (1)建立2+特派员队伍,具有不同专业,(2)确定任务路线和生命周期(收录框_ spec_建设_审查_完成),(3)在特派员之间制定交接协议,(4)建立审查和质量关口,(5)管理特派员之间的交流和文物共享.

Agent 工作流

Superpowers

Spec-first,TDD,子代理驱动的软件开发工作流程. 当:(1)构建任何新功能或应用——触发脑暴_计划_子代理执行回路,(2)调试出一个bug或测试失败——触发系统性的根起过程,(3)用户说"让我们构建","帮助我计划","我想添加X",或"这个被打破",(4)完成一个功…