What problem does it solve?
When creating .NET projects with dotnet new, related template parameters often interact in non-obvious ways — native AOT needs a compatible target framework, authentication requires HTTPS, and controllers conflict with minimal APIs. This Skill fills unset parameters with consistent defaults while never overriding values the user explicitly chose.
Core Features & Use Cases
- Cross-parameter default rules: Pairs
--aot with the latest AOT-capable framework, keeps HTTPS when --auth is set, and prevents contradictory controller/minimal-API flag combinations.
- Transparent decision log: Emits a "Defaults applied" table marking each value as
Source = user or Source = rule, plus the exact single dotnet new command containing only flags actually passed.
- Safe advice-only mode: Appends
--dry-run to displayed commands when the user asks for guidance without creating files, and verifies flag names against dotnet new <template> --help.
- Use Case: A user asks to create an AOT-enabled web API with individual authentication but no framework specified. The Skill selects the latest AOT-compatible TFM, keeps HTTPS, preserves the explicit
--auth Individual, and outputs the exact command with a full audit log.
Quick Start
Ask the agent to create a native AOT web API project with individual authentication and let it fill in the remaining dotnet new parameters with sensible defaults.