What problem does it solve? Renaming a table, column, or enum in Prisma is dangerous because prisma migrate dev renders renames as DROP plus CREATE, destroying production data while every test still passes. This Skill provides the operational discipline to perform renames without losing rows or leaving the schema half-migrated. ## Core Features & Use Cases - Hand-written rename migrations: Replace generated DROP/CREATE pairs with explicit ALTER ... RENAME statements wrapped in a single transaction. - Preflight validation: Add header queries with expected row counts to catch drifted constraint and index names before deploy. - Persisted-string sweeps: Write idempotent migrations that update old spellings stored in audit columns, JSON keys, and cached aggregates, with replay tests against old-shape rows. - Deploy-window handling: Re-run sweeps after promotion and choose between in-place rename and expand/contract based on traffic tolerance. - Use Case: You renamed a Prisma model from Proposal to Suggestion and migrate dev produced a DROP TABLE. Use this Skill to hand-write the rename migration, sweep persisted strings, and plan the deploy safely. ## Quick Start Ask the AI to help write a safe Prisma migration for renaming a table or column without losing existing production data.