Overview
.NET Application Solution Setup turns a blank working directory into a Codebelt-style application repository with real structure: solution files, app variants, test projects, CI, central package management, repository policies, and the shared assets that keep the output aligned with the broader ecosystem.
The skill is more than a thin wrapper over dotnet new. It collects parameters, chooses the correct app variant, restores shared assets when the installer omits dotfiles, resolves dynamic dependency versions, and checks the generated output against a post-generation checklist.
Concepts
- Variant-aware scaffolding: console, web, MVC, Razor Pages, API, and worker shapes are handled as explicit solution patterns rather than ad-hoc tweaks after generation.
- Manifest-backed assets: shared governance files and dotfiles are treated as required scaffold inputs, with an upstream restore path when the installer strips them.
- Convention-first output: CI, package versions, test environments, and repository hygiene are part of the scaffold contract from the start.
- Prompted parameter collection: the skill deliberately slows down at the start so the rest of the generation can be deterministic.
Usage guidance
Use this skill when a new .NET app should start with the full delivery posture already in place. It is the right fit for greenfield services, internal tools, worker processes, and web applications that need consistent structure across repos.
Let the skill collect the parameters it needs, then allow it to own the file-generation pass. It is most useful when the goal is not simply “make a project compile,” but “make the first commit look like it belongs in a maintained Codebelt repository.”