wpf-to-winui3-migration Skill
Guide for migrating PowerToys modules from WPF to WinUI 3 (Windows App SDK). Use when asked to migrate WPF code, convert WPF XAML to WinUI, replace System.Windows namespaces with Microsoft.UI.Xaml, update Dispatcher to DispatcherQueue, replace DynamicResource with ThemeResource, migrate imaging APIs from System.Windows Published by microsoft in PowerToys.
What is wpf-to-winui3-migration Skill?
Guide for migrating PowerToys modules from WPF to WinUI 3 (Windows App SDK). Use when asked to migrate WPF code, convert WPF XAML to WinUI, replace System.Windows namespaces with Microsoft.UI.Xaml, update Dispatcher to DispatcherQueue, replace DynamicResource with ThemeResource, migrate imaging APIs from System.Windows Published by microsoft in PowerToys. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Design and media
- Design and media use cases
Technical details
- Install or run with Copy skill directory
When to use wpf-to-winui3-migration Skill
- Use it for design and media.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/PowerToys
- Skill file: .github/skills/wpf-to-winui3-migration/SKILL.md
What it does
Guide for migrating PowerToys modules from WPF to WinUI 3 (Windows App SDK). Use when asked to migrate WPF code, convert WPF XAML to WinUI, replace System.Windows namespaces with Microsoft.UI.Xaml, update Dispatcher to DispatcherQueue, replace DynamicResource with ThemeResource, migrate imaging APIs from System.Windows
Skill instructions
WPF to WinUI 3 Migration Skill Migrate PowerToys modules from WPF (System.Windows.) to WinUI 3 (Microsoft.UI.Xaml. / Windows App SDK). Based on patterns validated in the ImageResizer module migration. When to Use This Skill - Migrate a PowerToys module from WPF to WinUI 3 - Convert WPF XAML files to WinUI 3 XAML - Replace System.Windows namespaces with Microsoft.UI.Xaml - Migrate Dispatcher usage to DispatcherQueue - Migrate custom Observable/RelayCommand to CommunityToolkit.Mvvm source generators - Replace WPF-UI (Lepo) controls with native WinUI 3 controls - Convert imaging code from System.Windows.Media.Imaging to Windows.Graphics.Imaging - Handle WPF Window vs WinUI Window differences (sizing, positioning, SizeToContent) - Migrate resource files from .resx to .resw with ResourceLoader - Fix installer/build pipeline issues after WinUI 3 migration - Update project files, NuGet packages, and signing config Prerequisites - Visual Studio 2022 17.4+ - Windows App SDK NuGet package (Micro
Explore related resources
Frequently asked questions
What is wpf-to-winui3-migration?
wpf-to-winui3-migration is a open-source AI agent skill with Copy skill directory. Guide for migrating PowerToys modules from WPF to WinUI 3 (Windows App SDK).
Who is wpf-to-winui3-migration best for?
wpf-to-winui3-migration is best for reusing agent instructions, scripts, and references, design and media workflows.
How do I install wpf-to-winui3-migration?
Install or run wpf-to-winui3-migration using Copy skill directory. Check wpf-to-winui3-migration for the latest setup command.
Is wpf-to-winui3-migration actively maintained?
wpf-to-winui3-migration may need a closer maintenance check before production use.
Auto-fetched from GitHub.
