Prisma 8 skill
prisma-8
The official Prisma 8 skill installed from your project's packages: data contract, migrations, queries and version upgrades
Install
npx prisma orm init
npx prisma skills syncThe first command adds Prisma 8 to an existing project, the second copies skills into agent folders.
This is third-party code. Review the repository files before installing.
What it does
The prisma-8 skill ships inside the @prisma/orm-postgres, @prisma/orm-sqlite and @prisma/orm-mongo packages and describes exactly the installed version. SKILL.md is a router: depending on the task it sends the agent to references on getting started, contract authoring, migrations, db.orm and db.sql queries, build tool integration, the Supabase extension and error code lookup. Version upgrades are part of the skill and rely on recipes shipped with each release. Every reference has a section on what Prisma 8 does not do yet, so the agent does not invent APIs.
Who it is for. For TypeScript developers starting a project on Prisma 8 or moving to it.
Good fit when
- The project uses @prisma/orm-* packages and contract.prisma
- You need to plan and apply a migration
- You need to upgrade Prisma 8 to a new release candidate
Not a fit when
- The project uses Prisma ORM 7 or earlier with schema.prisma and @prisma/client
- You want a global skill without project packages
Example request
Add an orders model related to users to the contract and apply the migrationLimitations
Prisma 8 is still a release candidate and may break compatibility between versions. The skill installs at project level only. A copy installed through npx skills straight from GitHub does not update itself.
How to disable. Remove the prisma-8 folders from .claude/skills, .cursor/skills and .agents/skills in the project root.
Security check
- Following the skill, the agent applies migrations to the database
README in short
The README presents Prisma 8 as a TypeScript rewrite of the ORM designed for work with agents. New projects start from a template, existing ones use npx prisma orm init, and then npx prisma skills sync installs the skills. The skill and a prisma-8.md primer land in Claude Code, Cursor, Devin and shared .agents folders. Apache 2.0 licensed.
SKILL.md
--- name: prisma-8 description: >- Use when working in a project that depends on @prisma/orm-postgres, @prisma/orm-sqlite, or @prisma/orm-mongo (Prisma 8, formerly Prisma Next): editing contract.prisma or a contract.ts builder, running `prisma contract emit`, planning or applying migrations, editing migration.ts, writing db.orm / db.sql / db.query queries, wiring db.ts or middleware, integrating a build tool, using the Supabase extension or RLS, or reading a dotted error code such as MIGRATION.HASH_MISMATCH. Use when the user asks "what is Prisma 8", "where do I start", or compares it to another ORM. Use when the user asks to upgrade or bump Prisma 8 in an app or an extension package. Use when you see @internal/* or @prisma/orm-* imports, prisma.config.ts with definePrismaConfig, or contract.json / contract.d.ts. Do not use for Prisma ORM 7 or earlier (schema.prisma + @prisma/client). metadata: library: '@prisma/orm-postgres' library_version: '8.0.0-rc.11' version: '2026-09-12' --- # Prisma 8 (Prisma 8)
FAQ
How do I know the skill is stale?
Every prisma command compares the synced skill with the installed packages and prints a line to stderr when they drift.
Does it work for Prisma 7?
No, the skill explicitly excludes projects with schema.prisma and @prisma/client.
Related
The official FastAPI skill, bundled with the package, teaching agents to write code for the installed version
Official skills and agents from the .NET team: performance, MSBuild, NuGet, upgrades, testing, ASP.NET Core, Blazor and MAUI
Firebase MCP Server
Firebase CLI and MCP Server
Official Firebase MCP server from the Firebase CLI: projects, Firestore, Auth, Crashlytics, Remote Config and function logs
Laravel's official MCP server, guidelines and skills: the agent sees the DB schema, logs and package versions and searches ecosystem docs