dotnet-project-setup

Organize .NET repositories into solution layouts with Directory.Build.props and Central Package Management.

8|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/Postpartum-genushyacinthus29/dotnet-skills --skill dotnet-project-setup-postpartum-genushyacinthus29
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-project-setup
Source: https://github.com/Postpartum-genushyacinthus29/dotnet-skills/tree/main/skills/dotnet-project-setup
Command: npx skills add https://github.com/Postpartum-genushyacinthus29/dotnet-skills --skill dotnet-project-setup-postpartum-genushyacinthus29

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Organizes and reorganizes .NET repositories into clean, scalable solution layouts with centralized build defaults and bounded project boundaries.

Core Features & Use Cases

  • Establishes a maintainable solution skeleton with Directory.Build.props and Central Package Management to reduce drift.
  • Provides guidance for organizing apps, libraries, tests, and tooling to support consistent navigation and contributor onboarding.
  • Use Case: when starting a new repo or refactoring an existing solution, apply a standard layout to accelerate setup and ensure consistent builds.

Quick Start

Organize a new or existing .NET repository by establishing a clean solution layout and centralized build defaults.

Frequently Asked Questions about dotnet-project-setup

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

FAQPage Schema
How do I organize a .NET solution layout for a new repository?

Organize a .NET solution layout by applying a conventional skeleton with Directory.Build.props, Central Package Management, and starter templates for core, api, and tests to ensure consistent builds and navigation.

What is the best way to structure a .NET project refactor with bounded contexts?

The best way to structure a .NET project refactor is to apply a clean, scalable solution layout that establishes bounded project boundaries and centralized build defaults to reduce configuration drift.

When do I need Central Package Management in a .NET project structure?

You need Central Package Management in a .NET project structure when establishing a maintainable solution skeleton and wanting to reduce dependency drift across multiple projects within the same repository.

Can I use Directory.Build.props to centralize settings across all .NET projects in a solution?

Yes, you can use Directory.Build.props to centralize build defaults across apps, libraries, tests, and tooling, which supports consistent contributor onboarding and reduces configuration drift in .NET repositories.

Does this .NET solution layout approach work for both new repos and existing refactors?

Yes, this .NET solution layout approach works for both new repositories and major refactors requiring bounded contexts and centralized build settings to accelerate setup and ensure consistent builds.

What starter templates are included in a conventional .NET solution skeleton?

A conventional .NET solution skeleton includes starter templates for core, api, and tests, providing guidance for organizing apps, libraries, tests, and tooling to support consistent navigation.