What problem does it solve? Upgrading from Prisma ORM v6 to v7 introduces breaking changes around the new prisma-client generator, mandatory driver adapters, prisma.config.ts, explicit environment loading, and new generated client entrypoints. This Skill provides a complete, step-by-step migration path so you avoid import errors, connection failures, and deprecated API usage after upgrading. ## Core Features & Use Cases - Schema and Generator Migration: Switch from prisma-client-js to the prisma-client generator with required output paths, moduleFormat options, and new client/browser/models/enums entrypoints. - Driver Adapter Setup: Install and configure the required adapter for PostgreSQL, MySQL, SQLite, SQL Server, Neon, PlanetScale, Turso, D1, or Prisma Postgres, including pool and SSL settings. - Config and Environment Migration: Create prisma.config.ts, move datasource URLs out of schema.prisma, and load .env files explicitly with dotenv. - Removed Feature Replacements: Replace $use middleware with Client Extensions, Prisma.validator with TypeScript satisfies, and handle removed CLI flags and metrics. - Use Case: Your Node.js API fails with "Cannot find module" and driver adapter errors after running npm install prisma@7. Follow the ordered migration steps to update the generator block, install @prisma/adapter-pg, create prisma.config.ts, and regenerate a working client. ## Quick Start Ask the AI to migrate your Prisma v6 project to v7 by updating the schema generator, installing a driver adapter, and creating prisma.config.ts.