/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
$ npx -y skills add managedcode/dotnet-skills --skill managedcode-orleans-signalr --agent claude-codeHow 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.mdname: 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
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
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.
Repo: managedcode/dotnet-skills
Other skills on dotnet-skills.
- /aspnet-core
Build, debug, modernize, or review ASP.NET Core applications with correct hosting, middleware, security, configuration, logging, and deployment patterns on current .NET. USE FOR: working on ASP.NET Core apps, services, or middleware; changing auth, routing, configuration,
Open skill - /aspire
Build, upgrade, and operate Aspire 13.4.x C# or TypeScript application hosts with the current CLI, AppHost, ServiceDefaults, integrations, dashboard, testing, MCP, and deployment patterns for distributed apps. USE FOR: Aspire.AppHost.Sdk, Aspire.Hosting.*,
Open skill - /azure-functions
Build, review, or migrate Azure Functions in .NET with correct execution model, isolated worker setup, bindings, DI, and Durable Functions patterns. USE FOR: working on Azure Functions in .NET; migrating from the in-process model to the isolated worker model; adding Durable
Open skill - /blazor
Build and review Blazor applications across server, WebAssembly, web app, and hybrid scenarios with correct component design, state flow, rendering, and hosting choices. USE FOR: building interactive web UIs with C# instead of JavaScript; choosing between Server, WebAssembly, or
Open skill - /entity-framework6
Maintain or migrate EF6-based applications with realistic guidance on what to keep, what to modernize, and when EF Core is or is not the right next step. USE FOR: EF6 codebases; runtime versus ORM migration decisions; EDMX, code-first, ObjectContext, and legacy data-access
Open skill - /entity-framework-core
Design, tune, or review EF Core data access with proper modeling, migrations, query translation, performance, and lifetime management for modern .NET applications. USE FOR: DbContext, migrations, model configuration, EF queries, tracking, loading, performance, transactions, and
Open skill

