What problem does it solve? Development database seeds often fail on re-run, require a database reset first, produce unrealistically clean data that hides UI bugs, or worse — risk running against a production database through a pasted connection string. This Skill provides the rules and guardrails for writing seeds that are safe, re-runnable, and realistic. ## Core Features & Use Cases - Production Safety Guard: Enforces a three-part check (NODE_ENV, deploy-platform variables, and a database host allowlist) in a dedicated, unit-tested prisma/seed-guard.ts module so a seed can never rewrite production data. - Idempotent Seeding: Requires upserts on natural keys (slugs, emails, external identifiers) so running the seed twice yields the same state as one run. - Minimal Mode & Realistic Fixtures: Defines a --minimal flag for onboarding and empty-state testing, and directs copying real production data shapes (long names, near-duplicates, hash collisions) instead of inventing tidy values. - Use Case: When adding a new fixture to prisma/seeders/, use this Skill to ensure the fixture upserts on a natural key, links correctly to other fixtures, and survives a second pnpm db:seed run. ## Quick Start Review my prisma/seed.ts and seeders to make the seed idempotent, add a production safety guard, and support a minimal mode.
