domains / families / software-engineering / author-component

author-component

separate

Create or review Blazor components (.razor files) with correct architecture. USE FOR: writing new Blazor components that do NOT involve JavaScript interop, implementing parameters and EventCallback, RenderFragment slots, component lifecycle (OnInitializedAsync, OnParametersSet), async patterns, IAsyncDisposable, CancellationToken, CSS isolation, code-behind. DO NOT USE FOR: creating new projects (use create-blazor-project), JavaScript interop or calling browser APIs from Blazor (use use-js-interop), forms and validation (use collect-user-input), prerendering issues (use support-prerendering), HTTP data fetching patterns (use fetch-and-send-data), coordinating state between unrelated components (use coordinate-components).

When to use

• writing new Blazor components
• implementing parameters and EventCallback
• RenderFragment slots
• component lifecycle
• async patterns
• IAsyncDisposable
• CancellationToken
• CSS isolation

When not to use

• creating new projects
• JavaScript interop
• calling browser APIs from Blazor
• forms and validation
• prerendering issues
• HTTP data fetching patterns
• coordinating state between unrelated components

Skill page

Source