What problem does it solve? Changing the schema of a live Convex app risks breaking existing data: tightening a validator before old rows are updated causes the deployment to reject them. This Skill provides a safe, staged workflow for evolving a production schema without downtime or data loss. ## Core Features & Use Cases - Staged schema changes: Add new fields as optional first so the deploy never rejects existing rows. - Guided backfills: Install @convex-dev/migrations and write a migration that transforms or backfills existing rows. - Verification before tightening: Check row counts and validity before making a field required. - Use Case: You need to add a required role field to an existing users table in production. The Skill walks you through adding it as optional, running a backfill migration, verifying all rows, and only then tightening the validator. ## Quick Start Ask the agent to migrate my live Convex schema by adding a new required field and backfilling existing rows with @convex-dev/migrations.
