component-development

Create Blazor components that emulate ASP.NET Web Forms controls.

450|78|Updated Dec 3, 2019
One-click install
npx skills add https://github.com/FritzAndFriends/BlazorWebFormsComponents --skill component-development-fritzandfriends
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: component-development
Source: https://github.com/FritzAndFriends/BlazorWebFormsComponents/tree/main/.github/skills/component-development
Command: npx skills add https://github.com/FritzAndFriends/BlazorWebFormsComponents --skill component-development-fritzandfriends

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers create Blazor components that faithfully emulate ASP.NET Web Forms controls, enabling a smoother migration path and consistent UI behavior.

Core Features & Use Cases

  • Structured development workflow: guidance from file creation, inheritance, testing, and documentation to navigation updates.
  • Standards conformance: enforces frontmatter in SKILL.md and consistent project layout across components.
  • Use Case: when adding a new Blazor control, follow this skill to ensure it mirrors Web Forms output and is integrated into samples and tests.

Quick Start

Identify the target Web Forms control, create component files under src/BlazorWebFormsComponents, choose the appropriate base class, add tests and sample pages, and update navigation and docs.

Frequently Asked Questions about component-development

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate ASP.NET Web Forms controls to Blazor?

You migrate Web Forms controls to Blazor by creating component files under src/BlazorWebFormsComponents, selecting an appropriate base class that emulates the original control behavior, and updating navigation across BlazorServerSide samples and related documentation.

What is the workflow for developing Blazor components that emulate Web Forms controls?

The component development workflow spans file creation, base-class selection, testing, documentation, and navigation updates across BlazorServerSide samples to ensure new components faithfully mirror Web Forms output and behavior.

Can I use this approach to ensure consistent UI behavior during a Web Forms to Blazor migration?

Yes, developing Blazor components that faithfully emulate ASP.NET Web Forms controls enables a smoother migration path and consistent UI behavior by mirroring the original control output within the BlazorServerSide samples.

Do I need to add tests and sample pages when creating a new Blazor control?

Yes, the structured development workflow requires adding tests and sample pages for new Blazor controls, alongside updating navigation and documentation, to ensure the component is fully integrated and validated within the project.

What's the best way to structure a Blazor component project for Web Forms emulation?

The best way is enforcing a consistent project layout with SKILL.md frontmatter, placing component files under src/BlazorWebFormsComponents, and utilizing optional scripts, references, and assets directories to supply necessary resources.

Why does my Blazor component need a SKILL.md frontmatter file?

A SKILL.md frontmatter with a name and description is required to enforce standards conformance across the component development workflow and maintain a consistent project layout for Web Forms emulation.