rider-mcp-first

Perform .NET symbol searches and refactorings through Rider semantic operations.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/MudraMartin/dotlight-skillset --skill rider-mcp-first
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rider-mcp-first
Source: https://github.com/MudraMartin/dotlight-skillset/tree/main/dotnet/rider-mcp-first
Command: npx skills add https://github.com/MudraMartin/dotlight-skillset --skill rider-mcp-first

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that .NET development operations are performed using Rider's semantic operations, saving context tokens and improving efficiency.

Core Features & Use Cases

  • Token Efficiency: Minimizes context token usage by encouraging the use of Rider's semantic operations over filesystem tools.
  • Rider Integration: Integrates with Rider IDE for precise code analysis and operations.
  • Use Case: When working on a .NET solution, this Skill prompts the user to use Rider's semantic operations for tasks like searching for symbols, finding references, and renaming refactoring, which are more efficient than filesystem tools.

Quick Start

Use the rider-mcp-first skill to perform a search for a symbol in your .NET solution.

Frequently Asked Questions about rider-mcp-first

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I improve .NET token efficiency when searching for symbols in Rider?

You can improve .NET token efficiency by using Rider's semantic operations for symbol searches instead of filesystem tools. This approach minimizes context token usage during development by leveraging precise code analysis directly through the Rider IDE integration.

What is the best way to find references in a .NET solution without wasting context tokens?

The best way to find references without wasting tokens is to use Rider semantic operations. By prompting the use of Rider's precise code analysis over filesystem tools, this approach saves context tokens and improves workflow efficiency during .NET development.

Do I need the Rider MCP plugin to perform semantic operations for .NET refactoring?

Yes, you need the Rider IDE and the MCP plugin installed and configured. This setup enables precise semantic operations like renaming refactoring and finding references, ensuring .NET development tasks are performed efficiently while saving context tokens.

Why use Rider semantic operations instead of filesystem tools for .NET code analysis?

Rider semantic operations provide precise code analysis that filesystem tools cannot match. Using them for tasks like searching symbols or renaming refactoring prevents unnecessary file scanning, saving context tokens and improving overall .NET development efficiency.

Can I use Rider semantic operations for renaming refactoring across a .NET solution?

Yes, Rider semantic operations support renaming refactoring across a .NET solution. By using these precise code analysis operations instead of filesystem tools, you ensure accurate modifications while actively saving context tokens and improving development efficiency.