Skip to content
Development
Skill

/managedcode-orleans-signalr

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. USE FOR: integrating ManagedCode.Orleans.SignalR into a real-time distributed application; coordinating

From plugin
dotnet-skills
466200 skills50 agents
Install
$ npx -y skills add managedcode/dotnet-skills --skill managedcode-orleans-signalr --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/managedcode-orleans-signalr

Context preview

The summary Claude sees to decide when to auto-load this skill.

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. USE FOR: integrating ManagedCode.Orleans.SignalR into a real-time distributed application; coordinating

SKILL.md

managedcode-orleans-signalr.SKILL.md
name: managedcode-orleans-signalr
description: "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. USE FOR: integrating ManagedCode.Orleans.SignalR into a real-time distributed application; coordinating SignalR delivery from Orleans grains; reviewing grain-to-hub push flows. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made."
compatibility: "Requires a .NET application that combines Orleans and SignalR through ManagedCode.Orleans.SignalR."

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
Read more
Ships withdotnet-skills

Stop explaining .NET to your AI. Start building. We've all been there: asking Claude to use Entity Framework, only to get EF6 patterns in a .NET 8 project. Explaining to Copilot that Blazor Server and Blazor WebAssembly aren't the same thing.

Get the whole plugin

Other skills on dotnet-skills.