What problem does it solve? When scaffolding .NET projects with dotnet new, related parameters often interact — for example, native AOT requires a recent target framework, and authentication requires HTTPS. Manually keeping these consistent is error-prone, and blindly applying defaults risks overriding values the user explicitly chose. ## Core Features & Use Cases - Cross-parameter default rules: Fills unset parameters based on explicit choices, such as pairing the latest AOT-compatible framework with --aot and keeping HTTPS when --auth is enabled. - Explicit-value protection: Never overrides a parameter the user set, and logs every decision with a Source (user/rule) and rationale. - Decisive command output: Emits a "Defaults applied" table plus the exact single dotnet new command containing only the flags actually passed. - Use Case: A user asks to create a Web API with --aot and --auth Individual but no framework specified. The skill fills --framework with the latest AOT-capable TFM, keeps HTTPS, and outputs the final command. ## Quick Start Ask the agent to apply smart defaults for a dotnet new webapi project where you have set --aot and --auth Individual but left the framework unspecified.