This covers the modern .NET project setup that Microsoft has been pushing since .NET 9, particularly the new .slnx XML solution format that actually makes sense in version control. You get the full picture: Directory.Build.props for centralizing compiler settings and metadata, Directory.Packages.props for managing NuGet versions in one place instead of scattered across dozens of csproj files, SourceLink configuration for debugging into your published packages, and global.json for pinning SDK versions. The migration guidance from .sln to .slnx is solid, including the critical warning about not keeping both formats around. If you're still manually updating version numbers in individual project files or dealing with merge conflicts in those old GUID-riddled .sln files, this is your blueprint for fixing it.
npx skills add https://github.com/aaronontheweb/dotnet-skills --skill dotnet-project-structure