This skill should be used when the user asks to "configure prisma", "prisma config", "set up prisma", "prisma orm", "work with prisma", or mentions general Prisma ORM questions. For specific topics, focused skills may be more appropriate.
From prisma-devnpx claudepluginhub nthplusio/functional-claude --plugin prisma-devThis skill uses the workspace's default tool permissions.
references/cli-reference.mdreferences/common-patterns.mdSearches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Guides idea refinement into designs: explores context, asks questions one-by-one, proposes approaches, presents sections for approval, writes/review specs before coding.
Configure and work with Prisma ORM in Node.js/TypeScript projects, focusing on schema design, migrations, and query patterns.
Always use prisma migrate dev for schema changes. Never use prisma db push on projects with existing migration history.
db push bypasses the migration system — migrate deploy (used in Docker/CI/CD) will not see those changes. Use migrate dev for every schema edit, commit the generated migration files alongside schema.prisma.
Before proceeding with any Prisma work, verify the repository has been analyzed:
${CLAUDE_PLUGIN_ROOT}/.cache/recon.json (if it exists)Standard Prisma setup in a project:
project/
├── prisma/
│ ├── schema.prisma # Main schema file
│ ├── migrations/ # Migration history (managed by prisma migrate)
│ │ ├── 20240101_init/
│ │ │ └── migration.sql
│ │ └── migration_lock.toml
│ └── seed.ts # Optional seed script
├── node_modules/
│ └── .prisma/client/ # Generated client
└── package.json
| Command | Purpose |
|---|---|
npx prisma init | Initialize Prisma in a project |
npx prisma generate | Generate Prisma Client from schema |
npx prisma db push | Push schema to database (no migration) |
npx prisma migrate dev | Create and apply migration (dev) |
npx prisma migrate deploy | Apply migrations (production) |
npx prisma studio | Open database GUI |
npx prisma format | Format schema file |
For specific Prisma topics, use these focused skills:
| Topic | Skill | Trigger Phrases |
|---|---|---|
| Schema Design | /prisma-dev:prisma-schema | "prisma model", "schema.prisma", "relations", "@@index" |
| Migrations | /prisma-dev:prisma-migrations | "prisma migrate", "migration", "database changes" |
| Queries | /prisma-dev:prisma-queries | "prisma client", "findMany", "create", "transactions" |
| Repository Analysis | /prisma-dev:prisma-recon | "analyze prisma", "prisma setup", "schema recon" |
Important: This plugin blocks manual creation of migration files in prisma/migrations/.
Always use the Prisma CLI to create migrations:
# Create a new migration (interactive - names the migration)
npx prisma migrate dev --name descriptive_name
# Create migration without applying (for review)
npx prisma migrate dev --create-only --name descriptive_name
Never manually create .sql files in the migrations folder.
# Initialize Prisma
npx prisma init
# Configure datasource in schema.prisma
# Add models to schema.prisma
# Create the initial migration and apply it
npx prisma migrate dev --name init
# Prisma Client is regenerated automatically
schema.prismanpx prisma migrate dev --name change_description# Apply pending migrations
npx prisma migrate deploy
# Generate client (if not in build step)
npx prisma generate
For debugging Prisma issues, the prisma-troubleshoot agent can autonomously diagnose and fix common problems.
references/cli-reference.md - Complete CLI command referencereferences/common-patterns.md - Common schema and query patterns