Prisma ORM CLI commands reference covering init, generate, migrate, db, dev, complete, studio, validate, format, debug, and mcp. Use for ORM/database CLI workflows, not the Prisma Platform CLI. Triggers on "prisma init", "prisma generate", "prisma migrate", "prisma db", "prisma complete", "prisma st

Prisma CLI Reference Reference for Prisma ORM CLI commands. This skill provides guidance on command usage, options, and best practices for current Prisma ORM releases. Boundary: Platform and Compute Do not confuse the stable ORM command ( prisma ) with the public beta Platform package ( @prisma/cli , binary prisma cli ). Use prisma compute for Compute apps and workspace auth, and prisma postgres for Platform projects and databases. When to Apply Reference this skill when: Setting up a new Prisma project ( prisma init ) Generating Prisma Client ( prisma generate ) Running database migrations ( prisma migrate ) Managing database state ( prisma db push/pull ) Using local development database ( prisma dev ) Debugging Prisma issues ( prisma debug ) Generating shell completions ( prisma complete ) Rule Categories by Priority Priority Category Impact Prefix 1 Setup HIGH init 2 Generation HIGH generate 3 Development HIGH dev 4 Database HIGH db 5 Migrations CRITICAL migrate 6 Utility MEDIUM complete , studio , validate , format , debug , mcp Command Categories Category Commands Purpose Setup init Initialize a Prisma project Generation generate Generate Prisma Client Validation validate , format Schema validation and formatting Development dev Local Prisma Postgres for development Database db pull , db push , db seed , db execute Direct database operations Migrations migrate dev , migrate deploy , migrate reset , migrate status , migrate diff , migrate resolve Schema migrations Utility complete , studio , mcp , version , debug Shell, development, and AI tooling Quick Reference Project Setup Client Generation Bun Runtime When using Bun, always add the bun flag so Prisma runs with the Bun runtime (otherwise it falls back to Node.js because of the CLI shebang): Local Development Database Database Operations Migrations (Development) Migrations (Production) Utility Commands AI Safety Checkpoint Prisma blocks destructive commands when it detects an AI agent until the agent has obtained explicit user consent. This covers migrate reset , db push force reset , and db push accept data loss . Explain the exact data loss impact and ask for consent immediately before running the command. Do not infer consent from earlier or unrelated messages. If automation needs the consent variable, set PRISMA USER CONSENT FOR DANGEROUS AI ACTION to the user's exact consent message. Do not invent the text. The Prisma MCP server deliberately has no migrate reset tool. Read references/agent safety.md before any destructive Prisma command. Current Prisma CLI Setup New Configuration File Use prisma.config.ts for CLI configuration: Current Command Behavior Run prisma generate explicitly after migrate dev , db push , or other schema syncs when you need fresh client output Run prisma db seed explicitly after migrate dev or migrate reset when you need seed data Use prisma db execute file ... for raw SQL scripts Environment Variables Load environment variables explicitly in prisma.config.ts , commonly with dotenv : Rule Files See individual rule files for detailed command documentation: How to Use Use the command categories above for navigation, then open the specific command reference file you need.

prisma-cli