Summary
The product was renamed to Prisma 8 (prisma/web#8117), and the unified CLI's docs no longer use the old name — but the command family this repo publishes in @prisma/orm-toolchain still introduces it to every newcomer:
prisma orm init --help (and the top-level orm init brief): "Initialize a new Prisma Next project"prisma lsp --help: "Start the Prisma Next language server"orm init's scaffold writes prisma-next.md and installs skills labeled "Prisma Next agent-skill"
Verified on @prisma/orm-toolchain@8.0.0-rc.3 (current latest), mounted in the prisma-cli shell at its main.
Why it matters
The first help text a Prisma 8 newcomer sees should match the naming the docs teach. Originally reported as part of prisma/prisma-cli#182; the shell repo's own strings are fixed there, but these strings ship from this repo's toolchain, and internal branding ("Prisma Next" in repo docs/skills) versus user-visible CLI strings is a product-naming call this repo's owners should make deliberately — hence an issue rather than a unilateral string-sweep PR.
Scope suggestion
User-visible surfaces only: command briefs/help text, the scaffolded prisma-next.md (name and/or contents), and next-step strings. Internal package names, repo docs, and skill slugs can lag.
Reported on behalf of datta@prisma.io while validating the Prisma 8 docs (prisma/web#8151).
🤖 Filed with Claude Code
Summary
The product was renamed to Prisma 8 (prisma/web#8117), and the unified CLI's docs no longer use the old name — but the command family this repo publishes in
@prisma/orm-toolchainstill introduces it to every newcomer:prisma orm init --help(and the top-levelorm initbrief): "Initialize a new Prisma Next project"prisma lsp --help: "Start the Prisma Next language server"orm init's scaffold writesprisma-next.mdand installs skills labeled "Prisma Next agent-skill"Verified on
@prisma/orm-toolchain@8.0.0-rc.3(currentlatest), mounted in the prisma-cli shell at its main.Why it matters
The first help text a Prisma 8 newcomer sees should match the naming the docs teach. Originally reported as part of prisma/prisma-cli#182; the shell repo's own strings are fixed there, but these strings ship from this repo's toolchain, and internal branding ("Prisma Next" in repo docs/skills) versus user-visible CLI strings is a product-naming call this repo's owners should make deliberately — hence an issue rather than a unilateral string-sweep PR.
Scope suggestion
User-visible surfaces only: command briefs/help text, the scaffolded
prisma-next.md(name and/or contents), and next-step strings. Internal package names, repo docs, and skill slugs can lag.Reported on behalf of datta@prisma.io while validating the Prisma 8 docs (prisma/web#8151).
🤖 Filed with Claude Code