What problem does it solve? Setting up a .NET solution involves many shared configuration files - .slnx, Directory.Build.props, Directory.Packages.props, global.json, and dotnet-tools.json - and getting them wrong leads to version drift, inconsistent builds across machines, and duplicated per-project settings. ## Core Features & Use Cases - Canonical solution layout: Organizes production code under src/ and tests under tests/, with a single .slnx solution file that diffs and merges cleanly. - Shared build configuration: Centralizes language baseline, target frameworks, and global usings in Directory.Build.props, and pins the SDK via global.json with rollForward policies. - Central package and tool management: Covers Directory.Packages.props for NuGet versions and .config/dotnet-tools.json for pinned CLI tools like dotnet-ef and csharpier, plus .NET Framework 4.8 specifics. - Use Case: You are starting a new ASP.NET API with a core library and test project. Use this Skill to scaffold the solution, pin the SDK, enable central package management, and add projects without hand-editing XML. ## Quick Start Set up a new .NET solution named MyApp with an src and tests layout, a .slnx solution file, central package management, and a pinned SDK in global.json.
