skills.rest
bbsbot
bbsbotCOMMUNITY
Explore all skills by this author →
GitHub

dotnet-project-structure

Create a modern .NET project structure with .slnx and centralized configuration.

1|Updated Feb 16, 2026
Search Tags:#project structure#nuget#.net#build configuration#sdk pinning#sourcelink
One-click install
npx skills add https://github.com/bbsbot/mac-md-win --skill dotnet-project-structure-bbsbot
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dotnet-project-structure
Source: https://github.com/bbsbot/mac-md-win/tree/main/.claude/skills/dotnet/skills/project-structure
Command: npx skills add https://github.com/bbsbot/mac-md-win --skill dotnet-project-structure-bbsbot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the setup and configuration of modern .NET projects, ensuring consistency, maintainability, and adherence to best practices across your codebase.

Core Features & Use Cases

  • Centralized Configuration: Manages build properties, package versions, and SDK pinning from a single source.
  • Modern Solution Format: Supports the .slnx XML-based solution file for better version control integration.
  • Automated Versioning: Integrates release notes for automated version bumping and package creation.
  • Use Case: When starting a new .NET solution, use this Skill to establish a robust project structure that includes Directory.Build.props, Directory.Packages.props, global.json, and SourceLink configuration, setting a solid foundation for development.

Quick Start

Apply the dotnet-project-structure skill to initialize a new .NET solution with best practices.

Frequently Asked Questions about dotnet-project-structure

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

FAQPage Schema
How do I set up central package management in a .NET project?▼

Central package management in a .NET project uses Directory.Packages.props to control NuGet package versions from a single file, ensuring version consistency across all projects in the solution.

What is the .slnx solution format and when should I use it?▼

The .slnx solution format is an XML-based solution file for .NET projects that offers better version control integration and readability compared to traditional .sln files.

How do I centralize build properties across multiple .NET projects?▼

You can centralize build properties across multiple .NET projects using Directory.Build.props, which automatically applies shared MSBuild configurations to all projects within the folder hierarchy.

What's the best way to pin the .NET SDK version for a solution?▼

The best way to pin the .NET SDK version is by using a global.json file, which specifies the exact SDK version required and ensures all developers use a consistent build environment.

Can I automate version bumping using release notes in a .NET build?▼

Yes, automated version management is possible by integrating RELEASE_NOTES.md with build scripts, which parse release notes to determine and apply the correct version bumps during package creation.

Does SourceLink integration work with central build configuration?▼

SourceLink integration works seamlessly with central build configuration by adding properties to Directory.Build.props, enabling source debugging for NuGet packages across the entire solution.

Related Skills

Explore More Software Engineering Skills→
MakisuoMakisuo
1.6k

clickhousectl-local-dev

Install and configure a local ClickHouse environment with clickhousectl.

Community
Intermediate
ntaksh42ntaksh42
1

azure-artifacts-manager

Create package feeds for npm, NuGet, Maven, and Python in Azure Artifacts.

Community
Intermediate
aRustyDevaRustyDev
7

pkgmgr-homebrew-formula-dev

Create, test, and maintain Homebrew formulas with livecheck integration.

Community
Intermediate
NotMyselfNotMyself
14

dotnet-cli-essentials

Manage .NET 10 projects with standard dotnet CLI commands.

Community
Basic