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

RoslynMcpServer / rules

Cursor rule8 starsChanged 45 days agoMITView on GitHub

Assembly resolve, ILSpy decompile, NuGet/BCL fallback

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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 exact {assemblyName}.dll — no fuzzy Contains matching (wrong DLL / BadImage).

    line 13
  2. Distinctive:

    Do not invent NuGet APIs from memory — decompile first.

    line 23
  3. Very specific:

    Do not assume cloud VssConnection.CreateAsync(organization) for on-prem — collection URI + Windows/PAT.

    line 26

≈ “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-decompile.mdc
---
description: Assembly resolve, ILSpy decompile, NuGet/BCL fallback
globs: Services/**/*.{cs},Tools/CodeAnalysisTools.cs,Tools/CodeSkeletonTools.cs
alwaysApply: false
---

# Decompile & assembly resolve

## Exact resolve (v1.0.13+)

`AssemblyReferenceResolver` / `DepsJsonAssemblyPathResolver` / `NuGetFallbackAssemblyResolver`:

- Prefer exact `{assemblyName}.dll` — **no** fuzzy `Contains` matching (wrong DLL / BadImage).
- Resolve via project `deps.json`, then NuGet cache, then BCL / runtime pack maps (`BclAssemblyPackageMap`).
- Tools accept `assemblyName` (after `load_workspace`) **or** `assemblyPath`.

## DecompilerHost

ILSpy-backed; circuit breakers (e.g. `decompile_type` max ~500 lines). Large types → skeleton first.

## API assumptions

Do not invent NuGet APIs from memory — decompile first. Especially **Azure DevOps / TFS**:

- Decompile `Microsoft.VisualStudio.Services.WebApi` (or graph-named assembly).
- Do **not** assume cloud `VssConnection.CreateAsync(organization)` for on-prem — collection URI + Windows/PAT.

## Tests

`AssemblyReferenceResolverTests`, `DepsJsonAssemblyPathResolverTests`, `NuGetFallbackAssemblyResolverTests`.

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