What problem does it solve? Creating new .NET projects that fit an existing workspace is error-prone: templates hardcode stale package versions, ignore Central Package Management, and default to the wrong target framework. This Skill scaffolds projects with validated parameters, workspace-aware defaults, and verified builds. ## Core Features & Use Cases - Workspace-aware scaffolding: Detects Directory.Packages.props (CPM), existing target frameworks, and global.json before running dotnet new, then mirrors those settings. - CPM adaptation: Strips inline PackageReference versions from generated .csproj files and centralizes them into Directory.Packages.props, with optional tooling-driven version refresh via dotnet list package --outdated. - Multi-project composition: Creates solutions combining API, test, and library projects, wires project references, and adds them to the .sln file. - Use Case: You need a new ASP.NET Core Web API with Individual auth and native AOT plus an xUnit test project inside a repo that uses CPM. The Skill previews with --dry-run, creates both projects, centralizes package versions, and confirms everything builds. ## Quick Start Ask the AI to create a new .NET Web API project named MyApi with Individual authentication in the src folder, respecting the repository's Central Package Management setup.