What problem does it solve? Building forms in Blazor is confusing because the correct pattern depends on the app's interactivity mode — Static SSR requires FormName and SupplyParameterFromForm, while interactive modes use @bind-Value, and mixing them up causes silent failures like null models, double submissions, or ignored validation. ## Core Features & Use Cases - Mode-Aware Form Patterns: Provides the correct EditForm setup for Static SSR, Server, WebAssembly, and Auto render modes, including FormName, SupplyParameterFromForm, and antiforgery handling. - Validation Guidance: Covers DataAnnotationsValidator, per-field ValidationMessage, custom validator components for server-side business rules, and custom CSS class providers for styling validation states. - Interactive Input Handling: Shows @bind:after reactions, real-time search filtering with @oninput, file uploads via InputFile, and double-submission prevention. - Use Case: You need to add a registration form with email uniqueness validation to a Blazor page using per-page interactivity — this Skill gives you the exact EditForm, validator component, and SSR fallback pattern that works. ## Quick Start Ask the AI to add a validated contact form with name, email, and a file upload to your Blazor page, respecting the interactivity mode defined in AGENTS.md.
