agentleFS
Sign inStart free
VuDZVuDZ/RoslynMcpServer/.cursor/rules/roslyn-mcp-dev-conventions.mdc

RoslynMcpServer / rules

Cursor rule8 starsChanged 45 days agoMITView on GitHub

Conventions when editing Tools and Services in this repo

The file

We split this roslyn-mcp-dev-conventions.mdc into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Prefer structured return strings (markdown sections, ### metadata) matching existing tools.

    line 12
  2. Very specific:

    Add/adjust unit tests under RoslynMcpServer.Tests for parsers, resolvers, path helpers.

    line 15

≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
roslyn-mcp-dev-conventions.mdc
---
description: Conventions when editing Tools and Services in this repo
globs: Tools/**/*.cs,Services/**/*.cs,Hosting/**/*.cs
alwaysApply: false
---

# Tools & Services changes

- Register new tools in `McpToolCatalog` (names, host, group, lite-core, read/write). That catalog drives DI host registration and method-level MCP SDK registration. Do **not** add a parallel `WithTools<T>()` list.
- Constructor-inject `SolutionManager` / helpers; tools are singletons.
- Resolve all relative file paths via `ResolvePathAgainstWorkspace`.
- Prefer structured return strings (markdown sections, `###` metadata) matching existing tools.
- Log outcomes as summary + warning highlights; gate full dumps behind `ROSLYN_MCP_LOG_TOOL_OUTPUT=full`.
- Friendly errors for bad/missing args — avoid unhandled exceptions leaking as opaque MCP failures.
- Add/adjust unit tests under `RoslynMcpServer.Tests` for parsers, resolvers, path helpers.
- Version: follow always-apply rule `roslyn-mcp-version-bump.mdc` — patch-bump after successful self-build when shipping code/tool changes; sync README + `AGENTS.md.sample`.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free