
Prisma Upgrade V7 Prisma Config
- 14 installs
- 8 repo stars
- Updated February 9, 2026
- prisma/cursor-plugin
prisma-upgrade-v7-prisma-config sets up prisma.config.ts for Prisma v7.
About
The prisma-upgrade-v7-prisma-config skill introduces prisma.config.ts at project root using defineConfig and env helpers. Options include schema path, datasource url directUrl and shadowDatabaseUrl, migrations path and seed command, and experimental preview settings. Replaces scattered v6 env-only patterns with typed TypeScript config importable by tooling. Shows dotenv first import, seed string like tsx prisma/seed.ts, and monorepo relative schema paths. Documents how CLI commands read config via --config override for multi-package repositories. prisma.config.ts centralizes CLI configuration in v7. defineConfig sets schema, datasource, and migrations. Supports directUrl and shadowDatabaseUrl fields. migrations.seed configures db seed command. --config overrides path in monorepos. Typed config file wiring schema, URL, migrations, and seed. User authors or fixes prisma.config.ts during v7 migration. Teams upgrading Prisma projects to v7 config model. Build-phase integrations work migrating Prisma config to v7 file.
- prisma.config.ts centralizes CLI configuration in v7.
- defineConfig sets schema, datasource, and migrations.
- Supports directUrl and shadowDatabaseUrl fields.
- migrations.seed configures db seed command.
- --config overrides path in monorepos.
Prisma Upgrade V7 Prisma Config by the numbers
- 14 all-time installs (skills.sh)
- Ranked #604 of 911 Databases skills by installs in the Skillselion catalog
- Data as of Aug 4, 2026 (Skillselion catalog sync)
prisma-upgrade-v7-prisma-config capabilities & compatibility
- Capabilities
- basic configuration example · configuration options reference
- Use cases
- database · devops
What prisma-upgrade-v7-prisma-config says it does
defineConfig, env
npx skills add https://github.com/prisma/cursor-plugin --skill prisma-upgrade-v7-prisma-configAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 14 |
|---|---|
| repo stars | ★ 8 |
| Last updated | February 9, 2026 |
| Repository | prisma/cursor-plugin ↗ |
What belongs in prisma.config.ts?
Adopt prisma.config.ts as central Prisma CLI configuration for schema, datasource, and migrations.
Who is it for?
Teams upgrading Prisma projects to v7 config model.
Skip if: Skip when prisma.config.ts already matches v7 docs.
When should I use this skill?
User authors or fixes prisma.config.ts during v7 migration.
What you get
Typed config file wiring schema, URL, migrations, and seed.
Files
Prisma Config
Prisma v7 introduces prisma.config.ts as the central configuration file for the Prisma CLI.
Location
Place prisma.config.ts at your project root (next to package.json).
Basic Configuration
import 'dotenv/config'
import { defineConfig, env } from 'prisma/config'
export default defineConfig({
schema: 'prisma/schema.prisma',
migrations: {
path: 'prisma/migrations',
},
datasource: {
url: env('DATABASE_URL'),
},
})Configuration Options
schema
Path to your Prisma schema file:
schema: 'prisma/schema.prisma'datasource.url
Database connection URL:
datasource: {
url: env('DATABASE_URL'),
}datasource.directUrl
Direct connection URL (bypassing connection pooler):
datasource: {
url: env('DATABASE_URL'),
directUrl: env('DIRECT_DATABASE_URL'),
}datasource.shadowDatabaseUrl
Shadow database for migrations:
datasource: {
url: env('DATABASE_URL'),
shadowDatabaseUrl: env('SHADOW_DATABASE_URL'),
}migrations.path
Directory for migration files:
migrations: {
path: 'prisma/migrations',
}migrations.seed
Seed command for prisma db seed:
migrations: {
path: 'prisma/migrations',
seed: 'tsx prisma/seed.ts',
}Full Example
import 'dotenv/config'
import { defineConfig, env } from 'prisma/config'
export default defineConfig({
// Schema location
schema: 'prisma/schema.prisma',
// Migration configuration
migrations: {
path: 'prisma/migrations',
seed: 'tsx prisma/seed.ts',
},
// Database connection
datasource: {
url: env('DATABASE_URL'),
directUrl: env('DIRECT_DATABASE_URL'),
shadowDatabaseUrl: env('SHADOW_DATABASE_URL'),
},
})Environment Variables
The env() helper
Use env() to reference environment variables:
import { env } from 'prisma/config'
datasource: {
url: env('DATABASE_URL'),
}This provides type safety but does NOT load .env files automatically.
Loading .env files
Install and import dotenv:
npm install dotenvimport 'dotenv/config' // Must be first import
import { defineConfig, env } from 'prisma/config'Migrating from v6
Before (v6) - schema.prisma
datasource db {
provider = "postgresql"
url = env("DATABASE_URL")
directUrl = env("DIRECT_URL")
}After (v7) - prisma.config.ts
import 'dotenv/config'
import { defineConfig, env } from 'prisma/config'
export default defineConfig({
schema: 'prisma/schema.prisma',
datasource: {
url: env('DATABASE_URL'),
directUrl: env('DIRECT_URL'),
},
})And update schema.prisma:
datasource db {
provider = "postgresql"
// URLs now in prisma.config.ts
}Custom Config Path
Use --config flag with CLI commands:
prisma migrate dev --config ./config/prisma.config.tsMonorepo Configuration
import 'dotenv/config'
import { defineConfig, env } from 'prisma/config'
import path from 'path'
export default defineConfig({
schema: path.join(__dirname, 'packages/database/prisma/schema.prisma'),
migrations: {
path: path.join(__dirname, 'packages/database/prisma/migrations'),
},
datasource: {
url: env('DATABASE_URL'),
},
}){
"name": "prisma-upgrade-v7-prisma-config",
"version": "7.0.0",
"author": "prisma",
"license": "MIT"
}Related skills
FAQ
What does prisma-upgrade-v7-prisma-config do?
prisma-upgrade-v7-prisma-config sets up prisma.config.ts for Prisma v7.
When should I use prisma-upgrade-v7-prisma-config?
User authors or fixes prisma.config.ts during v7 migration.
Is this skill safe to install?
Review the Security Audits panel on this page before installing in production.