dotnet-skills
ManagedCode
Platform .NET Foundations v1.0.3

.NET Project Setup

Create or reorganize .NET solutions with clean project boundaries, repeatable SDK settings, and a maintainable baseline for libraries, apps, tests, CI, and local development. USE FOR: creating a new .NET solution or restructuring an existing one; setting up Directory.Build.props, shared package management, or repo-wide defaults; defining project. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.

Trigger On

  • creating a new .NET solution or restructuring an existing one
  • setting up Directory.Build.props, shared package management, or repo-wide defaults
  • defining project layout for apps, libraries, and test projects

Workflow

  1. Start from the app model and deployment target, then choose the smallest correct SDK and target framework set.
  2. Use solution folders and project names that reflect bounded contexts or product areas, not temporary implementation details.
  3. Centralize shared build settings, analyzer rules, nullable context, and package versions where it reduces duplication without hiding important differences.
  4. Create test projects and CI hooks early so new projects do not drift into unverified templates.
  5. Prefer project references and composition over circular dependencies or utility dumping grounds.
  6. Document the local build, test, and run path in repo docs or AGENTS.md when the workflow is not obvious.

Deliver

  • a coherent solution structure
  • shared build defaults that are easy to reason about
  • starter quality and testing hooks for future work

Validate

  • projects have explicit responsibility boundaries
  • shared MSBuild settings do not accidentally override platform-specific needs
  • a new contributor can build and test the repo without guessing

References

  • patterns.md: solution layout conventions, Directory.Build.props, Directory.Build.targets, Central Package Management, global.json, nuget.config, analyzers, multi-targeting, and source link
  • templates.md: dotnet new templates for console apps, class libraries, ASP.NET Core APIs, worker services, Blazor, test projects, .NET Aspire, and gRPC services

Related skills

ManagedCode.Communication

Details →
Library .NET Foundations 1,274 tokens

Use ManagedCode.Communication when a .NET application needs explicit result objects, structured errors, and predictable service or API boundaries instead of exception-driven…

ManagedCode.Communication
dotnet skills install managedcode-communication

ManagedCode.MimeTypes

Details →
Library .NET Foundations 1,176 tokens

Use ManagedCode.MimeTypes when a .NET application needs consistent MIME type detection, extension mapping, and content-type decisions for uploads, downloads, or HTTP responses.

ManagedCode.MimeTypes
dotnet skills install managedcode-mimetypes

Related agents

Orchestration agent
6 linked skills

.NET Build

Build-focused orchestration agent for .NET restore, build, test, packaging, CI failures, diagnostics, and environment drift.

agents install build

Also works: dotnet agents install build

Routes to
project-setup+4 more
Open agent page → Source
Orchestration agent
4 linked skills

.NET Router

Broad .NET triage agent that classifies the repo and routes work to the right skills or specialist agents.

agents install router

Also works: dotnet agents install router

Routes to
dotnet+2 more
Open agent page → Source