Extend dev-software-engineer with .NET/C# backend specialization for Clean Architecture, CQRS, EF Core, and production-ready API practices. Use when tasks involve ASP.NET endpoints, handlers, services, dependency injection, MediatR, migrations, or backend performance/resilience and should follow the base implementation workflow.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
../dev-software-engineer/SKILL.md as the base contract..github/instructions/repository-operating-model.instructions.md as the canonical repo-operating reference inherited from the base skill..github/instructions/dotnet-csharp.instructions.md.github/instructions/clean-architecture-code.instructions.md.github/instructions/backend.instructions.md.github/instructions/database.instructions.md.github/instructions/orm.instructions.md.github/instructions/microservices-performance.instructions.md (when applicable).github/prompts/create-dotnet-class.prompt.md.github/prompts/create-api-endpoint.prompt.md.github/prompts/create-ef-migration.prompt.md.github/prompts/refactor-to-clean-architecture.prompt.md$SecurityScriptsRoot = Join-Path $env:USERPROFILE '.codex\shared-scripts\security'
pwsh -File (Join-Path $SecurityScriptsRoot 'Invoke-VulnerabilityAudit.ps1') -RepoRoot $PWD -SolutionPath NetToolsKit.sln -FailOnSeverities Critical,High
dotnet build
dotnet test --filter "Category=Unit"
dotnet test --filter "Category=Integration"
dotnet pack -c Release
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use for non-trivial feature, behavior, workflow, or architecture work before execution planning. Create or update a versioned spec under planning/specs/active with design intent, alternatives, risks, acceptance criteria, and planning readiness.
The English summary is being prepared. Showing the original description.
Use for non-trivial, design-bearing, or architecture-affecting work before execution planning. Creates or updates a versioned spec under planning/specs/active/ with design intent, alternatives, risks, and acceptance criteria.
The English summary is being prepared. Showing the original description.
Build a minimal context pack and recommend the correct specialist path for token-efficient execution. Use when the task is non-trivial, spans multiple domains, or should reduce token usage before implementation.
The English summary is being prepared. Showing the original description.
Assembles the minimal context pack for a given task. Use when the task spans multiple domains or the context set has obvious redundancy. Do not trim required working context by default.
The English summary is being prepared. Showing the original description.
Route tasks using this repository's static routing catalog and load only the minimal context pack.
The English summary is being prepared. Showing the original description.
Route tasks using the repository's static routing catalog and load only the minimal context pack. Use before execution when the task spans multiple domains or the correct instruction set is unclear.
The English summary is being prepared. Showing the original description.