Claude Skill

dotnet-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.

LLM Mart · 0 points · 0 0 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download postpartum-genushyacinthus29-dotnet-skills-skills_dotnet-managedcode-orleans-signalr-bfa4ebd.zip · 0 KB

postpartum-genushyacinthus29/dotnet-skills 12 1 forks MIT Updated 16h ago

Part of postpartum-genushyacinthus29/dotnet-skills — 80 skills

Install

skills CLI

npx skills add https://github.com/Postpartum-genushyacinthus29/dotnet-skills/tree/main/skills/dotnet-managedcode-orleans-signalr

Claude Code

claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install postpartum-genushyacinthus29-dotnet-skills@llmmart

Git git clone https://github.com/Postpartum-genushyacinthus29/dotnet-skills.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole postpartum-genushyacinthus29/dotnet-skills collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

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

Confirm the application genuinely needs both Orleans and SignalR in the same flow.
Identify which grain events or workflows should publish to connected clients.
Keep Orleans domain logic in grains and SignalR transport concerns in the integration boundary.
Document how user, group, or connection targeting is resolved.
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

Files (dotnet-skills)

SKILL.md 1.7 KB

---
name: dotnet-managedcode-orleans-signalr
version: "1.0.0"
category: "Distributed"
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."
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.

```mermaid
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