managedcode-orleans-signalr
ManagedCode.Orleans.SignalR integrates Orleans grain coordination with SignalR real-time messaging in distributed .NET applications, bridging grain events to client push notifications through hub delivery. Use this skill when establishing Orleans-driven SignalR flows, coordinating message delivery from grains to connected clients, or validating grain-to-hub communication patterns and connection routing logic.
git clone --depth 1 https://github.com/managedcode/dotnet-skills /tmp/managedcode-orleans-signalr && cp -r /tmp/managedcode-orleans-signalr/catalog/Libraries/ManagedCode-Orleans-SignalR/skills/managedcode-orleans-signalr ~/.claude/skills/managedcode-orleans-signalrSKILL.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. ```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
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, hosting, or deployment behavior; deciding between ASP.NET Core sub-stacks. 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.
Build, upgrade, and operate .NET Aspire 13.3.x application hosts with current CLI, AppHost, ServiceDefaults, integrations, dashboard, testing, and Azure deployment patterns for distributed apps. USE FOR: Aspire.AppHost.Sdk, Aspire.Hosting.*, DistributedApplication.CreateBuilder, WithReference, WaitFor, AddProject, AddRedis, AddPostgres, aspire run, aspire init, aspire. 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.
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 Functions, bindings, or host configuration. 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.
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 Auto render modes; designing component hierarchies and state. 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.
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 review. 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.
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 EF6 migration decisions. 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.
Build, review, or migrate .NET MAUI applications across Android, iOS, macOS, and Windows with correct cross-platform UI, platform integration, and native packaging assumptions. USE FOR: working on cross-platform mobile or desktop UI in .NET MAUI; integrating device capabilities, navigation, or platform-specific code; migrating Xamarin.Forms or aligning. 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.
Use ML.NET to train, evaluate, or integrate machine-learning models into .NET applications with realistic data preparation, inference, and deployment expectations. USE FOR: ML.NET integration; local model training or retraining; inference pipelines, model loading, evaluation, and deployment review. 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.