Ready to supercharge your AI agents?

Install any skill in seconds. Free to start, no credit card required.

Get Started Free →

Fritzandfriends/CLI Compile Surface Hardening — measured AI agent skill | DecimalAI

fritzandfriends/cli-compile-surface-hardening

NewSkillScoreMaintained

Keep migrated Blazor output compiling when more Web Forms artifacts stay on the generated compile surface

codingby fritzandfriends

Links this skill to your agents and keeps it current with the author’s updates.

Automatic

Coding pack

1 · One-time — install the CLI (docs ↗)

pip install decimalai

2 · Get the skill — writes .claude/skills/fritzandfriends-cli-compile-surface-hardening/SKILL.md

decimalai skills pull fritzandfriends-cli-compile-surface-hardening --out .claude/skills/

No CLI? Get the same file — curl · raw file

curl -fsSL --create-dirs -o .claude/skills/fritzandfriends-cli-compile-surface-hardening/SKILL.md https://app.decimal.ai/s/fritzandfriends-cli-compile-surface-hardening/SKILL.md

Raw file: /s/fritzandfriends-cli-compile-surface-hardening/SKILL.md ↗ · machine-readable summary at /s/fritzandfriends-cli-compile-surface-hardening.json ↗

In productionGlobal

how this skill behaves on real traffic · last 30 days

No production data for this skill yet — usage numbers appear here once agents start running it.

Anonymized aggregate across every org using this skill — proof from real production use, not a demo.

Does this skill help? · Benchmark: with vs. withoutsign in to run this on your agents

22 test cases from the publisher’s eval.yaml · each run twice on gemini-3.6-flash — with the skill injected, then without · last run 1h ago

Yes — +55% lift-40% tokens0% turns91% of whole cases pass with skill (20/22)

Test case	Without → With	Effect	Δ tokens	Δ turns
case-01	✗→✓	▲ Improved	-28%	0%
case-02	✗→✓	▲ Improved	-52%	0%
case-03	✗→✓	▲ Improved	-10%	0%
case-05	✗→✓	▲ Improved	-24%	0%
case-06	✗→✓	▲ Improved	-62%	0%

Showing 5 of 22 cases

SkillSafety

✓ 3 of 3 passed

Code scan15 of 15 checks clean

0 critical · 0 warning · 0 info — scanner v4 — 8/3/2026

live_secretremote_code_executionreverse_shelldata_exfiltrationssrf_metadataagent_snoopinganti_refusaldestructive_commandsobfuscated_unicodeunicode_homoglyphopaque_blobsuspicious_urltool_overreachtrigger_abuseprompt_injection_phrasing

IntentSafe

LLM judge · does the skill do what it claims

ContentClean

LLM judge · policy & harmful-content review

Source

Imported

fritzandfriends / blazorwebformscomponents

.squad/skills/cli-compile-surface-hardening/SKILL.md

View on GitHub ↗

License MITImported 8/3/2026Version v1

Skill contents

SKILL.md

Context

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.

Patterns

In generated migration projects, prefer <EnforceCodeStyleInBuild>false</EnforceCodeStyleInBuild> over broad warning suppression when copied legacy files would otherwise fail repo-level IDE analyzers.
Add validator generic arguments with the BWFC component's actual generic parameter name, not an assumed TValue alias:
RequiredFieldValidator → Type="string"
CompareValidator / RangeValidator → InputType="string"
Run markup-driven member stub generation after the main code-behind transforms, using transformed Razor markup (metadata.MarkupContent) as the source of truth.
Stub only the deterministic missing-member shapes that are safe to infer mechanically:
@MethodName() → render-method stub returning object?
@_fieldName → private object? field
OnClick="@HandlerName" and similar → void HandlerName(object? sender, EventArgs e)
Register new transforms in both production DI (src\BlazorWebFormsComponents.Cli\Program.cs) and tests\BlazorWebFormsComponents.Cli.Tests\TestHelpers.cs so the lightweight and full pipelines stay aligned.

Examples

src\BlazorWebFormsComponents.Cli\Transforms\Markup\ValidatorGenericTypeTransform.cs
src\BlazorWebFormsComponents.Cli\Transforms\CodeBehind\MarkupReferencedMemberStubTransform.cs
tests\BlazorWebFormsComponents.Cli.Tests\TransformUnit\CompiledCodeBehindStubPipelineTests.cs

Anti-Patterns

Suppressing all warnings/errors in the generated project when only code-style analyzers are the problem.
Injecting TValue="string" into BWFC validators that actually expose Type or InputType generic parameters.
Generating markup-reference stubs before markup transforms run, or reading original Web Forms markup instead of the transformed Razor output.
Emitting placeholder stubs for every @Identifier token; restrict deterministic generation to the specific reference shapes you can classify safely.

Want to see if fritzandfriends/cli-compile-surface-hardening would activate on your phrasing? Try it before you install — no LLM call, no signup.

Other measured skills in the registry, with their headline benchmark lift.