Agent skill · Databases

winui3-migration-guide

UWP-to-WinUI 3 migration reference. Maps legacy UWP APIs to correct Windows App SDK equivalents with before/after code snippets. Covers namespace changes, threading (CoreDispatcher to DispatcherQueue), windowing (CoreWindow to AppWindow), dialogs, pickers, sharing, printing, background tasks, and the most common Copilot code generation mistakes.

GitHub68,948★ · +463/wk · 2 repos on radarProfile →
copilotMIT
Install
npx skills add github/awesome-copilot --skill winui3-migration-guide --agent copilot

Same command for any agent — swap --agent for claude-code, codex, cursor.

Facts
Files in the skill folder: 1
SKILL.md size: 9 KB
Bundled scripts: none
Path: skills/winui3-migration-guide/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 37,432 · +281 this week
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# WinUI 3 Migration Guide Use this skill when migrating UWP apps to WinUI 3 / Windows App SDK, or when verifying that generated code uses correct WinUI 3 APIs instead of legacy UWP patterns. --- ## Namespace Changes All `Windows.UI.Xaml.*` namespaces move to `Microsoft.UI.Xaml.*`: | UWP Namespace | WinUI 3 Namespace | |--------------|-------------------| | `Windows.UI.Xaml` | `Microsoft.UI.Xaml` | | `Windows.UI.Xaml.Controls` | `Microsoft.UI.Xaml.Controls` | | `Windows.UI.Xaml.Media` | `Microsoft.UI.Xaml.Media` | | `Windows.UI.Xaml.Input` | `Microsoft.UI.Xaml.Input` | | `Windows.UI.Xaml.Data` | `Microsoft.UI.Xaml.Data` | | `Windows.UI.Xaml.Navigation` | `Microsoft.UI.Xaml.Navigation` | | `Windows.UI.Xaml.Shapes` | `Microsoft.UI.Xaml.Shapes` | | `Windows.UI.Composition` | `Microsoft.UI.Composition` | | `Windows.UI.Input` | `Microsoft.UI.Input` | | `Windows.UI.Colors` | `Microsoft.UI.Colors` | | `Windows.UI.Text` | `Microsoft.UI.Text` | | `Windows.UI.Core` | `Microsoft.UI.Dispatching` (for dispatcher) | --- ## Top 3 Most Common Copilot Mistakes ### 1. ContentDialog Without XamlRoot ```csharp // ❌ WRONG — Throws InvalidOperationException in WinUI 3 var dialog = new ContentDialog { Tit

What's inside
Steps it walks through
  1. Namespace Changes
  2. Top 3 Most Common Copilot Mistakes
  3. 1. ContentDialog Without XamlRoot
  4. 2. MessageDialog Instead of ContentDialog
  5. 3. CoreDispatcher Instead of DispatcherQueue
  6. Windowing Migration
  7. Window Reference
  8. Window Management
  9. Title Bar
  10. Dialogs and Pickers Migration
  11. File/Folder Pickers
  12. Threading Migration
  13. Background Tasks Migration
  14. App Settings Migration
More from awesome-copilot
All skills →
acquire-codebase-knowledgeUse this skill when the user explicitly asks to map, document, or onboard into an existing…AI & Agentsazure-architecture-autopilotDesign Azure infrastructure using natural language, or analyze existing Azure resources to…Securitymini-context-graphA persistent, compounding knowledge base combining Karpathy's LLM Wiki pattern with a structured…Content & Marketingcode-tourUse this skill to create CodeTour .tour files — persona-targeted, step-by-step walkthroughs that…Securityagent-skill-stackFind, evaluate, and assemble the smallest compatible set of AI Agent Skills for an end-to-end…Securitybuild-evidence-mapBuild an auditable evidence map for a contested technical choice, research synthesis, proposal…Code Review & Quality
About this skill
What does the winui3-migration-guide skill do?

UWP-to-WinUI 3 migration reference. Maps legacy UWP APIs to correct Windows App SDK equivalents with before/after code snippets. Covers namespace changes, threading (CoreDispatcher to DispatcherQueue), windowing (CoreWindow to AppWindow), dialogs, pickers, sharing, printing, background tasks, and the most common Copilot code generation mistakes.

How do I install it?

Run `npx skills add github/awesome-copilot --skill winui3-migration-guide --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From github/awesome-copilot, a repository with 37,432 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going
All skills →
The full catalog, by category and by tool.
Open Source Radar →
The repositories these skills come from, watched daily.
The people behind them →
Makers and builders across the ecosystem.