[New Plugin] dotnet-signalr — skills for ASP.NET Core SignalR

[puneet45678]

Proposed Plugin: dotnet-signalr

SignalR is a widely used ASP.NET Core library but there are no
skills covering it in this repo yet.

Proposed Skills

• signalr-hub-setup — setting up a SignalR hub with ASP.NET Core,
  DI registration, mapping, and common configuration
• signalr-redis-backplane — scaling SignalR across multiple server
  instances using Redis
• signalr-rate-limiting — applying rate limiting to SignalR hub
  endpoints using ASP.NET built-in rate limiter
• signalr-connection-management — managing connection lifecycle,
  OnConnectedAsync, OnDisconnectedAsync, room/group patterns

Why

These are non-obvious areas where developers frequently run into
issues that a well-written skill would prevent.

Happy to start with one skill and iterate from there.

[AbhitejJohn]

Thanks for sharing!
Tagging @danroth27 . We have been looking at adding a plugin for aspnet and blazor.

[BrennanConroy]

We'd want to first see what LLMs struggle with in this area. I'd be a bit surprised if LLMs couldn't handle common SignalR scenarios.

These are non-obvious areas where developers frequently run into
issues that a well-written skill would prevent.

What are these issues? And did you use an LLM to try to solve them? Did it fail which is why a skill might be needed?

[puneet45678]

@BrennanConroy
Thanks for the feedback fair point, let me be more specific.

I recently worked on a project using ASP.NET Core SignalR as a signaling server for WebRTC. During that I ran into a few issues that LLMs didn't handle well out of the box:

1. ICE candidate race condition
   When relaying WebRTC ICE candidates through a SignalR hub, candidates from Peer A would arrive at Peer B before setRemoteDescription was called, causing them to be silently dropped and the WebRTC connection to fail. The fix is queuing candidates and flushing them after remote description is set ,but LLMs would generate the basic relay code without mentioning this timing issue at all.

2. Rate limiting SignalR hub endpoints
   LLMs often generate incorrect or outdated code for applying AddRateLimiter to SignalR hubs — missing the correct using directive (Microsoft.AspNetCore.RateLimiting) or using the old package-based approach.

3. Connection lifecycle and room management
   Patterns like using ConcurrentDictionary for room state with proper OnDisconnectedAsync cleanup are non-obvious. LLMs tend to suggest locking or non-thread-safe approaches.

Happy to start with just one of these as a focused skill to show the value.