agentleFS
Sign inStart free
Postpartum-genushyacinthus29Postpartum-genushyacinthus29/dotnet-skills/skills/dotnet-managedcode-communication/SKILL.md

dotnet-managedcode-communication

Skill13 starsChanged 8 months agoMITView on GitHub

Use ManagedCode.Communication when a .NET application needs explicit result objects, structured errors, and predictable service or API boundaries instead of exception-driven control flow.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep result creation and error mapping explicit instead of mixing exceptions, nulls, and ad-hoc tuples.

    line 24
  2. Distinctive:

    Do not hide domain failures behind generic success wrappers.

    line 26

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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
SKILL.md

ManagedCode.Communication

Trigger On

  • integrating ManagedCode.Communication into services or APIs
  • replacing exception-driven result handling with explicit results
  • reviewing service boundaries that return success or failure payloads
  • documenting result-pattern usage across ASP.NET Core or application services

Workflow

  1. Confirm the boundary where the library belongs:
    • service result contracts
    • application manager boundaries
    • API endpoints that translate results into HTTP responses
  2. Keep result creation and error mapping explicit instead of mixing exceptions, nulls, and ad-hoc tuples.
  3. Pattern-match result objects at the boundary that converts them into user-facing responses.
  4. Do not hide domain failures behind generic success wrappers.
  5. Validate positive, negative, and error-path handling after integration.
flowchart LR
  A["Domain or service operation"] --> B["ManagedCode.Communication result"]
  B --> C["Application or API boundary"]
  C --> D["HTTP response or caller-visible contract"]

Deliver

  • guidance on where explicit result objects improve clarity
  • usage boundaries for translating results into API or caller responses
  • validation expectations for success and failure flows

Validate

  • result handling is consistent across the boundary that uses the library
  • callers do not fall back to exception-only logic for normal failure cases
  • negative and error scenarios are documented and tested

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