bootstrap-solution

Bootstrap .NET Solution

Purpose

Create or guide a reproducible .NET solution scaffold without making C# the silent default.

The user should leave with a clear project layout, explicit F# or C# choice, predictable SDK behavior, and validation commands that prove the scaffold works.

When To Use

• Use this skill when creating a new .NET solution or project.
• Use this skill when adding a test project to an existing .NET repository.
• Use this skill when a repo needs global.json, solution-level layout, or explicit validation commands.
• Use this skill after dotnet:choose-project-shape when the project shape is settled.

Source Check

Use repo-local .NET files, checked-out dependency sources, Dash MCP or Dash HTTP for installed .NET docsets, and then official Microsoft documentation when Dash/local coverage is missing or stale:

• .NET CLI documentation
• dotnet new documentation
• global.json documentation
• dotnet build documentation
• dotnet test documentation

Check the local SDK only when implementation actually needs it:

dotnet --info
dotnet --list-sdks

Required Inputs

• target path
• project or solution name
• project shape
• language: F#, C#, or mixed
• test project expectation
• test framework expectation; default to xUnit for new scaffolds unless the repo or user chooses another framework
• SDK pinning expectation
• git initialization or commit expectation

If the user has not selected F# or C#, ask before scaffolding.

Guidance Workflow

1. Inspect the target:
   • existing files
   • git state
   • .sln or .slnx
   • global.json
   • Directory.Build.props
   • .fsproj or .csproj
2. Confirm the project shape and language.
3. Choose SDK behavior:
   • use existing global.json when present
   • add global.json when reproducibility matters and the user accepts the SDK pin
   • avoid inventing a machine-local SDK path
4. Create projects with the dotnet CLI.
5. Add project references.
6. Add tests when the project has behavior worth preserving. Use the existing repo test framework if one exists; otherwise default new scaffolds to xUnit.
7. Run validation.
8. Report the generated paths and exact commands.