From dotnet-ddd
Create and apply an EF Core migration for a .NET DDD API, targeting the Infrastructure project with the API as startup. Use when the model changed and the database schema needs to follow.
How this skill is triggered — by the user, by Claude, or both
Slash command
/dotnet-ddd:add-migrationThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Create (and optionally apply) an EF Core migration named after `$ARGUMENTS`. Follow `AGENTS.md`.
Create (and optionally apply) an EF Core migration named after $ARGUMENTS. Follow AGENTS.md.
dotnet-ef is available: dotnet ef --version. If missing: dotnet tool install --global dotnet-ef.*.Infrastructure.Data.Repositories (holds ApplicationDbContext); the startup project is *.API. Glob to get the real names.DbSet<> in ApplicationDbContext and an IEntityTypeConfiguration in Configurations/. A migration over an unconfigured entity is the usual cause of a wrong/empty diff.dotnet ef migrations add <Name> -p <Infrastructure.Data.Repositories> -s <API>
Up/Down before applying — confirm it matches the intended schema change and isn't dropping data unexpectedly.dotnet ef database update -p <Infrastructure.Data.Repositories> -s <API>
Name the migration after the change (Add_Order, Add_Product_Sku), not a version number.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub jino-labs/ai-agent-framework --plugin dotnet-ddd