What problem does it solve? Building real-time features like chat, notifications, and live updates in ASP.NET Core requires correct handling of hub lifetimes, reconnection, group membership, authentication, and multi-server scale-out, which are easy to get wrong. ## Core Features & Use Cases - Hub Implementation Patterns: Strongly-typed hubs, thin hub methods with service delegation, custom request objects for backward-compatible API evolution, and group-based targeted messaging. - Connection & Client Guidance: Automatic reconnection with retry delays, group rejoining after reconnect, JWT authentication over WebSockets, and lifecycle event handling for both JavaScript and .NET clients. - Scale-Out & Anti-Patterns: Redis backplane and Azure SignalR Service configuration, plus a detailed catalog of mistakes such as storing state in hub properties, unawaited sends, and missing input validation. - Use Case: When adding a live notification feed to an ASP.NET Core app deployed across multiple servers, use this Skill to design the hub contract, configure JWT auth and a Redis backplane, and verify reconnection behavior. ## Quick Start Ask the assistant to implement a strongly-typed SignalR chat hub with automatic reconnection and Redis backplane scaling in your ASP.NET Core project.