What problem does it solve? MSBuild project files accumulate subtle mistakes—unquoted condition operands, misplaced property defaults, duplicate project instances—that cause build failures, silent wrong values, or slow maintenance. This Skill provides a numbered catalog of 29 antipatterns so reviewers can detect, prove, and correct each smell systematically. ## Core Features & Use Cases - Antipattern Catalog: 29 entries (AP-01 through AP-29) covering evaluation, placement, items and references, targets, execution and paths, and build graph, each with severity (ERROR or STYLE), the failure it causes, the rule, and paired BAD/GOOD XML forms. - Proof Commands: Each section names the verification command, such as dotnet msbuild <project> -getProperty:<Name>, -getItem:<Type>, -pp:, or binlog evaluation analysis. - Worked Examples: A references file with full-file corrections for multi-element fixes like duplicate publish instances, SetTargetFramework forms, host-supplied references, and layer validation targets. - Use Case: When reviewing a pull request that edits Directory.Build.props, check each changed property against the placement section to catch conditions on later values or unconditional overrides before they break the build. ## Quick Start Review my Directory.Build.props and all .csproj files for MSBuild antipatterns and list each violation with its fix.
