
Prisma Orm V7 Skills
- 962 installs
- 22 repo stars
- Updated January 21, 2026
- gocallum/nextjs16-agent-skills
prisma-orm-v7-skills is a Prisma ORM reference skill that provides v7 breaking changes, upgrade commands, and migration guidance for developers generating or troubleshooting database code before upgrading to Prisma 7.
About
prisma-orm-v7-skills is a Next.js agent skill collecting Prisma ORM 7 facts, breaking changes, and migration guidance before code generation or troubleshooting. The skill links to the official v7 upgrade guide, Prisma Config reference, Client Extensions docs, and the Prisma 7 migration prompt for AI agents. Upgrade commands include pnpm add @prisma/client@7 and pnpm add -D prisma@7. Developers reach for prisma-orm-v7-skills when upgrading existing Prisma projects or generating database code that must comply with v7 minimum version requirements and config changes.
- Covers all Prisma 7 minimum version requirements including Node.js 20.19+ and TypeScript 5.4+
- Explains the full ESM transition and required package.json and tsconfig changes
- Details generator provider rename, mandatory output setting, and updated import paths
- Lists deprecated datasource fields and schema generation behavior changes
- Includes direct links to official Prisma 7 upgrade guide and AI migration prompt
Prisma Orm V7 Skills by the numbers
- 962 all-time installs (skills.sh)
- +5 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #408 of 4,347 Backend & APIs skills by installs in the Skillselion catalog
- Security screen: MEDIUM risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/gocallum/nextjs16-agent-skills --skill prisma-orm-v7-skillsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 962 |
|---|---|
| repo stars | ★ 22 |
| Security audit | 3 / 3 scanners passed |
| Last updated | January 21, 2026 |
| Repository | gocallum/nextjs16-agent-skills ↗ |
What breaking changes exist in Prisma ORM v7?
Get accurate Prisma ORM v7 facts, breaking changes, and migration guidance before generating or updating database code.
Who is it for?
Backend developers upgrading Prisma projects to v7 or generating database code that must follow new config and client requirements.
Skip if: Greenfield ORMs unrelated to Prisma or projects staying on Prisma 6 without planned upgrades.
When should I use this skill?
A developer upgrades Prisma, asks about v7 breaking changes, prisma.config, or client extensions before generation.
What you get
Prisma v7 upgrade plan, package version updates, and config migration aligned with official v7 docs.
- v7 migration checklist
- updated package versions
Files
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
# Upgrade packages
pnpm add @prisma/client@7
pnpm add -D prisma@7Breaking 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"inpackage.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. outputis required ingenerator client.- Prisma Client is no longer generated into
node_modulesby default. - After
npx prisma generate, update imports to your generated output path (example:
import { PrismaClient } from './generated/prisma/client').
Schema datasource deprecations:
url,directUrl,shadowDatabaseUrlinschema.prismaare deprecated.- Move datasource config to
prisma.config.ts(Prisma Config). - If you used
directUrlfor migrations, set the CLI migration connection string inprisma.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(usePrismaPgwith a direct DB connection string) - SQLite:
@prisma/adapter-better-sqlite3
Prisma Accelerate users (v6 → v7)
- Do not pass
prisma://orprisma+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
.envfiles in v7. - Explicitly load env vars (for example
import 'dotenv/config'inprisma.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.tsat the project root (next topackage.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 resetis removed. - Run seeding explicitly:
pnpm prisma db seed(orpnpm exec prisma db seed). --skip-generateand--skip-seedflags removed.prisma migrate devandprisma db pushno longer runprisma generateautomatically.- Run
pnpm prisma generate(orpnpm exec prisma generate) explicitly.
Prisma-specific env vars removed
- Removed env vars:
PRISMA_CLI_QUERY_ENGINE_TYPEPRISMA_CLIENT_ENGINE_TYPEPRISMA_QUERY_ENGINE_BINARYPRISMA_QUERY_ENGINE_LIBRARYPRISMA_GENERATE_SKIP_AUTOINSTALLPRISMA_SKIP_POSTINSTALL_GENERATEPRISMA_GENERATE_IN_POSTINSTALLPRISMA_GENERATE_DATAPROXYPRISMA_GENERATE_NO_ENGINEPRISMA_CLIENT_NO_RETRYPRISMA_MIGRATE_SKIP_GENERATEPRISMA_MIGRATE_SKIP_SEED
MongoDB support
- Prisma ORM 7 does not support MongoDB yet; stay on Prisma ORM 6 if you need MongoDB.
Upgrade Checklist (quick)
- Upgrade packages; confirm Node/TypeScript versions.
- Move to ESM (or adjust your runtime/build to consume ESM).
- Update
schema.prismagenerator toprovider = "prisma-client"and setoutput. - Run
pnpm prisma generateand update Prisma Client imports to the generated output path. - Add
prisma.config.tsat repo root; move datasource config and load env explicitly. - Update Prisma Client instantiation to use a driver adapter (unless using Accelerate).
- Update workflows: run
pnpm prisma generateandpnpm prisma db seedexplicitly.
Related skills
FAQ
What packages does prisma-orm-v7-skills upgrade?
prisma-orm-v7-skills documents upgrading with pnpm add @prisma/client@7 and pnpm add -D prisma@7, following the official Prisma v7 upgrade guide and config reference.
When should developers consult prisma-orm-v7-skills?
prisma-orm-v7-skills should be consulted before generating or troubleshooting Prisma database code when upgrading to version 7 or applying prisma.config and client extension changes.
Is Prisma Orm V7 Skills safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.