template-smart-defaults

Applies cross-parameter default rules when creating .NET projects with dotnet new.

Updated Sep 22, 2026
One-click install
npx skills add https://github.com/bytecakelake/Nurse-Scheduler --skill template-smart-defaults-bytecakelake
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: template-smart-defaults
Source: https://github.com/bytecakelake/Nurse-Scheduler/tree/main/.agents/plugins/dotnet-template-engine/skills/template-smart-defaults
Command: npx skills add https://github.com/bytecakelake/Nurse-Scheduler --skill template-smart-defaults-bytecakelake

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about template-smart-defaults

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose the right target framework for dotnet new with native AOT?▼

Native AOT requires a recent AOT-capable target framework, so pair `--aot` with the latest framework listed in the template's `--framework` choices. Confirm availability with `dotnet new <template> --help`, since not every template exposes an `--aot` flag.

Should I disable HTTPS when using authentication in a dotnet new project?▼

No, keep HTTPS when `--auth` is set to anything other than None. Authentication flows such as cookies, tokens, and redirects depend on HTTPS, so passing `--no-https` would break them.

Can I use controllers and minimal APIs together in one dotnet new command?▼

No, controllers and minimal APIs are mutually exclusive program models. If `--use-controllers` is set, do not also pass a minimal-API flag, and include only the flag you actually intend to use in the final command.

Does dotnet new have a --publish-aot flag for native AOT?▼

No, there is no `--publish-aot` template flag. Publish-time native AOT is enabled with the MSBuild property `PublishAot=true` via `dotnet publish` or in the `.csproj` file, while `--aot` exists only on templates whose help output lists it.

When should smart defaults not override my dotnet new parameters?▼

Smart defaults only fill parameters you left unset; any value you set explicitly is always preserved. A framework pinned by the workspace or `global.json` also counts as set and is kept unless incompatible with AOT.