What problem does it solve? Prisma ORM v7 introduces breaking changes—prisma.config.ts is now mandatory, datasource url moves out of schema.prisma, and the CLI no longer auto-loads .env files—which causes setup and migration failures for Node.js and Next.js projects. ## Core Features & Use Cases - New Project Setup: Installs prisma and @prisma/client, generates prisma.config.ts, configures the datasource URL, and runs generate/migrate/studio. - v6 to v7 Migration: Moves datasource url/directUrl into prisma.config.ts, defines a .env loading strategy, and chooses between the legacy prisma-client-js generator and the new prisma-client with driver adapters or Accelerate. - Automated Diagnostics: The prisma7-doctor.mjs script checks Node version, dependencies, config files, schema, and .env, then prints next actions. - Use Case: A Next.js app upgraded to Prisma v7 fails with "datasource property url is no longer supported"—use this Skill to restructure the config and restore migrations. ## Quick Start Set up Prisma v7 in my Next.js project and fix the prisma.config.ts and DATABASE_URL errors blocking prisma migrate dev.