winui-setup
Install and verify WinUI 3 prerequisites — .NET SDK 8.0.100+, WinApp CLI 0.7+, and Developer Mode; identify additional Native AOT and Windows Sandbox requirements. Use when the user asks to set up or repair the toolchain, or when another WinUI skill finds a missing or outdated prerequisite.
- Installs
- 169
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/microsoft/win-dev-skills --skill winui-setup- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads winui-setup automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Purpose
Install and verify the prerequisites every other winui-* skill assumes. WinApp CLI 0.7 owns WinUI template discovery and installation through winapp new; do not install the template pack separately. The project's target framework may require a newer .NET SDK than the CLI's minimum.
[!IMPORTANT] Install per-user prerequisites (WinApp CLI) without asking, and tell the user what changed. Ask before anything that needs admin rights (UAC) or a large toolchain — the .NET SDK, Developer Mode, and Native AOT build tools. Windows Sandbox enablement is the user's to do.
This skill is idempotent: detect everything first, install or upgrade only what is needed, and print one final summary.
Steps
Detect everything
Run these checks together so the user sees the full state before anything changes:
$minimumDotNet = [version]'8.0.100'
$minimumWinApp = [version]'0.7.0'
# .NET SDK — project-mode winapp run requires SDK 8.0.100+
$dotnetSdks = @(& dotnet --list-sdks 2>$null) | ForEach-Object {
$text = ($_ -replace ' \[.*$','').Trim()
$parsed = $null
if ([version]::TryParse(($text -split '-')[0], [ref]$parsed)) { $parsed }
}
$dotnetVersion = $dotnetSdks |
Where-Object { $_ -ge $minimumDotNet } |
Sort-Object -Descending |
Select-Object -First 1
$dotnetOk = $null -ne $dotnetVersion
# WinApp CLI — require released 0.7+ for the migrated workflows
$winappCmd = Get-Command winapp -ErrorAction SilentlyContinue
$winappVersion = $null
$winappPrerelease = $false
if ($winappCmd) {
foreach ($line in @(& winapp --version 2>$null)) {
$match = [regex]::Match(
[string]$line,
'^\s*v?(?<version>\d+\.\d+\.\d+)(?:-(?<prerelease>[0-9A-Za-z.-]+))?(?:\+[0-9A-Za-z.-]+)?\s*$'
)
if ($match.Success) {
$parsed = $null
if ([version]::TryParse($match.Groups['version'].Value, [ref]$parsed)) {
$winappVersion = $parsed
$winappPrerelease = $match.Groups['prerelease'].Success
}
}
}
}
$winappOk = ($winappVersion -ge $minimumWinApp) -and -not $winappPrerelease
# Developer Mode
$devModeOk = ((Get-ItemProperty `
-Path 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\AppModelUnlock' `
-Name AllowDevelopmentWithoutDevLicense -ErrorAction SilentlyContinue
).AllowDevelopmentWithoutDevLicense) -eq 1
Print a one-shot status table:
.NET SDK >= 8.0.100 [OK] found 10.0.100
WinApp CLI >= 0.7.0 [!] found 0.6.0 — will upgrade
Developer Mode [X] disabled — needs admin to enable
Install what's missing
.NET SDK (ask first)
The SDK installer is machine-wide and triggers UAC. Ask the user first. When they agree and no SDK at or above 8.0.100 was found, install the recommended SDK:
winget install --id Microsoft.DotNet.SDK.10 --exact --silent --accept-package-agreements --accept-source-agreements
Do not install another SDK when one already satisfies both the CLI minimum and
the requested project's target framework / global.json. The CLI's minimum
does not let an 8.x SDK build a net10.0-windows app.
If the base check passed but the requested project needs another SDK, report
that requirement and offer to install its matching SDK rather than declaring
the project ready. If the user declines, print the command for later use.
WinApp CLI (no admin needed)
WinApp CLI is a per-user MSIX package, so install or upgrade it without asking and tell the user what changed. If winapp is missing, install it. If it is below released 0.7.0, upgrade it. Skip both when the installed version already meets the minimum:
# When winapp is missing
winget install --id Microsoft.WinAppCli --exact --silent --accept-package-agreements --accept-source-agreements
# When winapp does not meet the released 0.7.0 minimum
winget upgrade --id Microsoft.WinAppCli --exact --silent --accept-package-agreements --accept-source-agreements
Refresh PATH after any winget install or upgrade:
$env:Path = [Environment]::GetEnvironmentVariable('Path','Machine') + ';' +
[Environment]::GetEnvironmentVariable('Path','User')
Run the version detection again. If a released 0.7.0 or later is still unavailable, report the actual version and mark setup blocked; do not fall back to older commands. A prerelease doesn't meet the requirement unless the user asks for preview validation.
Developer Mode (ask first)
Developer Mode requires admin elevation. Ask the user before triggering UAC. Only if they agree, elevate this one operation:
Start-Process powershell -Verb RunAs -ArgumentList @(
'-NoProfile','-Command',
"New-Item -Path 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\AppModelUnlock' -Force | Out-Null; " +
"Set-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\AppModelUnlock' " +
"-Name AllowDevelopmentWithoutDevLicense -Type DWord -Value 1"
) -Wait
If the user declines or dismisses UAC, continue to the summary and print the command for later use.
Additional requirements for the requested workflow
| Workflow | Additional requirements |
|---|---|
| Native AOT publish/run | Windows native compiler/linker toolchain: Visual Studio or Build Tools with Desktop development with C++, including the target architecture's tools and Windows SDK. See Native AOT prerequisites. These are not required for normal JIT iteration. |
| Windows Sandbox app runs and UI automation (preferred when available) | WinApp's integration requires Windows 11 24H2+, hardware virtualization, and a working Windows Sandbox feature/client. Supported editions include Pro, Enterprise, and Education; not Home. Input/capture needs an unlocked host and a connected, non-minimized client. See WinApp Sandbox prerequisites. |
Report these separately from the base toolchain. winapp target snapshot sandbox --json inspects an existing
guest without starting or repairing it; "no target running" alone does not
mean the Windows feature is unavailable. winui-ui-testing
Step 1 defines what to do when Windows Sandbox is unavailable.
Enabling Windows Sandbox is a user action (admin plus a reboot): ask the user to open Turn Windows features on or off, select Windows Sandbox, and restart if prompted. Hardware virtualization must be enabled; a VM may also require nested virtualization. See Microsoft's supported editions and installation steps.
Final summary
Always print a single summary:
==== winui-setup summary ====
.NET SDK >= 8.0.100 [>] already present (10.0.100)
WinApp CLI >= 0.7.0 [OK] upgraded to 0.7.0
Developer Mode [OK] enabled
Only report readiness for the workflows whose requirements passed. 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:
copilot --agent winui:winui-dev -p "build me a WinUI 3 markdown editor"
Things to NOT do
- Do not install Visual Studio; it is optional. Native AOT needs only the MSVC C++ build tools, a separate, explicitly approved setup.
- Do not install or upgrade the user's AI coding harness; this skill manages Windows/WinUI development prerequisites only.
- Do not elevate the entire session; request elevation only for the specific approved setup operation.
- Do not silently retry failed installs.
FAQ
What does the winui-setup skill do?
Install and verify WinUI 3 prerequisites — .NET SDK 8.0.100+, WinApp CLI 0.7+, and Developer Mode; identify additional Native AOT and Windows Sandbox requirements. Use when the user asks to set up or repair the toolchain, or when another WinUI skill finds a missing or outdated prerequisite.
How do I install winui-setup?
Run npx skills add https://github.com/microsoft/win-dev-skills --skill winui-setup in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/winui-setup/ (personal) or .claude/skills/winui-setup/ (project).
Which AI agents can use winui-setup?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is winui-setup safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains winui-setup?
It is published by microsoft in microsoft/win-dev-skills, and it is an official skill from the maker of the technology it covers. It has 169 recorded installs.
More from microsoft/win-dev-skills
winui-design
microsoft/win-dev-skills
Open the skill to read its SKILL.md instructions.
winui-ui-testing
microsoft/win-dev-skills
Open the skill to read its SKILL.md instructions.
winui-dev-workflow
microsoft/win-dev-skills
Build and run workflow for WinUI 3 apps with WinApp CLI 0.7+ — project creation with winapp new, per-app NuGet analyzer setup, project-mode winapp run, Native AOT publish runs, crash diagnosis, and prerequisites. Use when creating, building, running, or fixing build errors in a WinUI 3 project.
winui-code-review
microsoft/win-dev-skills
Open the skill to read its SKILL.md instructions.
winui-packaging
microsoft/win-dev-skills
Open the skill to read its SKILL.md instructions.
pr-review
microsoft/win-dev-skills
Open the skill to read its SKILL.md instructions.
Popular backend & apis skills
find-skills
vercel-labs/skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
entra-app-registration
microsoft/azure-skills
Guides Microsoft Entra ID app registration, OAuth 2.0 authentication, and MSAL integration. USE FOR: create app registration, register Azure AD app, configure OAuth, set up authentication, add API permissions, generate service principal, MSAL example, console app auth, Entra ID setup, Azure AD authentication. DO NOT USE FOR: Key Vault secrets (use azure-keyvault-expiration-audit), general Azure resource security guidance.
google-agents-cli-adk-code
google/agents-cli
This skill should be used when the user wants to "write agent code", "build an agent with ADK", "add a tool", "create a callback", "define an agent", "use state management" — in a project that needs ADK (Agent Development Kit) API patterns and code examples. It provides a quick reference for agent types, tool definitions, orchestration patterns, callbacks, state management, the graph Workflow API, and reference recipes to study. Do NOT use for scaffolding (use google-agents-cli-scaffold) or deployment (use google-agents-cli-deploy).
embedded-captions
heygen-com/hyperframes
Add captions or subtitles to an existing single-subject talking-head video without editing the footage. Use for plain verbatim captions, cinematic captions embedded behind the subject, VFX captions, “炸/特效/酷炫字幕,” or a named identity from the 35-style catalog. Route by visual identity, not by backend engine. The quiet anchor rail is the default; embed every word only when the user explicitly wants a fully cinematic treatment. The workflow runs locally end to end, including transcription and subject matting; split multi-shot footage before applying it.
entra-agent-id
microsoft/azure-skills
Provision Microsoft Entra Agent Identity Blueprints, BlueprintPrincipals, and per-instance Agent Identities via Microsoft Graph, and configure OAuth 2.0 token exchange (fmipath, OBO, cross-tenant) including the Microsoft Entra SDK for AgentID sidecar. USE FOR: Agent Identity Blueprint, BlueprintPrincipal, agent OAuth, fmipath token exchange, agent OBO, Workload Identity Federation for agents, polyglot agent auth, Microsoft.Identity.Web.AgentIdentities. DO NOT USE FOR: standard Entra app registration (use entra-app-registration), Microsoft Foundry agent authoring (use microsoft-foundry).
neon
neondatabase/agent-skills
Overview of Neon, a complete set of cloud backend primitives around Lakebase Postgres: Auth, Object Storage, Functions, the AI Gateway, and Realtime. Start here to choose Neon for undecided login, files, APIs, and LLM calls, set up the CLI or MCP server, and follow the branch-first workflow. Use when building an app or backend on Neon, or when "Neon" or "Lakebase Postgres" is mentioned. Child skill neon-postgres wins for an existing DATABASEURL, SQL, schema, inspect, or search. Child skill neon-auth wins for login, users, sessions, identity routing, and Managed Better Auth setup. Child skill neon-realtime wins for live queries in reactive apps and agents. Also use for object storage, S3, buckets, serverless functions, function triggers, cron, AI gateway, LLM calls, realtime, logs, Loki, Grafana, observability, postgres, database, backend, Claimable Neon, neon.new, or a no-signup database.