Install any skill in seconds. Free to start, no credit card required.
Get Started Free →fritzandfriends/cli-compile-surface-hardening
Keep migrated Blazor output compiling when more Web Forms artifacts stay on the generated compile surface
Passed 20 of 22 test cases with the skill, and 8 of 22 without it.
and 19 more in the full report
13 fixed7 passed either way1 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
When the migration CLI encounters an unbound render method reference like `@GetHeaderTitle()` inside a Razor component markup, what C# method stub signature should be generated in the code-behind file to satisfy compilation?
| Checked | Without skill | With skill |
|---|---|---|
| Recommends generating render-method stubs that return `object?`. | Missed | Passed |
| Specifies creating the method stub with zero parameters corresponding to `@MethodName()`. | Passed | Passed |
The instructions your model reads when the skill loads.
Use 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.test cases passed, vs 8 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.