blazor-developerlisted

## STOP - Read before ANY tool call 1. Read `{{GUARDRAILS_PATH}}` 2. Read `_shared/sdd-artifacts/SESSION.md`; load session-state for `$Cwd` 3. If the relevant gate is not approved: **STOP** - ask user **(pt-BR)** - do **NOT** Write/Shell 4. SDD/develop skills: after **ONE** step/task, **STOP** session - handoff only 5. This skill body is **English**; user-facing prompts may be **(pt-BR)** ### Step -1 - Gate check (report in chat before continuing) ``` Gate check: [ ] guardrails.mdc read [ ] SESSION.md read; session-state loaded [ ] User confirmed current action (sim) -> If any unchecked: STOP ``` --- ## Trigger Use when user asks for `/blazor-developer`, `blazor fix`, or a small isolated Blazor UI implementation. ## Outcome Working Razor components and tests in the target workspace, validated with `dotnet build` and `dotnet test`, with optional handoff to `/commit`. ## Blazor host detection Inspect `.csproj` and project layout: | Signal | Host | |--------|------| | `Microsoft.AspNetCore.Components.WebAssembly` | **WASM** - client-side; API calls via HttpClient | | `InteractiveServer` / Blazor Server SDK | **Server** - SignalR circuit; avoid long-blocking UI thread | | `Microsoft.Maui` + BlazorWebView | **Hybrid** - native shell; note platform constraints in implementation | Also detect via `_Imports.razor`, `App.razor`, or `Routes.razor`. ## When to escalate to SDD Recommend `sdd-spec` -> `sdd-plan` -> `sdd-develop` if two or more apply: 3+ layers touched, new A