Author Blazor Component
Core Rules
- Data flows down via
[Parameter]. Events flow up via EventCallback<T> (never Action/Func).
- Never mutate
[Parameter] properties. Copy to a private field in OnParametersSet.
- Use
[Parameter] public T Prop { get; set; } — never required or init (causes BL0007).
- Use
[EditorRequired] for required parameters.
- Handle all states: loading, empty, loaded, error — each with
@if/@else.
- Use
@key on repeated elements in loops for efficient diffing.
- Use
IReadOnlyList<T> (not IEnumerable<T>) for collection parameters.
RenderFragment & Generics
[Parameter] public RenderFragment? ChildContent { get; set; }
[Parameter] public RenderFragment<TItem>? RowTemplate { get; set; } // generic template
Use @typeparam TItem for generic components.
File Patterns
- Single-file:
.razor with @code block when logic < ~50 lines.
- Code-behind:
.razor + .razor.cs with partial class when logic > ~50 lines.
Disposal
Implement IAsyncDisposable (not IDisposable) when the component owns subscriptions, timers, or CTS.
In DisposeAsync: unsubscribe (-=), cancel CTS, dispose resources. Never call StateHasChanged.
Async Patterns
await every async operation. Never use .Result, .Wait(), Task.Run, ContinueWith, Thread.Start.
- Debounce:
Task.Delay + CancellationTokenSource. Cancel old CTS, create new, await delay, do work. Never use System.Threading.Timer or System.Timers.Timer.
- Polling: Loop in
OnInitializedAsync with await Task.Delay(interval, token) — stays on sync context.
- External events (
Action<T>): Use async void handler + await InvokeAsync(() => { state++; StateHasChanged(); }) + catch → DispatchExceptionAsync. Never _ = InvokeAsync(...).
- Cancel CTS in
DisposeAsync. Don't catch ObjectDisposedException — use CTS cancellation.
Don'ts
required/init on [Parameter] — runtime failure
- Mutate
[Parameter] — copy to private field in OnParametersSet
Action/Func for events — use EventCallback<T>
Task.Run/.Result/.Wait()/Timer for debounce — deadlock or thread-pool escape
- Inline
style attributes — use CSS classes or data-* attributes
catch { throw; } — use when guard or let exceptions propagate
- Gold-plating: ARIA, wrapper divs, accessibility features not requested
_ = InvokeAsync(...) — swallows exceptions; use async void + DispatchExceptionAsync
1---2license: MIT3name: author-component4description: >5 Create or review Blazor components (.razor files) with correct architecture.6 USE FOR: writing new Blazor components that do NOT involve JavaScript interop,7 implementing parameters and EventCallback, RenderFragment slots, component8 lifecycle (OnInitializedAsync, OnParametersSet), async patterns, IAsyncDisposable,9 CancellationToken, CSS isolation, code-behind.10 DO NOT USE FOR: creating new projects (use create-blazor-project), JavaScript11 interop or calling browser APIs from Blazor (use use-js-interop), forms and12 validation (use collect-user-input), prerendering issues (use support-prerendering),13 HTTP data fetching patterns (use fetch-and-send-data), coordinating state between14 unrelated components (use coordinate-components).15metadata:16 source: https://skillmd.com/skills/dotnet/author-component17---1819# Author Blazor Component2021## Core Rules2223- Data flows **down** via `[Parameter]`. Events flow **up** via `EventCallback<T>` (never `Action`/`Func`).24- Never mutate `[Parameter]` properties. Copy to a private field in `OnParametersSet`.25- Use `[Parameter] public T Prop { get; set; }` — never `required` or `init` (causes BL0007).26- Use `[EditorRequired]` for required parameters.27- Handle all states: loading, empty, loaded, error — each with `@if`/`@else`.28- Use `@key` on repeated elements in loops for efficient diffing.29- Use `IReadOnlyList<T>` (not `IEnumerable<T>`) for collection parameters.3031## RenderFragment & Generics3233```csharp34[Parameter] public RenderFragment? ChildContent { get; set; }35[Parameter] public RenderFragment<TItem>? RowTemplate { get; set; } // generic template36```3738Use `@typeparam TItem` for generic components.3940## File Patterns4142- **Single-file:** `.razor` with `@code` block when logic < ~50 lines.43- **Code-behind:** `.razor` + `.razor.cs` with `partial class` when logic > ~50 lines.4445## Disposal4647Implement `IAsyncDisposable` (not `IDisposable`) when the component owns subscriptions, timers, or CTS.48In `DisposeAsync`: unsubscribe (`-=`), cancel CTS, dispose resources. Never call `StateHasChanged`.4950## Async Patterns5152- `await` every async operation. Never use `.Result`, `.Wait()`, `Task.Run`, `ContinueWith`, `Thread.Start`.53- **Debounce:** `Task.Delay` + `CancellationTokenSource`. Cancel old CTS, create new, await delay, do work. Never use `System.Threading.Timer` or `System.Timers.Timer`.54- **Polling:** Loop in `OnInitializedAsync` with `await Task.Delay(interval, token)` — stays on sync context.55- **External events** (`Action<T>`): Use `async void` handler + `await InvokeAsync(() => { state++; StateHasChanged(); })` + `catch` → `DispatchExceptionAsync`. Never `_ = InvokeAsync(...)`.56- Cancel CTS in `DisposeAsync`. Don't catch `ObjectDisposedException` — use CTS cancellation.5758## Don'ts5960- `required`/`init` on `[Parameter]` — runtime failure61- Mutate `[Parameter]` — copy to private field in `OnParametersSet`62- `Action`/`Func` for events — use `EventCallback<T>`63- `Task.Run`/`.Result`/`.Wait()`/Timer for debounce — deadlock or thread-pool escape64- Inline `style` attributes — use CSS classes or `data-*` attributes65- `catch { throw; }` — use `when` guard or let exceptions propagate66- Gold-plating: ARIA, wrapper divs, accessibility features not requested67- `_ = InvokeAsync(...)` — swallows exceptions; use `async void` + `DispatchExceptionAsync`