dotnet-claude-kit is an opinionated Claude Code plugin that transforms the AI assistant into an expert .NET 10 developer. It provides 47 skills (knowledge + workflow orchestrators), 10 specialist agents (e.g., dotnet-architect, ef-core-specialist), 10 always-loaded rules, 5 project templates, automation hooks, and a Roslyn-based MCP server (CWM.RoslynNavigator) offering 22 read-only code analysis tools. The MCP server delivers token-efficient semantic queries (symbol resolution, anti-pattern detection, dead code analysis, dependency graphs) via stdio, replacing expensive file reads. The architecture is modular: skills are markdown files loaded on demand, agents route requests to specialists, and the MCP server provides a robust program analysis backend. The system supports multiple AI coding tools (Claude Code, Cursor, Codex CLI, OpenCode) with cross-tool rule parity validation. Its core philosophy emphasizes guided over prescriptive development, modern .NET only (.NET 10/C# 14), and token-conscious interactions. The codebase demonstrates strong engineering with clean abstractions, extensive unit tests (200+ tests), CI/CD for NuGet publishing, and well-documented ADRs. The MCP server components (WorkspaceManager, SymbolResolver, anti-pattern detectors, pagination) are highly reusable and exhibit non-obvious craftsmanship. While the large skill surface requires synchronization, the overall quality is excellent for a developer tooling project.
A Visual Studio extension (VSIX) that integrates SonarQube/SonarCloud static analysis into the IDE. It provides real-time code quality and security analysis for C#, VB.NET, C/C++, JavaScript/TypeScript, CSS, and other languages via an embedded SLCore backend (Java process) and a separate Roslyn analyzer server for .NET. The extension supports both standalone analysis and 'connected mode' that binds to SonarQube/SonarCloud servers, including project binding, credential management, issue visualization with flows and locations, security hotspots, taint vulnerabilities, dependency risks, quick fixes, rule education (HTML-to-XAML rendering), and telemetry. The architecture is modular, heavily relying on MEF for dependency injection, with distinct assemblies for core abstractions, VS integration, connected mode UI, issue visualization, security-specific features, and education. The codebase is well-tested with extensive unit tests and some integration tests, but shows signs of ongoing migration from legacy binding models to a modern SLCore-based protocol, resulting in some technical debt and backward-compatibility code.