What problem does it solve? Changing an entity or its IEntityTypeConfiguration in a .NET API requires a matching database schema migration, and hand-writing migrations is error-prone. This Skill walks through the full EF Core migration workflow so schema changes are generated from the C# model, applied at startup, and committed correctly. ## Core Features & Use Cases - Migration Generation: Runs dotnet ef migrations add against the Tsz.Api project to produce Up/Down migration files, a Designer file, and an updated AppDbContextModelSnapshot. - SQLite-Specific Guidance: Flags table-rebuild behavior for DROP COLUMN and type changes, and shows how to add migrationBuilder.Sql(...) for data backfills on new NOT NULL columns. - Safe Rollback: Explains how to remove a not-yet-applied migration or roll back a locally applied one with dotnet ef database update. - Use Case: After adding a Colour field to the User entity, generate an AddColourToUser migration, backfill existing rows, restart the API so db.Database.Migrate() applies it, and commit the snapshot. ## Quick Start Add an EF Core migration for the entity change I just made in packages/api and apply it to the local SQLite database.