build-dotnetlisted
Install: claude install-skill JorgeCostaMacia/skills
# Building .NET repositories
The conventions every repo follows; how MSBuild itself works is the `dotnet-msbuild` skill's (from the dotnet/skills marketplace, not this one). Code style and its gates are `code-style-dotnet`'s.
## Directory.Build.props — three tiers
- **Root** — what every project shares:
- the repo's identity (`Authors`, `Company`, `Copyright`, `RepositoryUrl`, `RepositoryType`) and the **`VersionPrefix`**;
- `TargetFramework`, `ImplicitUsings`, `Nullable`, `AnalysisLevel latest`, `EnforceCodeStyleInBuild`, `TreatWarningsAsErrors`;
- `IsPackable false` by default — a project packs only by saying so;
- the vulnerability audit (below).
- **`src/`** — only where `src` packs (a library): imports the root, then the package output — `GenerateDocumentationFile` (on for a library with outside consumers; a contracts repo turns it off on purpose, see `code-style-dotnet`), icon, readme, license, SourceLink (`Microsoft.SourceLink.GitHub`), symbols (`snupkg`), `Deterministic`, `ContinuousIntegrationBuild` on CI, and the files packed into every package.
- **`test/`** — imports the root, then the test settings (see `testing-dotnet`).
- Each lower tier starts with `<Import Project="$([MSBuild]::GetPathOfFileAbove('Directory.Build.props', '$(MSBuildThisFileDirectory)../'))" />` — a `Directory.Build.props` does not inherit the one above on its own.
- **A `.csproj` declares only what is its own**: references, and for a package its `Description` / `PackageTags`. Everyt