What problem does it solve? Interactive Blazor components prerender on the server by default, causing OnInitializedAsync to run twice, data to be fetched twice, UI flicker during the prerender-to-interactive handoff, and null references when browser APIs are unavailable. This Skill provides the patterns to diagnose and fix these prerendering problems. ## Core Features & Use Cases - State Persistence: Persist component state across the prerender-to-interactive transition using the [PersistentState] attribute or the PersistentComponentState service, eliminating duplicate API and database calls. - Prerendering Control: Disable prerendering per component, per instance, or app-wide, and exclude pages from interactive routing when they need HttpContext access. - Runtime Detection: Use RendererInfo to detect whether a component is currently prerendering and guard interactive-only code such as SignalR connections. - Use Case: A weather forecast page fetches data in OnInitializedAsync and flickers while calling the API twice. Apply [PersistentState] with the ??= pattern so the prerendered data is restored instead of re-fetched. ## Quick Start Ask the AI to fix the duplicate data loading and flicker in your Blazor page by persisting state across prerendering.