The body is lean and assumes competence; the schema-validation explanation is Convex-specific behavior Claude would not already know, so it earns its place rather than padding.

Provides executable schema snippets and copy-paste commands such as `npx convex run migrations:myMigration '{"dryRun": true}'`, with deeper migration code appropriately deferred to references.

The breaking-change workflow is sequenced as Deploy 1 / Migrate / Deploy 2 with explicit validation checkpoints (dry run, "Verify all documents are migrated") and a closing checklist.

The body is an overview that points to two real, one-level-deep reference files (migrations-component.md, migration-patterns.md), each clearly signaled with what it contains.

Names the domain and methodology ("Plans Convex schema and data migrations with widen-migrate-narrow and @convex-dev/migrations"), but the actions collapse to a single verb rather than a list of distinct concrete actions as in the anchor-3 example.

Explicitly states what it does and provides a "Use for ..." trigger clause covering multiple scenarios, answering both what and when.

"breaking schema changes, backfills, table reshaping, zero-downtime rollouts" gives good coverage of natural terms a Convex user would actually say.

The Convex-specific migration niche with distinct triggers makes it unlikely to fire for the wrong skill.