What problem does it solve? Upgrading from Prisma ORM v6 to v7 introduces breaking changes around the new prisma-client generator, required driver adapters, prisma.config.ts, explicit environment loading, and new generated client entrypoints, which cause import errors and runtime failures if handled incorrectly. ## Core Features & Use Cases - Step-by-step migration path: Covers package updates, ESM or CommonJS module format selection, tsconfig changes, schema generator block updates, and prisma.config.ts creation. - Driver adapter setup: Provides installation and configuration for PostgreSQL, MySQL, SQLite, SQL Server, Neon, PlanetScale, Turso, D1, and Prisma Postgres adapters, including pool and SSL settings. - Removed feature replacements: Shows how to replace $use middleware with Client Extensions, Prisma.validator with TypeScript satisfies, and removed CLI flags with explicit commands. - Use Case: A team upgrading a Next.js app to Prisma 7 follows the guide to switch the generator to prisma-client with an explicit output path, install @prisma/adapter-pg, create prisma.config.ts with dotenv loading, and fix all client imports. ## Quick Start Ask the AI to upgrade my project from Prisma 6 to Prisma 7 and fix the resulting generator, adapter, and import errors.