Loading...
Loading...
Found 8 Skills
Choosing CLI output format. AOT vs framework-dependent, RID matrix, single-file, dotnet tool.
Manage NuGet packages in .NET projects/solutions. Use this skill when adding, removing, or updating NuGet package versions. It enforces using `dotnet` CLI for package management and provides strict procedures for direct file edits only when updating versions.
Managing local .NET tools with dotnet-tools.json for consistent tooling across development environments and CI/CD pipelines.
Helps find, inspect, and compare .NET project templates. Resolves natural-language project descriptions to ranked template matches with pre-filled parameters. USE FOR: finding the right dotnet new template for a task, comparing templates side by side, inspecting template parameters and constraints, understanding what a template produces before creating a project, resolving intent like "web API with auth" to concrete template + parameters. DO NOT USE FOR: actually creating projects (use template-instantiation), authoring custom templates (use template-authoring), MSBuild or build issues (use dotnet-msbuild plugin), NuGet package management unrelated to template packages.
C# and .NET development expert using the dotnet CLI.
Manage NuGet packages using Central Package Management (CPM) and dotnet CLI commands. Never edit XML directly - use dotnet add/remove/list commands. Use shared version variables for related packages.
Using System.CommandLine 2.0. Commands, options, SetAction, custom parsing, middleware, testing.
Builds .NET 10 file-based C# apps. Directives, CLI commands, csproj migration.