validate-blazor-feature
Installation
SKILL.md
Validate a Blazor feature with the Components samples
Workflow: pick a sample, add a scenario page, set the render mode, build, launch, drive it in a browser, and check for errors. Validate behavior before writing E2E tests; remove the sample code afterward (git checkout/git clean) once the E2E test covers it.
1. Pick the sample and where the page goes
Samples live in src/Components/Samples (Blazor Web Apps) and src/Components/WebAssembly/Samples (standalone). Each is a full checkout against the in-tree framework.
| Sample | Use it to test | Add your page in |
|---|---|---|
BlazorWebAppPerPage (+ .Client) |
Most features: mix static SSR with per-page interactivity; switch one page's mode independently | .Client/Pages/ for WebAssembly/Auto-capable pages; host Components/Pages/ for Server-only or static SSR pages |
BlazorWebAppGlobal (+ .Client) |
Root/global interactivity concerns (whole app one mode) | .Client/Pages/ (all routable pages live there) |
| BlazorWebAssemblyStandalone | Pure client WebAssembly behavior, no server host | Pages/ |
A WebAssembly or Auto component must live in the .Client project so it compiles into the client assembly. A page placed in the server host can only run Server or static SSR. Routable pages need @page "/your-route".
2. Set the render mode
The two Web App samples express interactivity differently: