Codebelt

.NET Library Solution Setup

A library-scaffolding skill for maintainers who want a NuGet repository that is ready for stewardship, not just compilation.

.NET · NuGet · Engineering 3 installs .NET libraries NuGet packages CLI agents IDE agents
Open on Skills.sh View source

Overview

.NET Library Solution Setup scaffolds a new Codebelt-style library repository around the realities of shipping a NuGet package: multi-targeting, release notes, DocFX, benchmarking, packaging metadata, governance files, and strong-name expectations. The generated solution is meant to be stewarded, versioned, and published, not abandoned after the first successful build.

Like the application variant, the skill handles more than project creation. It resolves dependency versions, applies shared templates, fills project-specific placeholders, generates tuning and tooling projects, and checks the finished scaffold against a release-minded checklist.

Concepts

  • Package stewardship from day one: .nuget/ metadata, README content, release notes, and source/package URLs are part of the scaffold contract.
  • Library-specific topology: source, tests, tuning benchmarks, tooling runners, and DocFX assets are generated as a connected solution rather than bolted on later.
  • Dynamic dependency resolution: package placeholders are resolved against live NuGet data instead of frozen example versions.
  • Signing-aware workflow: the skill is designed to hand off naturally to dotnet-strong-name-signing once the solution skeleton exists.

Usage guidance

Use this skill when the output is intended to become a reusable package rather than an internal one-off project. It is especially helpful when consistency across multiple libraries matters more than generating the smallest possible starter template.

Let it own the scaffold while you focus on naming, target frameworks, and publishing intent. The payoff is a repository that already knows how it will be built, documented, benchmarked, versioned, and released.