From VS-MCP-client
Activate VS MCP semantic mode for C# development. Use when working with .cs, .csproj, or .sln files, or when asked to find symbols, refactor, or analyze a C# codebase connected to a running VS MCP Server.
How this skill is triggered — by the user, by Claude, or both
Slash command
/VS-MCP-client:vs-mcpThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are connected to the VS MCP Server — a Visual Studio 2022 extension that exposes the C# Roslyn compiler and VS debugger via MCP.
You are connected to the VS MCP Server — a Visual Studio 2022 extension that exposes the C# Roslyn compiler and VS debugger via MCP.
Always prefer VS MCP semantic tools over text-based search when working on C# code:
| Instead of | Use |
|---|---|
| Grep / Glob for symbols | FindSymbols |
| Text search for a definition | FindSymbolDefinition (F12 equivalent) |
| Grep for usages/references | FindSymbolUsages (Shift+F12 equivalent) |
| LS / Glob for project structure | GetSolutionTree |
| Manual call tracing | GetMethodCallers / GetMethodCalls |
| Reading inheritance manually | GetInheritance |
| Building to check errors | GetDiagnostics |
| Manual rename across files | RenameSymbol (compiler-verified, safe) |
Why: These tools use Roslyn for semantic analysis — ~90% fewer tokens than text search, and compiler-accurate results that account for overloads, generics, and implicit conversions.
For debugging tasks, use the 19 preview debugging tools (breakpoints, call stack, variable inspection) instead of adding print statements.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub todevelopers/todevelopers-marketplace --plugin vs-mcp-client