nuget-package-scaffoldlisted

# NuGet Package Scaffold > "The best libraries are those that disappear into the code that uses them." > -- Krzysztof Cwalina, Framework Design Guidelines ## Core Philosophy This skill scaffolds production-ready NuGet packages with proper metadata, testing, CI/CD pipelines, and publish workflows. Every package must meet a quality bar before it reaches any feed. **Non-negotiable constraints:** 1. **No publish without tests** -- a package without a passing test suite is not a package, it is a liability 2. **Semantic versioning is law** -- every version bump must communicate intent: breaking, feature, or fix 3. **Metadata is not optional** -- description, license, authors, repository URL, and README are required before first publish 4. **Multi-target when possible** -- support the broadest reasonable set of target frameworks for your consumers 5. **Deterministic builds** -- the same source must produce the same binary, every time The full domain principles, knowledge-base lookup protocol, AI discipline rules, anti-patterns, and error-recovery procedures live in `references/conventions.md`. ## Workflow Six-step pipeline: **Scaffold → Configure → Test → Pack → Publish** (with iterate back if needed). ### Step 1: Scaffold Create the solution structure: ``` PackageName/ ├── src/ │ └── PackageName/ │ ├── PackageName.csproj │ └── Class1.cs ├── tests/ │ └── PackageName.Tests/ │ ├── PackageName.Tests.csproj │ └── Class1Tests.cs ├── .github/ │ └──