What problem does it solve? MSBuild project files (.csproj, .props, .targets) often accumulate subtle mistakes—unquoted conditions, hardcoded paths, missing incremental build inputs, scattered package versions—that cause broken builds, slow no-op builds, and cross-platform failures. This Skill provides a numbered catalog of 21 anti-patterns so reviewers can systematically audit and clean up build files. ## Core Features & Use Cases - Anti-Pattern Catalog: 21 documented anti-patterns (AP-01 through AP-21), each with a smell, an explanation of why it is harmful, and a concrete BAD-to-GOOD XML transformation. - Severity-Ranked Checklist: A quick-reference table ordering checks by severity, from error-prone unquoted conditions down to style-level noise like restated SDK defaults. - Deep-Dive References: Detailed guidance on PrivateAssets for analyzer packages and on Inputs/Outputs attributes for incremental builds. - Use Case: When reviewing a pull request that modifies Directory.Build.props or a .csproj file, scan it against the catalog to catch issues like property conditions on TargetFramework in .props files (which silently fail for single-targeting projects) before they reach CI. ## Quick Start Review my .csproj and Directory.Build.props files for MSBuild anti-patterns and suggest fixes for each issue found.
