Winui3 Migration Guide

Name: Winui3 Migration Guide
Author: github

Official

github·vlatest·database·MIT

Automates WinUI 3 migration from older frameworks, providing step-by-step guidance and code adjustments based on GitHub best practices.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

Run this in your project

terminal

$ npx skills add github/awesome-copilot --skill winui3-migration-guide -a claude-code

Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

github

Matched to the vendor's own GitHub organisation.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned 28 Sept 2026

This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

Declares what it does: failed
No SKILL.md was found in the skill's directory.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned github/awesome-copilot at 6c4d33b9cf.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit: 6c4d33b9cf
Manifest: skills/winui3-migration-guide/SKILL.md
Scanned: 0 files

This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.

What each check looks for →

About this skill

What it does

The winui3-migration-guide skill provides detailed instructions and best practices for migrating applications to WinUI 3, a modern UI framework for Windows apps. It covers topics like project setup, control migration, styling, and compatibility considerations.

When to use it

You are upgrading an existing UWP or WPF application to WinUI 3.
You need guidance on replacing deprecated controls with their WinUI 3 equivalents.
Your team is preparing for a Windows app modernization initiative.
You're encountering layout or styling issues after migrating to WinUI 3.

Key capabilities

Step-by-step migration workflows
Code examples for common control conversions
Troubleshooting tips for compatibility issues
Recommendations for tooling and IDE support

Example prompts

"How do I migrate a WPF ListView to WinUI 3?"
"What are the steps to update my UWP app to use WinUI 3 controls?"
"I'm having layout issues after migrating to WinUI 3—what should I check?"

Tips & gotchas

Ensure your project targets .NET 6 or later, as WinUI 3 requires this runtime.
Review third-party libraries for WinUI 3 compatibility before migration.