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 guides the full migration so projects 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, module format options, and new client/browser/models/enums entrypoints. - Driver Adapter Setup: Install and configure required adapters for PostgreSQL, MySQL, SQLite, SQL Server, Neon, PlanetScale, Turso, D1, and Prisma Postgres, including pool and SSL settings. - Configuration and Environment Migration: Create prisma.config.ts, move datasource URLs out of the schema, and load environment variables 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: A team upgrading a PostgreSQL-backed Node.js API to Prisma 7 follows the step-by-step guide to update packages, configure the PrismaPg adapter, create prisma.config.ts, fix imports, and regenerate the client. ## Quick Start Ask the assistant to upgrade your project from Prisma 6 to Prisma 7 and apply the required schema, adapter, and configuration changes.