What problem does it solve? Legacy .NET projects carry verbose XML, explicit file lists, packages.config, and AssemblyInfo.cs boilerplate that make builds hard to maintain. This Skill provides a step-by-step checklist to convert them into minimal SDK-style projects. ## Core Features & Use Cases - Legacy Detection: Identifies legacy indicators such as ToolsVersion attributes, MSBuildToolsPath imports, explicit Compile includes, and packages.config files. - Step-by-Step Migration: Covers replacing the project root element, mapping TargetFrameworkVersion to TargetFramework TFMs, removing explicit file includes, deleting AssemblyInfo.cs, and converting packages.config to PackageReference. - Consolidation & Modernization: Guides Central Package Management via Directory.Packages.props, shared settings via Directory.Build.props/targets, and enabling Nullable and ImplicitUsings. - Use Case: A 65-line legacy .csproj for a .NET Framework 4.7.2 library is reduced to an 11-line SDK-style project with PackageReference entries, then validated with dotnet build. ## Quick Start Ask the assistant to convert this legacy .csproj file to SDK-style format and migrate its packages.config to PackageReference.