Implement or review SignalR hubs, streaming, reconnection, transport, and real-time delivery patterns in ASP.NET Core applications. USE FOR: building chat, notification, collaboration, or live-update features; debugging hub lifetime, connection state, or transport issues; deciding whether SignalR or another. 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
SkillScore100Maintained
Automatic
◆Coding pack
Last verified 8/19/2026
What it changes
Passed 22 of 22 test cases with the skill, and 21 of 22 without it.
Without skill95%
With skill100%
Checks it passed that the model alone missed
Recommends passing a single custom request DTO object instead of individual primitive arguments.
1 fixed21 passed either way0 still failing0 broke
Pass-rate lift
+5 pp
Tokens
+199%
Agent turns
0%
Response time
-10%
Model gemini-3.6-flashMeasured 8/19/2026v222 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
What's inside
The instructions your model reads when the skill loads.
SKILL.md337 lines3 files
SignalR
Trigger On
building chat, notification, collaboration, or live-update features
debugging hub lifetime, connection state, or transport issues
deciding whether SignalR or another transport better fits the scenario
implementing real-time broadcasting to groups of connected clients
anti-patterns.md - Common SignalR mistakes and how to avoid them
Workflow
Use SignalR for broadcast-style or connection-oriented real-time features; do not force gRPC into hub-style fan-out scenarios.
Model hub contracts intentionally and keep hub methods thin, delegating durable work elsewhere.
Plan for reconnection, backpressure, auth, and fan-out costs instead of treating real-time messaging as stateless request/response.
Use groups, presence, and connection metadata deliberately so scale-out behavior is understandable.
If Native AOT or trimming is in play, validate supported protocols and serialization choices explicitly.
Test connection behavior and failure modes, not just happy-path message delivery.
Current Upstream Notes
dotnet/aspnetcorev10.0.11 is a servicing release and does not change the SignalR programming model. Keep guidance focused on hub contract design, reconnection, transport, authorization, and scale-out validation.
The August 2026 ASP.NET Core overview still positions SignalR for real-time server/client communication. After servicing updates, rerun at least one reconnect and group-broadcast smoke path because dependency updates can expose client/server package mismatches.
Use the open-source free `StyleCop.Analyzers` package for naming, layout, documentation, and style rules in .NET projects. Use when a repo wants stricter style conventions than the SDK analyzers alone provide. USE FOR: the repo wants StyleCop.Analyzers; naming, layout, or documentation style needs stronger enforcement; the team needs stylecop.json guidance. DO NOT USE FOR: repos that intentionally rely only on SDK analyzers; repos where StyleCop overlaps too heavily with an existing style packag