What problem does it solve? MSBuild project and build files often accumulate subtle authoring mistakes—unquoted conditions, hardcoded paths, missing incremental-build metadata, redundant references—that cause broken builds, slow no-op builds, and flaky parallel-build failures. This Skill provides a numbered catalog of 23 anti-patterns, each with a symptom, an explanation of the impact, and a concrete BAD→GOOD fix. ## Core Features & Use Cases - Anti-Pattern Detection: Scan .csproj, .vbproj, .fsproj, .props, .targets, and Directory.Build.props/.targets files for 23 cataloged issues with severity ratings (Error, Warning, Style). - Concrete Fixes: Every entry includes a BAD→GOOD XML transformation, covering Exec misuse, condition quoting, PrivateAssets, Central Package Management, Inputs/Outputs, and ProjectReference instance forking. - Use Case: When a CI build intermittently fails with file-lock errors, use the catalog to identify AP-22/AP-23 (path-neutral global properties forking a second project instance that races the same bin/obj output) and apply the single-instance fix. ## Quick Start Review my Directory.Build.props and all .csproj files for MSBuild anti-patterns and suggest fixes.
