Prisma Orm V7 Skills
Upgrade or troubleshoot a Node/TypeScript app migrating to Prisma ORM 7 without missing ESM, generator, or config breaking changes.
Overview
prisma-orm-v7-skills is an agent skill most often used in Build (also Ship, Operate) that surfaces Prisma ORM 7 breaking changes before generate, import, or upgrade troubleshooting.
Install
npx skills add https://github.com/gocallum/nextjs16-agent-skills --skill prisma-orm-v7-skillsWhat is this skill?
- Documents Prisma 7 breaking changes: Node 20.19+, TypeScript 5.4+, ESM-only package
- Generator migration: prisma-client-js to prisma-client with required output path
- Datasource URL moves toward prisma.config deprecations in schema.prisma
- pnpm upgrade commands for @prisma/client@7 and prisma@7 dev dependency
- Links to official upgrade guide, Prisma Config reference, and Prisma 7 AI migration prompt
- Node.js minimum 20.19.0+ (and 22.x) for Prisma 7
- TypeScript minimum 5.4.0+ for Prisma 7
Adoption & trust: 874 installs on skills.sh; 22 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You bumped Prisma or started a greenfield v7 project and hit ESM, generator output, or deprecated datasource URL errors you did not expect.
Who is it for?
Solo full-stack devs upgrading PostgreSQL/MySQL apps using Prisma Client in Next.js 16 or Node ESM projects.
Skip if: Teams staying on Prisma 6 indefinitely or using ORMs other than Prisma without planned v7 migration.
When should I use this skill?
Upgrading to Prisma ORM 7 or troubleshooting generation, ESM, and config issues—consider v7 changes before generate.
What do I get? / Deliverables
You apply the documented v7 constraints—packages, ESM settings, generator output, and config migration—so prisma generate and client imports work on supported Node/TS versions.
- Updated package.json and schema.generator blocks aligned to v7
- Correct Prisma Client import path after generate
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
ORM upgrades and schema generation are core backend build work and resurface during ship perf fixes and operate incidents. Backend is where Prisma schema, client generation, and database URL configuration live for solo full-stack builders.
Where it fits
Align package.json type module and generator output before first prisma generate on a new SaaS API.
Verify client import paths and config references before a release that includes the Prisma 7 bump.
Diagnose runtime import or deprecated datasource URL warnings after a partial upgrade in production.
How it compares
Version-specific upgrade facts pack—not a generic SQL modeling or raw migration runner skill.
Common Questions / FAQ
Who is prisma-orm-v7-skills for?
It is for developers upgrading to Prisma 7 or debugging generation and import issues on Node 20+ and TypeScript 5.4+ codebases.
When should I use prisma-orm-v7-skills?
Use it in Build before changing schema or generators, in Ship when release prep includes a major Prisma bump, and in Operate when production errors mention deprecated datasource fields or ESM import failures.
Is prisma-orm-v7-skills safe to install?
It is documentation-only guidance; review the Security Audits panel on this page and follow official Prisma upgrade steps in a branch before touching production databases.
SKILL.md
READMESKILL.md - Prisma Orm V7 Skills
## Links - Upgrade guide (v7): https://www.prisma.io/docs/orm/more/upgrade-guides/upgrading-versions/upgrading-to-prisma-7 - Prisma Config reference: https://www.prisma.io/docs/orm/reference/prisma-config-reference - Prisma Client Extensions: https://www.prisma.io/docs/orm/prisma-client/client-extensions - Prisma 7 migration prompt (AI agents): https://www.prisma.io/docs/ai/prompts/prisma-7 ## Upgrade ```sh # Upgrade packages pnpm add @prisma/client@7 pnpm add -D prisma@7 ``` ## Breaking Changes (v7) ### Minimum versions - Node.js: 20.19.0+ (and 22.x) - TypeScript: 5.4.0+ ### Prisma is now ESM - Prisma ORM ships as ES modules. - Set `"type": "module"` in `package.json` (or migrate your project to ESM). - TypeScript projects must compile/resolve ESM (guide example: `module: ESNext`, `target: ES2023`, `moduleResolution: node`). ### Prisma schema + generation changes - Generator provider: `prisma-client-js` → `prisma-client`. - `output` is required in `generator client`. - Prisma Client is no longer generated into `node_modules` by default. - After `npx prisma generate`, update imports to your generated output path (example: `import { PrismaClient } from './generated/prisma/client'`). Schema datasource deprecations: - `url`, `directUrl`, `shadowDatabaseUrl` in `schema.prisma` are deprecated. - Move datasource config to `prisma.config.ts` (Prisma Config). - If you used `directUrl` for migrations, set the CLI migration connection string in `prisma.config.ts`. ### Driver adapters required for Prisma Client (new instantiation) - Prisma Client creation now requires a driver adapter for all databases. - Example adapters: - Postgres: `@prisma/adapter-pg` (use `PrismaPg` with a direct DB connection string) - SQLite: `@prisma/adapter-better-sqlite3` ### Prisma Accelerate users (v6 → v7) - Do not pass `prisma://` or `prisma+postgres://` (Accelerate URLs) to a driver adapter. - Keep the Accelerate URL and instantiate Prisma Client with the Accelerate extension instead. ### Env vars are not loaded by default - Prisma CLI no longer auto-loads `.env` files in v7. - Explicitly load env vars (for example `import 'dotenv/config'` in `prisma.config.ts`, or load env in your scripts). - Bun users: no change required (bun auto-loads `.env`). ### Prisma CLI config moved to `prisma.config.ts` - Prisma Config is now the default place to configure how Prisma CLI behaves. - Place `prisma.config.ts` at the project root (next to `package.json`). - Configure schema path, migrations path/seed, and datasource URL there. ### Client middleware removed - `prisma.$use(...)` is removed. - Migrate middleware logic to Prisma Client Extensions. ### Metrics removed from Client Extensions - The Metrics preview feature is removed in v7. - Use your database driver/adapter or implement custom counters via extensions. ### Migrate/seed/generate behavior changes - Automatic seeding after `prisma migrate dev` / `prisma migrate reset` is removed. - Run seeding explicitly: `pnpm prisma db seed` (or `pnpm exec prisma db seed`). - `--skip-generate` and `--skip-seed` flags removed. - `prisma migrate dev` and `prisma db push` no longer run `prisma generate` automatically. - Run `pnpm prisma generate` (or `pnpm exec prisma generate`) explicitly. ### Prisma-specific env vars removed - Removed env vars: - `PRISMA_CLI_QUERY_ENGINE_TYPE` - `PRISMA_CLIENT_ENGINE_TYPE` - `PRISMA_QUERY_ENGINE_BINARY` - `PRISMA_QUERY_ENGINE_LIBRARY` - `PRISMA_GENERATE_SKIP_AUTOINSTALL` - `PRISMA_SKIP_POSTINSTALL_GENERATE` - `PRISMA_GENERATE_IN_POSTINSTALL` - `PRISMA_GENERATE_DATAPROXY` - `PRISMA_GENERATE_NO_ENGINE` - `PRISMA_CLIENT_NO_RETRY` - `PRISMA_MIGRATE_SKIP_GENERATE` - `PRISMA_MIGRATE_SKIP_SEED` ### MongoDB support - Prisma ORM 7 does not support MongoDB yet; stay on Prisma ORM 6 if