npx skills add ...
npx skills add microsoft/win-dev-skills --skill winui-setup
Install and verify the prerequisites the win-dev-skills WinUI 3 toolchain depends on — .NET SDK 8.0.100+, WinApp CLI 0.6+, and Developer Mode. Use only when the user explicitly asks to set up or repair the toolchain. Do not invoke automatically when another skill reports a missing prerequisite; tell the user what is missing and ask them to invoke this skill.
npx skills add microsoft/win-dev-skills --skill winui-setup
Install and verify the prerequisites every other winui-* skill assumes. WinApp CLI 0.6 owns WinUI template discovery and installation through winapp new; do not install the template pack separately.
[!IMPORTANT] Run this skill only when the user explicitly asks to set up or repair the toolchain. If it is loaded without an explicit request, do not run checks or installations; explain what the skill changes and wait for confirmation.
This skill is idempotent: detect everything first, install or upgrade only what is needed, and print one final summary.
Run these checks together so the user sees the full state before anything changes:
Print a one-shot status table:
Only when no SDK at or above 8.0.100 was found:
Do not install another SDK when 8.0.100+, 9.x, or 10.x is already present.
If winapp is missing, install it. If it is present but below 0.6.0, try to upgrade it. Skip both commands when the installed version already meets the minimum:
Refresh PATH after any winget install or upgrade:
Run the version detection again. If the result is still below 0.6.0, report the actual version and mark setup failed; do not continue with old command fallbacks.
winapp newinstalls the officialMicrosoft.WindowsAppSDK.WinUI.CSharp.Templatespack on demand and can update it with--template-version latest. Do not rundotnet new installduring setup.
Developer Mode requires admin elevation. Ask the user before triggering UAC. Only if they agree, elevate this one operation:
If the user declines or dismisses UAC, continue to the summary and print the command for later use.
Always print a single summary:
You're ready. If the current harness exposes the winui-dev orchestrator agent,
start a fresh session with that agent and ask it to build a WinUI app. Otherwise,
start a fresh session in the current harness and ask it to perform the WinUI task;
it will load the relevant winui-* skills on demand.
For GitHub Copilot CLI, for example:
dotnet and winapp.winapp new owns it in 0.6+.