agentleFS
Postpartum-genushyacinthus29Postpartum-genushyacinthus29/dotnet-skills/skills/dotnet-managedcode-orleans-signalr/SKILL.md

dotnet-managedcode-orleans-signalr

Skill13 starsChanged 8 months agoMITView on GitHub

Use ManagedCode.Orleans.SignalR when a distributed .NET application needs Orleans-based coordination of SignalR real-time messaging, hub delivery, and grain-driven push flows.

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 Orleans domain logic in grains and SignalR transport concerns in the integration boundary.

    line 22
  2. Distinctive:

    Document how user, group, or connection targeting is resolved.

    line 23

≈ “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.Orleans.SignalR

Trigger On

  • integrating ManagedCode.Orleans.SignalR into a real-time distributed application
  • coordinating SignalR delivery from Orleans grains
  • reviewing grain-to-hub push flows and connection routing
  • documenting how Orleans state or events become SignalR messages

Workflow

  1. Confirm the application genuinely needs both Orleans and SignalR in the same flow.
  2. Identify which grain events or workflows should publish to connected clients.
  3. Keep Orleans domain logic in grains and SignalR transport concerns in the integration boundary.
  4. Document how user, group, or connection targeting is resolved.
  5. Validate end-to-end message delivery from grain event to connected client.
flowchart LR
  A["Orleans grain event"] --> B["ManagedCode.Orleans.SignalR integration"]
  B --> C["SignalR hub delivery"]
  C --> D["Connected client or group"]

Deliver

  • guidance on where the Orleans-to-SignalR bridge belongs
  • separation between grain logic and transport concerns
  • validation expectations for real-time distributed delivery

Validate

  • the integration is justified instead of mixing Orleans and SignalR casually
  • grain logic stays focused on domain or orchestration concerns
  • real-time delivery is verified end to end, not only through registration code

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.