What problem does it solve? Adding authentication to a Blazor Web App is error-prone because behavior differs across static SSR, interactive Server, and WebAssembly render modes, causing null auth state, SignInManager exceptions, and broken Identity pages. ## Core Features & Use Cases - Render-mode-aware setup: Registers cascading authentication state, Identity services, and wires App.razor with AuthorizeRouteView and AcceptsInteractiveRouting. - Page and component protection: Applies [Authorize] attributes, role and policy checks, AuthorizeView conditional UI, and cascading AuthenticationState access. - WebAssembly auth serialization: Configures AddAuthenticationStateSerialization and Deserialization so auth state survives the prerender-to-WASM transition. - Use Case: A developer adds login to a globally interactive Blazor app and finds Identity pages crash; this Skill marks them with [ExcludeFromInteractiveRouting] so they render as static SSR with a real HttpContext. ## Quick Start Add authentication with ASP.NET Core Identity to my Blazor Web App and protect the admin pages with role-based authorization.
