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

RoslynMcpServer / rules

Cursor rule8 starsChanged 45 days agoMITView on GitHub

Path resolution, search_code defaults, workspace-relative paths

The file

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

4 rules. About 0 are common, 0 are distinctive, and 4 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.

  • 4

    Very specific

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

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

    No workspace → fallback Path.GetFullPath (CWD)

    line 14
  2. Very specific:

    Default root: GetLoadedWorkspaceDirectory() when directoryPath omitted — never rely on CWD alone (hangs scanning user profile).

    line 20
  3. Very specific:

    Default extensions: .cs only.

    line 21
  4. Very specific:

    Do not set CurrentDirectory to AppContext.BaseDirectory (publish output) — breaks search/scratchpad.

    line 27

≈ “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-paths.mdc
---
description: Path resolution, search_code defaults, workspace-relative paths
alwaysApply: true
---

# Path resolution & search

## Relative `filePath`

`Path.GetFullPath` alone resolves against **process CWD** (often the user profile under Cursor). Always use `SolutionManager.ResolvePathAgainstWorkspace`:

- Absolute → normalize and return
- Relative → combine with directory of loaded `.sln`/`.csproj` (`_loadedPath`)
- No workspace → fallback `Path.GetFullPath` (CWD)

Wire **all** filePath-based tools through this helper. Tests: `SolutionManagerPathResolutionTests`.

## `search_code`

- Default root: `GetLoadedWorkspaceDirectory()` when `directoryPath` omitted — **never** rely on CWD alone (hangs scanning user profile).
- Default extensions: `.cs` only; override via `includeExtensions` (e.g. `.cs,.csproj,.json` or `*` for all).
- Support `maxScanSeconds` + progress logging to avoid unbounded scans.

## Env

- `ROSLYN_MCP_WORKSPACE` — repo root (folder with `global.json`); sets process cwd at startup for tools that still use CWD.
- Do **not** set `CurrentDirectory` to `AppContext.BaseDirectory` (publish output) — breaks search/scratchpad.

## Agent-facing docs

Relative paths in MCP calls are OK after `load_workspace`. Prefer absolute when unsure. Never hardcode machine-specific paths in `AGENTS.md` / README samples.

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