From dotnet-ddd
Add a new endpoint/action to an existing aggregate's controller and application service in a .NET DDD API, without scaffolding a whole new aggregate. Use for "add a GET/POST/search/... to the X API".
How this skill is triggered — by the user, by Claude, or both
Slash command
/dotnet-ddd:new-endpointThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Add the operation described in `$ARGUMENTS` (e.g. "search Products by name") to an existing
Add the operation described in $ARGUMENTS (e.g. "search Products by name") to an existing
aggregate. Follow AGENTS.md.
*ApplicationService, *Controller, and repo interface.I<Name>ApplicationService and implement it, returning Result/Result<T>, with CancellationToken ct = default.I<Name>Repository and implement it in <Name>Repository (AsNoTracking() for reads). Do not add CRUD that the generic Repository<T> already covers.*.Application.DTO/<Name>/ if the shape is new; map via Mapster in Transversal, not inline.Result → IActionResult, keep authorization consistent.dotnet build and dotnet test.No domain change unless the operation introduces a new invariant — if it does, put it in the domain service, not the application service.
npx claudepluginhub jino-labs/ai-agent-framework --plugin dotnet-dddCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.