Populate Prisma databases with idempotent seed data using upsert.
npx skills add https://github.com/theslashdojo/dojo --skill seed-theslashdojo
Please help me install this Agent Skill. Skill: seed Source: https://github.com/theslashdojo/dojo/tree/main/nodes/prisma/seed Command: npx skills add https://github.com/theslashdojo/dojo --skill seed-theslashdojo
Database initialization and test fixture creation are repetitive and fragile tasks that often fail on duplicate keys or require manual scripts per project. Prisma seed scripts, when misconfigured, can be non-idempotent, hang the process, or be difficult to integrate into migration workflows. This Skill centralizes best practices for creating safe, repeatable seeds that developers can run reliably in development and test environments.
Create a prisma/seed.ts that uses upsert for your core models, add prisma.seed to package.json to run tsx prisma/seed.ts, and run npx prisma db seed to populate the database.
High-intent search queries and answers about installing and using this skill.
To make Prisma seed scripts idempotent, use the upsert operation with an update: {} pattern for your core models. This allows the seed script to run multiple times safely without triggering P2002 duplicate key errors in development and test environments.
Configuring a Prisma seed script requires adding a prisma.seed entry in package.json pointing to a TypeScript runner like tsx. Once configured, you execute the script to populate the database by running the npx prisma db seed command.
The best way to generate bulk test fixtures with Prisma is to combine the createMany method for bulk inserts with @faker-js/faker for realistic data generation. This approach efficiently populates lookup tables and creates load data for test environments.
Yes, Prisma db seed supports repopulating data after applying migrations. By configuring idempotent seed scripts via prisma.seed in package.json, developers can reliably initialize fresh development databases with admin users and sample posts post-migration.
Prisma seed scripts hang or fail when run multiple times if they use standard create operations instead of idempotent upsert patterns. Implementing upsert with an empty update object prevents duplicate key conflicts and ensures the process exits cleanly.
itsnex1sAutomate Prisma migrations, seeding, and client generation with Node.js.
SumitRajpalGenerate 5–10 realistic seed records per Prisma model with upsert logic.
thbehGenerate synthetic datasets with Faker and store them in Databricks volumes.
ClawLink-HQAutomate Prisma PostgreSQL database management and schema querying via OAuth 2.0.
