winui-to-avalonia

Port WinUI or Windows App SDK applications to Avalonia, including shell design, dependency-property patterns, theme resources, composition, commands, dialogs, and platform integration. Use for `NavigationView`, `ContentDialog`, `ThemeResource`, `VisualStateManager`, `ItemsRepeater`, `AppWindow`, or broader WinUI-to-Avalonia migration work.

Stars 57

Forks 6

Install this agent skill to your Project

npx add-skill https://github.com/wieslawsoltes/development-plugin-for-avalonia/tree/main/skills/winui-to-avalonia

SKILL.md

WinUI to Avalonia

Start with:

../../references/65-winui-to-avalonia-modern-ui-conversion-index.md
../../references/winui-to-avalonia/README.md

Prioritize the chapters that match the source app:

object or property system, bindings, resources, and state mapping
NavigationView, dialog, titlebar, and multi-window shell behavior
composition, rendering, scroll, gesture, and advanced control migration
platform services, activation, storage, notifications, and WebView boundaries

Workflow

Identify the WinUI shell and state model before moving individual controls.
Translate ThemeResource, VisualStateManager, and composition assumptions explicitly.
Rebuild platform integration through Avalonia services rather than Windows-only primitives.
Keep modern-shell decisions intentional instead of chasing one-to-one surface parity.

Rules

Do not treat NavigationView, ContentDialog, or AppWindow as direct API renames.
Separate composition effects from essential interaction behavior.
Make Windows-specific contracts and Avalonia cross-platform replacements explicit.