5 solution docs
Prisma solution docs
Schema-first Postgres ORM with generated types, real migrations and a GUI.
Pick Prisma and all 5 land in docs/solutions/prisma/, next to the rules and skills that reference them.
Every Prisma doc in the registry
Tags: codegen · connection-pooling · connections · deployment · dev · hot-reload · migrations · n-plus-one · nextjs · performance · pgbouncer · postgres · prisma · queries · serverless · sql · troubleshooting · typescript · vercel
Prisma types are wrong after a schema edit: generated client drift
The Prisma client is generated code. Edit the schema without regenerating and TypeScript describes the old database, locally, in CI-free builds and after a cached deploy.
prisma · codegen · typescript · vercel
Prisma in dev: "too many clients already" after a few saves
Next.js hot reload re-runs your module and builds a new PrismaClient every time. Cache one instance on globalThis and the connection leak stops.
prisma · nextjs · hot-reload · connections
Running Prisma migrations on Vercel without breaking production
Put prisma generate and prisma migrate deploy in the Vercel build command, never db push or migrate dev, and design migrations to survive a rolling deploy.
prisma · vercel · migrations · deployment
Fixing N+1 queries in Prisma with include, select and groupBy
A loop that queries per row turns one page load into hundreds of round trips. Fetch relations in the parent query, batch by id, and aggregate in the database.
prisma · performance · n-plus-one · sql
Prisma on serverless: why you need a pooler URL and a direct URL
Each serverless instance opens its own Postgres pool, so traffic exhausts connections. Route runtime queries through a pooler and keep a direct URL for migrations.
prisma · serverless · vercel · connection-pooling