PaperclipOrg
Claude Agent Skill · by Prisma

Prisma Cli

A comprehensive reference for all Prisma CLI commands, from project setup to production migrations. Covers the current v7.6.0 command structure including the ne

Install
Terminal · npx
$npx skills add https://github.com/prisma/skills --skill prisma-cli
Works with Paperclip

How Prisma Cli fits into a Paperclip company.

Prisma Cli drops into any Paperclip agent that handles this kind of work. Assign it to a specialist inside a pre-configured PaperclipOrg company and the skill becomes available on every heartbeat — no prompt engineering, no tool wiring.

S
SaaS FactoryPaired

Pre-configured AI company — 18 agents, 18 skills, one-time purchase.

$27$59
Explore pack
Source file
SKILL.md243 lines
Expand
---name: prisma-clidescription: Prisma CLI commands reference covering all available commands, options, and usage patterns. Use when running Prisma CLI commands, setting up projects, generating client, running migrations, managing databases, or starting Prisma's MCP server. Triggers on "prisma init", "prisma generate", "prisma migrate", "prisma db", "prisma studio", "prisma mcp".license: MITmetadata:  author: prisma  version: "7.6.0"--- # Prisma CLI Reference Complete reference for all Prisma CLI commands. This skill provides guidance on command usage, options, and best practices for current Prisma releases. ## 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`) ## 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 | `studio`, `validate`, `format`, `debug`, `mcp` | ## Command Categories | Category | Commands | Purpose ||----------|----------|---------|| Setup | `init` | Bootstrap new 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 | `studio`, `mcp`, `version`, `debug` | Development and AI tooling | ## Quick Reference ### Project Setup ```bash# Initialize new project (creates prisma/ folder and prisma.config.ts)prisma init # Initialize with specific databaseprisma init --datasource-provider postgresqlprisma init --datasource-provider mysqlprisma init --datasource-provider sqlite # Initialize with Prisma Postgres (cloud)prisma init --db # Initialize with an example modelprisma init --with-model``` ### Client Generation ```bash# Generate Prisma Clientprisma generate # Watch mode for developmentprisma generate --watch # Generate specific generator onlyprisma generate --generator client``` ### 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): ```bashbunx --bun prisma initbunx --bun prisma generate``` ### Local Development Database ```bash# Start local Prisma Postgresprisma dev # Start with specific nameprisma dev --name myproject # Start in background (detached)prisma dev --detach # List all local instancesprisma dev ls # Stop instanceprisma dev stop myproject # Remove instance dataprisma dev rm myproject``` ### Database Operations ```bash# Pull schema from existing databaseprisma db pull # Push schema to database (no migrations)prisma db push # Seed databaseprisma db seed # Execute raw SQLprisma db execute --file ./script.sql``` ### Migrations (Development) ```bash# Create and apply migrationprisma migrate dev # Create migration with nameprisma migrate dev --name add_users_table # Create migration without applyingprisma migrate dev --create-only # Reset database and apply all migrationsprisma migrate reset``` ### Migrations (Production) ```bash# Apply pending migrations (CI/CD)prisma migrate deploy # Check migration statusprisma migrate status # Compare schemas and generate diffprisma migrate diff --from-config-datasource --to-schema schema.prisma --script``` ### Utility Commands ```bash# Open Prisma Studio (database GUI)prisma studio # Start Prisma's MCP server for AI toolsprisma mcp # Show version infoprisma versionprisma -v # Debug informationprisma debug # Validate schemaprisma validate # Format schemaprisma format``` ## Current Prisma CLI Setup ### New Configuration File Use `prisma.config.ts` for CLI configuration: ```typescriptimport 'dotenv/config'import { defineConfig, env } from 'prisma/config' export default defineConfig({  schema: 'prisma/schema.prisma',  migrations: {    path: 'prisma/migrations',    seed: 'tsx prisma/seed.ts',  },  datasource: {    url: env('DATABASE_URL'),  },})``` ### 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`: ```typescript// prisma.config.tsimport 'dotenv/config'``` ## Rule Files See individual rule files for detailed command documentation: ```references/init.md           - Project initializationreferences/generate.md       - Client generationreferences/dev.md            - Local development databasereferences/db-pull.md        - Database introspectionreferences/db-push.md        - Schema pushreferences/db-seed.md        - Database seedingreferences/db-execute.md     - Raw SQL executionreferences/migrate-dev.md    - Development migrationsreferences/migrate-deploy.md - Production migrationsreferences/migrate-reset.md  - Database resetreferences/migrate-status.md - Migration statusreferences/migrate-resolve.md - Migration resolutionreferences/migrate-diff.md   - Schema diffingreferences/studio.md         - Database GUIreferences/mcp.md            - Prisma MCP serverreferences/validate.md       - Schema validationreferences/format.md         - Schema formattingreferences/debug.md          - Debug info``` ## How to Use Use the command categories above for navigation, then open the specific command reference file you need.