Stats
Actions
Tags
From blueprint
Answers questions about the .NET quality methodology — why tools are chosen, how thresholds work, what each dimension covers, and how hooks interact. Use when user asks "why this tool", "what does the quality gate do", "how are thresholds set", or any .NET methodology question.
How this skill is triggered — by the user, by Claude, or both
Slash command
/blueprint:dotnet-explainThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Read-only — does not modify any files.
Read-only — does not modify any files.
skills/shared/references/explain-pattern.md — shared answer format and behaviorskills/shared/references/methodology-framework.md — shared principles, hook architectureskills/dotnet-setup/references/methodology.md — .NET-specific dimensions, rationale, adaptation rulesskills/dotnet-setup/references/analysis-checklist.md — how projects are analyzed"Why Roslyn analyzers over external tools?" → Dimension 2. Roslyn analyzers run during dotnet build, integrate with IDEs, controlled via .editorconfig. No separate step needed.
"What's the coverage threshold?" → Dimension 1. 90% default; 70% for new projects; legacy: start at current.
"Should I use all 9 dimensions?" → Principles: incremental adoption. Start with testing + linting, add incrementally.
"Why Directory.Build.props?" → .NET-Specific Patterns. Centralizes MSBuild properties, avoids duplication across .csproj files.
"How does nullable reference types fit?" → Dimension 3. <Nullable>enable</Nullable> + AnalysisLevel: latest-Recommended.
"How do I disable a check?" → Each check has a [check:*] comment marker. Delete the run_check block.
npx claudepluginhub ondrasek/cc-plugins --plugin blueprintAssesses .NET project health across 8 dimensions (build, code quality, architecture, test coverage, dead code, API surface, security, documentation) with letter grades A-F and actionable recommendations using Roslyn MCP tools.
Adds Roslynator and Meziantou analyzers, creates a comprehensive .editorconfig with 80+ diagnostic rules for enforcing strict .NET/C# coding standards.
Patterns for detecting and managing code smells and technical debt in .NET applications. Run Slopwatch CLI to detect LLM reward hacking, disabled tests, suppressed warnings, empty catches, and other shortcuts. Use when identifying code smells, running quality gates in CI/CD, or validating LLM-generated code changes.