Enforce canonical migration standards for ASP.NET Web Forms to Blazor using BWFC. Covers target architecture (.NET 10, Server Interactive), database provider detection, event handler preservation, SelectMethod patterns, and page lifecycle mapping. WHEN: "migration standards", "target architecture", "render mode placement", "page base class", "Layer 1 vs Layer 2".
92
88%
Does it follow best practices?
Impact
100%
1.81xAverage score across 3 eval scenarios
Passed
No known issues
SelectMethod and BWFC data control migration
BWFC ListView used
100%
100%
SelectMethod preserved
60%
100%
SelectMethod signature correct
100%
100%
Event attribute preserved
0%
100%
Handler signature updated
20%
100%
No System.Web.UI.Page base class
50%
100%
var for local variables
100%
100%
NavigationManager for redirect
100%
100%
GroupItemCount preserved
100%
100%
Migration notes present
100%
100%
Blazor project scaffold and render mode setup
Static RenderMode using in _Imports
0%
100%
WebFormsPageBase in _Imports
0%
100%
rendermode on HeadOutlet in App.razor
0%
100%
rendermode on Routes in App.razor
100%
100%
No standalone rendermode in _Imports
100%
100%
BWFC Page component in MainLayout
0%
100%
LayoutComponentBase in MainLayout
100%
100%
Notes mention rendermode placement
50%
100%
Notes mention base class strategy
37%
100%
InteractiveServer shorthand used
100%
100%
Playwright test patterns and enhanced navigation
BlurAsync or Tab after FillAsync
0%
100%
Delay after blur
0%
100%
Submit after binding committed
60%
100%
data-enhance-nav or form method=post
26%
100%
No plain anchor to server endpoint
100%
100%
Testing notes explain blur pattern
62%
100%
Testing notes explain enhanced nav
100%
100%
Multiple fields filled
100%
100%
Checkout endpoint test present
100%
100%
onchange vs oninput distinction noted
100%
100%
9bf8669
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.