skills.rest
mkerchenski
mkerchenskiCOMMUNITY
Explore all skills by this author →
GitHub

dotnet-project-setup

Create or reorganize .NET solutions with shared SDK and MSBuild defaults.

1|Updated Mar 25, 2026
Search Tags:#.net#msbuild#directory.build.props#solution structure#central package management#test projects#ci templates
One-click install
npx skills add https://github.com/mkerchenski/hurrah-tv --skill dotnet-project-setup-mkerchenski
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dotnet-project-setup
Source: https://github.com/mkerchenski/hurrah-tv/tree/main/.claude/skills/dotnet-project-setup
Command: npx skills add https://github.com/mkerchenski/hurrah-tv --skill dotnet-project-setup-mkerchenski

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents messy, inconsistent .NET solution structures by giving you a repeatable way to create or reorganize solutions with clear boundaries and maintainable shared build settings.

Core Features & Use Cases

  • Solution & project structuring guidance: Establishes a consistent directory and naming convention for product code, infrastructure, web/API layers, and test projects.
  • Repository-wide SDK/MSBuild configuration: Defines how to use Directory.Build.props, Directory.Build.targets, Directory.Packages.props, global.json, and nuget.config to reduce duplication while avoiding harmful overrides.
  • Repeatable build/test/CI baseline: Helps you create test projects and CI hooks early, so new projects don’t drift into unverified templates.

Quick Start

Ask the AI to propose a clean .NET solution structure for a repo with frontend, API, and test projects, including what to put in Directory.Build.props and Directory.Packages.props.

Frequently Asked Questions about dotnet-project-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure a .NET solution to scale cleanly across multiple projects?▼

To structure a scalable .NET solution, establish consistent directory and naming conventions for product code, infrastructure, web/API layers, and test projects. This creates clear boundaries and maintainable shared build settings across the entire repository.

What is the best way to configure MSBuild defaults across a .NET repository?▼

The best way to configure repository-wide MSBuild defaults is using Directory.Build.props and Directory.Build.targets files. These reduce configuration duplication across projects while avoiding harmful overrides, ensuring repeatable builds.

How do I set up Central Package Management in a .NET solution?▼

Central Package Management is set up using Directory.Packages.props to define shared package versions across your .NET solution. This reduces duplication and ensures version consistency when managing dependencies across multiple projects.

Do I need global.json and nuget.config for a contributor-friendly .NET build?▼

Yes, global.json pins the .NET SDK version and nuget.config sets up package sources. Together they create a contributor-friendly build environment by ensuring repeatable, consistent builds across different development machines.

Can I add test projects and CI templates to an existing .NET solution structure?▼

Yes, you can add test projects and CI hooks to an existing .NET solution structure. Establishing these repeatable build and test baselines early prevents new projects from drifting into unverified templates during structural refactors.

When should I reorganize .NET solution boundaries and shared build settings?▼

You should reorganize .NET solution boundaries when your repository suffers from inconsistent project structures or duplicated build configurations. Applying repeatable SDK and MSBuild defaults fixes messy structures and improves maintainability.

Related Skills

Explore More Software Engineering Skills→
codewithmukeshcodewithmukesh
640

project-structure

Standardize .NET solution and project structure with centralized build settings and package versions.

Official
Intermediate
managedcodemanagedcode
466

dotnet-project-setup

Create .NET solutions with centralized MSBuild settings and package management.

Official
Intermediate
devingobledevingoble

dotnet-project-structure

Configure .NET projects with .slnx, Directory.Build.props, and global.json.

Community
Advanced
s205109s205109
2

cck-project-structure

Standardize .NET solution and project structure with .slnx and central package management.

Community
Intermediate