Implements the parameter alias pattern for Blazor components where multiple parameter names map to the same behavior. Covers independent auto-property declaration, invocation-site coalescing, and HasDelegate guard updates. Use when a Blazor component needs backward-compatible parameter names, supporting On-prefixed event aliases, or ensuring Web Forms markup migration works without breaking existing consumers.
95
92%
Does it follow best practices?
Impact
100%
1.36xAverage score across 3 eval scenarios
Passed
No known issues
Independent alias parameter declaration
Original property preserved
100%
100%
Alias is auto-property
0%
100%
No getter/setter delegation
0%
100%
Alias has [Parameter] attribute
100%
100%
Matching EventCallback type
100%
100%
XML doc comment present
100%
100%
Doc comment references original
100%
100%
No rename of original
100%
100%
Both declarations present
100%
100%
Alias placed near original
100%
100%
No third property added
100%
100%
Invocation site coalescing
HasDelegate check present
0%
100%
Original checked first
0%
100%
Fallback to alias
0%
100%
Single InvokeAsync call
0%
100%
No dual invocation
100%
100%
Intermediate variable used
0%
100%
Correct args passed
100%
100%
Coalesce covers all call sites
100%
100%
Both params retained
100%
100%
No backing field bridge
100%
100%
Ternary or equivalent used
0%
100%
HasDelegate guard updates
Guard checks both properties
100%
100%
Logical OR used
100%
100%
Original property in guard
100%
100%
Alias property in guard
100%
100%
No guard removed
100%
100%
Invocation site also coalesced
100%
100%
Single InvokeAsync call
100%
100%
Both params retained
100%
100%
No getter/setter delegation in alias
100%
100%
Guard used in markup or render logic
100%
100%
1bd9b17
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.