From blueprint
Analyzes a .NET/C# project and configures 9-dimension quality methodology including hooks, CI, and tool configs. Use when user says "set up quality tools", "configure analyzers", "add CI pipeline", "dotnet quality", or wants to apply coding standards to a .NET project.
How this skill is triggered — by the user, by Claude, or both
Slash command
/blueprint:dotnet-setupThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
- **Always present analysis and plan to the user before making changes**
dotnet CLI for all build, test, and format operationschmod +x)Read these files before starting:
skills/shared/references/methodology-framework.md — shared principles, hook architecture, exit codes, settings.json formatskills/shared/references/setup-workflow.md — the 6-phase workflow structureskills/dotnet-setup/references/methodology.md — .NET-specific 9 dimensions, thresholds, tool research guidanceskills/dotnet-setup/references/analysis-checklist.md — what to check in the target codebaseskills/dotnet-setup/templates/ — annotated examples showing structural patterns. Use templates for patterns but substitute the tools chosen during research.Follow the 6-phase workflow from setup-workflow.md.
Follow analysis-checklist.md systematically: .NET SDK version, target framework, solution structure, frameworks, existing tools, CI, maturity.
Research tools for each of the 9 dimensions. .NET-specific files to plan:
Directory.Build.props — centralized MSBuild properties and analyzer packages.editorconfig — formatting and analyzer severity rules.claude/hooks/ — quality-gate.sh, per-edit-fix.sh, session-start.sh, optionally auto-commit.sh.claude/settings.json — hook registrations (see methodology-framework.md for format).github/workflows/ci.yml — CI pipelineCLAUDE.md — project instructionssemver-check.sh — only when Dimension 9 is activated at level 3Present complete plan and wait for approval. Ask about optional items (auto-commit, architecture tests).
Read each template in templates/ for the structural pattern, substitute the researched tools. Restore NuGet packages and verify build.
Read references/reviewer-prompt.md for the full prompt template. Spawn reviewer subagent using Task tool with subagent_type: "general-purpose".
Run .claude/hooks/quality-gate.sh. Distinguish pre-existing issues from config problems.
Structured summary: configured dimensions, files created/modified, quality gate results, next steps.
Solution file not found: Check for .sln files. If none, look for .csproj files directly. Ask the user.
Build restore fails: Check for custom NuGet feeds in nuget.config. Ensure authentication is configured for private feeds.
npx claudepluginhub ondrasek/cc-plugins --plugin blueprintAdds Roslynator and Meziantou analyzers, creates a comprehensive .editorconfig with 80+ diagnostic rules for enforcing strict .NET/C# coding standards.
Guides .NET developers through project initialization with customized CLAUDE.md generation, codebase health analysis using MCP tools, and .NET version migration.
Adding CI/CD to a .NET project. GitHub Actions vs Azure DevOps detection, workflow templates.