tooling-csharp-generator_skill

Overview

This skill scaffolds modern C# .NET projects and configures tooling end-to-end. It generates cross-platform project layouts, csproj templates, test projects (xUnit/NUnit/MSTest), StyleCop/roslyn analyzers, and packaging options for NuGet and Docker. It targets .NET 6/7/8 and common project types (library, console, web-api, blazor, wpf, maui).

How this skill works

Given validated inputs (project_name, project_type, dotnet_version, test_framework), the skill emits a directory structure, syntactically valid project files, solution entries, and CI/publishing artifacts. It provides optional levels: T1 basic scaffolding, T2 full tooling with tests and analyzers, and T3 advanced packaging (NuGet, native AOT, Docker, GitHub Actions). Outputs include recommended dotnet commands and next steps plus a NOW_ET timestamp for citations.

When to use it

• Starting a new .NET 6/7/8 project that needs modern defaults
• Creating ASP.NET Core Web APIs or Blazor single-page apps
• Building libraries for NuGet distribution or multi-targeting
• Setting up test projects with xUnit, NUnit, or MSTest
• Packaging apps for Docker or native AOT publishing

Best practices

• Validate project_name as a .NET identifier (PascalCase recommended) and enforce no spaces or special chars
• Prefer .NET 8.0 for new work; use 6.0 for long-term compatibility
• Include StyleCop.Analyzers and an .editorconfig at solution root to enforce consistent style
• Keep test projects IsPackable=false and reference source projects via ProjectReference
• Enable GeneratePackageOnBuild and SourceLink for NuGet packages; use CI to automate build/test/publish

Example use cases

• Generate a class library with multi-targeting and NuGet packaging metadata for immediate publishing
• Scaffold an ASP.NET Core minimal web-api with Swagger, HTTPS redirection, and Dockerfile for container deployment
• Create a console app with native AOT publish and cross-platform Docker CI pipeline
• Set up a repository with src/, tests/, solution file, StyleCop rules and GitHub Actions for build/test/coverage
• Migrate a library to net8.0, add analyzers, and produce a .snupkg symbol package