dotnet-ui

Identify and unify best practices for cross-platform .NET UI applications.

2|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/sayedihashimi/copilot-skill-eval --skill dotnet-ui-sayedihashimi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-ui
Source: https://github.com/sayedihashimi/copilot-skill-eval/tree/main/examples/aspnet-razor-pages/plugins/dotnet-artisan/skills/dotnet-ui
Command: npx skills add https://github.com/sayedihashimi/copilot-skill-eval --skill dotnet-ui-sayedihashimi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides a consolidated guide for designing and implementing UI across Blazor, MAUI, Uno Platform, WPF, WinUI, and WinForms to streamline architecture decisions and accelerate delivery.

Core Features & Use Cases

  • Cross-framework UI guidance across Blazor, MAUI, Uno Platform, WPF, WinUI, and WinForms.
  • Accessibility and localization patterns spanning ARIA, SemanticProperties, RTL, and resource strategies.
  • Migration and interoperability patterns across targets, including MVVM / MVUX, DI, and platform bindings.

Quick Start

Summarize best practices for building cross-platform .NET UI apps across the listed frameworks.

Frequently Asked Questions about dotnet-ui

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

FAQPage Schema
What is the best way to build cross-platform .NET UI applications across multiple frameworks like Blazor and MAUI?

The best way to build cross-platform .NET UI applications is to unify architecture decisions, accessibility, and localization patterns across Blazor, MAUI, Uno Platform, WPF, WinUI, and WinForms to ensure rapid, safe implementation and streamlined delivery.

How do I choose between Blazor, MAUI, and Uno Platform for my .NET UI project?

Choosing between Blazor, MAUI, and Uno Platform involves evaluating per-framework nuances, render modes, and platform bindings against your specific UI development planning needs to identify the most suitable framework-agnostic design patterns.

Does Blazor work with WinUI and WPF for cross-platform .NET UI migration?

Blazor works alongside WinUI and WPF by applying migration and interoperability patterns, enabling cross-target transitions using MVVM, MVUX, dependency injection, and platform bindings for unified UI architecture.

How do I implement accessibility and localization in .NET MAUI and Blazor apps?

Implement accessibility and localization in .NET MAUI and Blazor by applying cross-framework patterns spanning ARIA, SemanticProperties, RTL text directions, and unified resource strategies to ensure compliant UI design.

Can I use MVUX and dependency injection across WPF, WinForms, and WinUI?

You can use MVUX and dependency injection across WPF, WinForms, and WinUI by following established migration and interoperability patterns that support platform bindings and framework-agnostic architecture.

What are the limitations of unifying architecture patterns across Blazor and WinForms?

Limitations of unifying architecture across Blazor and WinForms stem from distinct render modes and per-framework nuances, requiring careful evaluation of migration patterns and platform bindings to avoid incompatible UI designs.