Agent skill
wpf-to-avalonia
Port WPF applications and patterns to Avalonia, including dependency-property mapping, bindings, resources, templates, layout, rendering, and shell behavior. Use for `DependencyProperty`, routed-command, trigger, `Frame` or `Page`, `OnRender`, `HwndHost`, or other WPF-to-Avalonia migration work.
Install this agent skill to your Project
npx add-skill https://github.com/wieslawsoltes/development-plugin-for-avalonia/tree/main/skills/wpf-to-avalonia
SKILL.md
WPF to Avalonia
Start with:
../../references/64-wpf-to-avalonia-modern-ui-conversion-index.md../../references/wpf-to-avalonia/README.md
Prioritize the chapters that match the WPF source:
- property system, bindings, resources, styles, and templates
- layout, navigation, windows, dialogs, and dispatcher workflows
- rendering, animation, popup, interop, and document workflows
- advanced control families, selection models, and platform services
Workflow
- Map the WPF concept first, then choose the Avalonia equivalent or redesign.
- Call out where Avalonia does not preserve a WPF subsystem directly, especially triggers, navigation, and interop.
- Replace resource, layout, and rendering assumptions before doing control-by-control cleanup.
- Keep the migration narrative explicit about what stays familiar and what changes materially.
Rules
- Do not promise WPF trigger,
CommandManager, orHwndHostparity where it does not exist. - Use Avalonia selectors, templates, and state patterns rather than recreating WPF internals.
- Keep document and printing workflows in a separate explicit decision track.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
development-plugin-for-avalonia
Repo-local umbrella skill for building, reviewing, designing, porting, and migrating Avalonia applications with modern XAML/C# patterns on Avalonia 11.3.12. Use when working inside this repository and the request is broad Avalonia work; route quickly to the focused plugin skills for startup, bindings, styling, controls, layout, rendering, testing, design systems, or HTML/WinForms/WPF/WinUI/Avalonia 12 migration work.
avalonia-styling-and-resources
Build or troubleshoot Avalonia styles, themes, resources, property-system usage, theme variants, resource packaging, and custom theme architecture. Use for selector fixes, attached properties, resource lookup problems, theme switching, library resource packaging, or code-only theme work.
avalonia-design-systems
Design polished Avalonia design systems with reusable tokens, typography, spacing, shell composition, dense workflow UX, motion, and governance rules. Use for professional UI direction, design-token architecture, responsive layout systems, information architecture, or high-quality desktop workflow design.
avalonia-testing-diagnostics-and-performance
Validate Avalonia applications with headless tests, render or UI tests, diagnostics tooling, troubleshooting workflows, and performance reviews. Use for test strategy, DevTools or profiler usage, performance regressions, rendering investigations, or production hardening passes.
avalonia-accessibility-and-validation
Design or review Avalonia validation, data-error presentation, accessibility semantics, automation properties, focus order, and testable UI metadata. Use for validation pipelines, screen-reader support, keyboard-only UX, automation-tree issues, or accessibility hardening.
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.
Didn't find tool you were looking for?