prisma-dev
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.
What this skill does
# Prisma Development
Configure and work with Prisma ORM in Node.js/TypeScript projects, focusing on schema design, migrations, and query patterns.
## Migration-First Policy
**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`.
## First Actions
### 1. Check Repository Recon
Before proceeding with any Prisma work, verify the repository has been analyzed:
1. Read `${CLAUDE_PLUGIN_ROOT}/.cache/recon.json` (if it exists)
2. Check if schema location and model structure are cached
3. If missing or stale, run the prisma-recon skill to analyze the repository
4. Use cached information to provide context-aware guidance
## Prisma Project Structure
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
```
## Core Prisma Commands
| 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 |
## Focused Skills
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" |
## Migration Safety
**Important:** This plugin blocks manual creation of migration files in `prisma/migrations/`.
Always use the Prisma CLI to create migrations:
```bash
# 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.
## Common Workflows
### Initial Setup
```bash
# 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 Changes
1. Modify `schema.prisma`
2. Run `npx prisma migrate dev --name change_description`
3. Prisma Client auto-regenerates
4. Update application code if needed
### Production Deployment
```bash
# Apply pending migrations
npx prisma migrate deploy
# Generate client (if not in build step)
npx prisma generate
```
## Troubleshooting
For debugging Prisma issues, the prisma-troubleshoot agent can autonomously diagnose and fix common problems.
## Reference Files
- **`references/cli-reference.md`** - Complete CLI command reference
- **`references/common-patterns.md`** - Common schema and query patterns
## Resources
- Official docs: https://www.prisma.io/docs
- GitHub: https://github.com/prisma/prisma
- Prisma Examples: https://github.com/prisma/prisma-examples
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.