Keep migrated Blazor output compiling when more Web Forms artifacts stay on the generated compile surface
59
74%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./.squad/skills/cli-compile-surface-hardening/SKILL.mdUse this when the migration CLI starts emitting more generated .razor.cs files or copying more legacy source into the output project. The goal is to preserve deterministic L1 behavior while preventing compile failures from style analyzers, generic Razor component inference, or unresolved markup references.
<EnforceCodeStyleInBuild>false</EnforceCodeStyleInBuild> over broad warning suppression when copied legacy files would otherwise fail repo-level IDE analyzers.TValue alias:
RequiredFieldValidator → Type="string"CompareValidator / RangeValidator → InputType="string"metadata.MarkupContent) as the source of truth.@MethodName() → render-method stub returning object?@_fieldName → private object? fieldOnClick="@HandlerName" and similar → void HandlerName(object? sender, EventArgs e)src\BlazorWebFormsComponents.Cli\Program.cs) and tests\BlazorWebFormsComponents.Cli.Tests\TestHelpers.cs so the lightweight and full pipelines stay aligned.src\BlazorWebFormsComponents.Cli\Transforms\Markup\ValidatorGenericTypeTransform.cssrc\BlazorWebFormsComponents.Cli\Transforms\CodeBehind\MarkupReferencedMemberStubTransform.cstests\BlazorWebFormsComponents.Cli.Tests\TransformUnit\CompiledCodeBehindStubPipelineTests.csTValue="string" into BWFC validators that actually expose Type or InputType generic parameters.@Identifier token; restrict deterministic generation to the specific reference shapes you can classify safely.FritzAndFriends/BlazorWebFormsComponents
3154758
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.