What problem does it solve? Schema changes in a multi-service .NET backend are risky: a badly written migration can drop production data, break NOT NULL constraints on existing rows, or fail to roll back. This Skill enforces a disciplined EF Core migration workflow so every schema change is named clearly, seeded safely, and rollback-tested before commit. ## Core Features & Use Cases - Standardized migration commands: Create and apply migrations with the correct -p (Infrastructure project) and -s (startup project) flags for each microservice. - Safe NOT NULL handling: Seed existing rows with migrationBuilder.Sql before adding constraints, and always provide defaultValue. - Mandatory rollback test: Revert to the previous migration and re-apply to prove Down() works before committing. - Use Case: You add a status column to the batteries table. The Skill guides you to name the migration AddBatteryStatusColumn, seed existing rows, set a default value, and verify rollback — instead of shipping a migration that fails on production data. ## Quick Start Ask the AI to create and apply an EF Core migration for your entity change, following the migration checklist including the rollback test.