[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M699KXTHG9FHK4X3JSZ4SV8J":3,"skill-same:01M699KXTHG9FHK4X3JSZ4SV8J":69},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M699KXTHG9FHK4X3JSZ4SV8J","winui-dev-workflow",null,"Create, build, run, and fix build errors in WinUI 3 apps (C# or C++) with WinApp CLI 0.7+: winapp new, winapp run, Native AOT, crash diagnosis. Use for a new WinUI app or a WinUI project that fails to build or crashes. Not for WPF, WinForms, or Electron apps that only reference the Windows App SDK.","microsoft\u002FwinappCli","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M699J7Q2FM9V32CFV0Q8VPF9",1381,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FwinappCli\u002Fblob\u002Fmain\u002Fplugins\u002Fwinui\u002Fagent-plugin\u002Fskills\u002Fwinui-dev-workflow\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"workflow","winui dev workflow","winui","dev","dev workflow","fix","new","errors","winapp cli","native","winforms","apps","diagnosis","app","project","only","cli","run","create","windows","electron","sdk","2026-11-10 10:12:30",false,"---\nname: winui-dev-workflow\ndescription: \"Create, build, run, and fix build errors in WinUI 3 apps (C# or C++) with WinApp CLI 0.7+: winapp new, winapp run, Native AOT, crash diagnosis. Use for a new WinUI app or a WinUI project that fails to build or crashes. Not for WPF, WinForms, or Electron apps that only reference the Windows App SDK.\"\n---\n\n**Scope: WinUI 3 apps only.** The Windows App SDK is not WinUI. A WPF, WinForms, Electron, or other app that references the Windows App SDK (for notifications, packaging, or other APIs) is not a WinUI app; keep its framework and don't apply this skill unless the task is to port it to WinUI 3. A WinUI 3 project has `\u003CUseWinUI>true\u003C\u002FUseWinUI>` or uses `Microsoft.UI.Xaml`.\n\nRequires **WinApp CLI 0.7+**.\n\n### Create or Open a Project\n\n**New app** — let WinApp CLI install\u002Fupdate the official templates and scaffold:\n```powershell\nwinapp new --name \u003CAppName> --template winui-mvvm --template-version latest --use-defaults\ncd \u003CAppName>\n```\nRun `winapp new --list` to discover the currently installed template short names. Do not install the template pack separately and do not create the output directory first.\n\n**Existing app** — read the `.csproj` to understand:\n- `\u003CTargetFramework>` (e.g., `net10.0-windows10.0.26100.0`)\n- `\u003CPackageReference>` versions (WindowsAppSDK, CommunityToolkit)\n- Project structure and established patterns\n\n### Add or Check the Per-App Analyzer\n\nAdd the latest stable analyzer to each app project; do not assume a template includes it:\n```powershell\ndotnet add .\\MyApp.csproj package Microsoft.Windows.SDK.BuildTools.WinUIAnalyzer\n```\n\nKeep `PrivateAssets=\"all\"` on the reference. It loads in normal CLI, IDE, and CI builds; WinApp CLI does not inject it. If the package is unavailable, continue and tell the user its checks for potential runtime issues did not run. Undo only an incomplete reference added by this attempt; do not remove existing references or hide other restore failures.\n\nFor other packages, prefer the latest stable unless the project has a version policy or the user requests a specific version. Before coding API assumptions, use `winapp find-api` scoped to the restored app with `--project-dir \u003Capp-project-dir>` (or `--project \u003Cname>` in a solution); see `winui-design`.\n\n### Build & Run (JIT Development)\n\n```powershell\nwinapp run . --detach --json\n```\nFor UI testing, see `winui-ui-testing`, which chooses the execution target itself.\n\nOrdinary `winapp run` uses the build\u002FJIT path, **even with `-c Release`**; it does not validate Native AOT. Use an explicit `.csproj` when project selection is ambiguous; see `winapp run --help` for options.\n\n**If build fails:** Read all errors, batch-fix them in one pass, then rerun the same command.\n\n### Native AOT Publish Runs\n\nFor intended AOT deployment, set `\u003CPublishAot>true\u003C\u002FPublishAot>` in the app project (it also enables analysis during development); for a one-off trial, pass `-p PublishAot=true`. `--aot` publishes rather than builds; choose an `--arch` runnable on this machine:\n```powershell\nwinapp run . --aot -c Release --arch \u003Cx64|arm64> --detach --json\nwinapp run . --aot -c Release --arch \u003Cx64|arm64> -p PublishAot=true --detach --json\n```\nFix IL\u002FCsWinRT warnings rather than suppressing them. See `winui-packaging`'s `references\u002Fsourcegen-patterns.md`.\n\n### Diagnosing Crashes\n\nRun attached with `--debug-output` and **invoke it with `mode: \"async\"`**, then read the same shell. On a WinUI crash, stowed-exception triage surfaces the real XAML error behind an opaque `0x8000FFFF` \u002F `E_FAIL`; add `--symbols` for richer native frames. The first crash downloads debugger components; set `WINAPP_DBGTOOLS_DIR` to an existing *Debugging Tools for Windows* install when offline. `--debug-output` cannot combine with `--json` or `--no-launch`.\n\n### Common Errors\n\n| Error | Fix |\n|-------|-----|\n| Developer Mode not enabled | Settings → System → For developers → On |\n| CS0234\u002FCS0246 missing type | Add `using` or `dotnet add package` |\n| NETSDK1136 platform required | Target a Windows TFM (for example `net10.0-windows10.0.26100.0`); use `-f \u003Cwindows-tfm>` when the project already multi-targets |\n| XLS0414 XAML type not found | Add `xmlns` declaration |\n| XDG0062 binding path missing | Check `x:Bind` property exists on ViewModel |\n| Dynamic bound value does not update | Check effective mode, including inherited `x:DefaultBindMode`; use `OneWay`\u002F`TwoWay` and change notifications where needed |\n| App silently exits | Use project-mode `winapp run`; don't bypass packaged activation by running the .exe directly |\n| App crashes with opaque `0x8000FFFF` \u002F `E_FAIL` | See **Diagnosing Crashes** |\n| XAML compiler crashes silently | Remove any `PresentationCore.dll` \u002F `System.Windows` references |\n| MSB3073 \u002F `XamlCompiler.exe ... exited with code 1`, no `.xaml` named | Old WindowsAppSDK XAML-compiler bug — update `Microsoft.WindowsAppSDK` NuGet to latest (≥ 2.1.3, or ≥ 1.8 on the 1.x line) |\n| 0x80073CF6 package install failed | Check the manifest publisher and Developer Mode; apps from `winapp new` need no separate `winapp init` |\n| 0x80073CF9 \u002F \"Failed to reach state Staged\" on a deeply nested project | For a packaged app, rerun with `--output-appx-directory \"$env:LOCALAPPDATA\\winapp-layout\\\u003Capp>-\u003Cconfig>-\u003Carch>\"`, or move the repo closer to the drive root. Keep the directory unique per configuration and architecture — a registered development package holds a live reference to it, so Debug and Release must not share one — and empty it before reuse so payload files dropped since the last build do not linger |\n| 0x8007000B bad image format | Wrong platform target — use x64 or ARM64, not AnyCPU |\n\n### Prerequisites\n\n| Requirement | Required for this workflow |\n|-------------|----------------------------|\n| Windows | Windows 10 v1903+ and the app's OS requirements |\n| Developer Mode | Enabled for development deployment |\n| .NET SDK | 8.0.100 minimum **plus the SDK required by the app's TFM** (e.g., .NET 10 for `net10.0-windows…`) |\n| WinApp CLI | 0.7+ |\n| Native AOT only | MSVC C++ build tools (Visual Studio or Build Tools, **Desktop development with C++** workload, target-architecture tools); not needed for normal builds |\n\nIf WinApp CLI is missing or older than 0.7, install or upgrade it using `winui-setup` without asking (it needs no admin rights) and tell the user. Ask before installing anything that needs admin rights — the .NET SDK, Developer Mode, or the [Native AOT toolchain](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fdotnet\u002Fcore\u002Fdeploying\u002Fnative-aot\u002F); do not work around them.\n\n### Critical Rules\n\n- Keep **packaged** as the default and use project-mode `winapp run` for activation.\n- Only for an **explicitly requested unpackaged\u002Fdebug experiment**, set `WindowsPackageType=None`; package-identity-dependent APIs may fail and runtime requirements still apply. Do not use this as a silent launch workaround. Preserve the manifest and restore the original packaged setting after the experiment.\n- Do not delete `Package.appxmanifest`.\n- ❌ NEVER use `AnyCPU` — always x64 or ARM64\n\n### References\n\n- `winui-packaging` — release packaging directly from the project; no development registration required.\n","**Scope: WinUI 3 apps only.** The Windows App SDK is not WinUI. A WPF, WinForms, Electron, or other app that references the Windows App SDK (for notifications, packaging, or other APIs) is not a WinUI app; keep its framework and don't apply this skill unless the task is to port it to WinUI 3. A WinUI 3 project has `\u003CUseWinUI>true\u003C\u002FUseWinUI>` or uses `Microsoft.UI.Xaml`.\n\nRequires **WinApp CLI 0.7+**.\n\n### Create or Open a Project\n\n**New app** — let WinApp CLI install\u002Fupdate the official templates and scaffold:\n```powershell\nwinapp new --name \u003CAppName> --template winui-mvvm --template-version latest --use-defaults\ncd \u003CAppName>\n```\nRun `winapp new --list` to discover the currently installed template short names. Do not install the template pack separately and do not create the output directory first.\n\n**Existing app** — read the `.csproj` to understand:\n- `\u003CTargetFramework>` (e.g., `net10.0-windows10.0.26100.0`)\n- `\u003CPackageReference>` versions (WindowsAppSDK, CommunityToolkit)\n- Project structure and established patterns\n\n### Add or Check the Per-App Analyzer\n\nAdd the latest stable analyzer to each app project; do not assume a template includes it:\n```powershell\ndotnet add .\\MyApp.csproj package Microsoft.Windows.SDK.BuildTools.WinUIAnalyzer\n```\n\nKeep `PrivateAssets=\"all\"` on the reference. It loads in normal CLI, IDE, and CI builds; WinApp CLI does not inject it. If the package is unavailable, continue and tell the user its checks for potential runtime issues did not run. Undo only an incomplete reference added by this attempt; do not remove existing references or hide other restore failures.\n\nFor other packages, prefer the latest stable unless the project has a version policy or the user requests a specific version. Before coding API assumptions, use `winapp find-api` scoped to the restored app with `--project-dir \u003Capp-project-dir>` (or `--project \u003Cname>` in a solution); see `winui-design`.\n\n### Build & Run (JIT Development)\n\n```powershell\nwinapp run . --detach --json\n```\nFor UI testing, see `winui-ui-testing`, which chooses the execution target itself.\n\nOrdinary `winapp run` uses the build\u002FJIT path, **even with `-c Release`**; it does not validate Native AOT. Use an explicit `.csproj` when project selection is ambiguous; see `winapp run --help` for options.\n\n**If build fails:** Read all errors, batch-fix them in one pass, then rerun the same command.\n\n### Native AOT Publish Runs\n\nFor intended AOT deployment, set `\u003CPublishAot>true\u003C\u002FPublishAot>` in the app project (it also enables analysis during development); for a one-off trial, pass `-p PublishAot=true`. `--aot` publishes rather than builds; choose an `--arch` runnable on this machine:\n```powershell\nwinapp run . --aot -c Release --arch \u003Cx64|arm64> --detach --json\nwinapp run . --aot -c Release --arch \u003Cx64|arm64> -p PublishAot=true --detach --json\n```\nFix IL\u002FCsWinRT warnings rather than suppressing them. See `winui-packaging`'s `references\u002Fsourcegen-patterns.md`.\n\n### Diagnosing Crashes\n\nRun attached with `--debug-output` and **invoke it with `mode: \"async\"`**, then read the same shell. On a WinUI crash, stowed-exception triage surfaces the real XAML error behind an opaque `0x8000FFFF` \u002F `E_FAIL`; add `--symbols` for richer native frames. The first crash downloads debugger components; set `WINAPP_DBGTOOLS_DIR` to an existing *Debugging Tools for Windows* install when offline. `--debug-output` cannot combine with `--json` or `--no-launch`.\n\n### Common Errors\n\n| Error | Fix |\n|-------|-----|\n| Developer Mode not enabled | Settings → System → For developers → On |\n| CS0234\u002FCS0246 missing type | Add `using` or `dotnet add package` |\n| NETSDK1136 platform required | Target a Windows TFM (for example `net10.0-windows10.0.26100.0`); use `-f \u003Cwindows-tfm>` when the project already multi-targets |\n| XLS0414 XAML type not found | Add `xmlns` declaration |\n| XDG0062 binding path missing | Check `x:Bind` property exists on ViewModel |\n| Dynamic bound value does not update | Check effective mode, including inherited `x:DefaultBindMode`; use `OneWay`\u002F`TwoWay` and change notifications where needed |\n| App silently exits | Use project-mode `winapp run`; don't bypass packaged activation by running the .exe directly |\n| App crashes with opaque `0x8000FFFF` \u002F `E_FAIL` | See **Diagnosing Crashes** |\n| XAML compiler crashes silently | Remove any `PresentationCore.dll` \u002F `System.Windows` references |\n| MSB3073 \u002F `XamlCompiler.exe ... exited with code 1`, no `.xaml` named | Old WindowsAppSDK XAML-compiler bug — update `Microsoft.WindowsAppSDK` NuGet to latest (≥ 2.1.3, or ≥ 1.8 on the 1.x line) |\n| 0x80073CF6 package install failed | Check the manifest publisher and Developer Mode; apps from `winapp new` need no separate `winapp init` |\n| 0x80073CF9 \u002F \"Failed to reach state Staged\" on a deeply nested project | For a packaged app, rerun with `--output-appx-directory \"$env:LOCALAPPDATA\\winapp-layout\\\u003Capp>-\u003Cconfig>-\u003Carch>\"`, or move the repo closer to the drive root. Keep the directory unique per configuration and architecture — a registered development package holds a live reference to it, so Debug and Release must not share one — and empty it before reuse so payload files dropped since the last build do not linger |\n| 0x8007000B bad image format | Wrong platform target — use x64 or ARM64, not AnyCPU |\n\n### Prerequisites\n\n| Requirement | Required for this workflow |\n|-------------|----------------------------|\n| Windows | Windows 10 v1903+ and the app's OS requirements |\n| Developer Mode | Enabled for development deployment |\n| .NET SDK | 8.0.100 minimum **plus the SDK required by the app's TFM** (e.g., .NET 10 for `net10.0-windows…`) |\n| WinApp CLI | 0.7+ |\n| Native AOT only | MSVC C++ build tools (Visual Studio or Build Tools, **Desktop development with C++** workload, target-architecture tools); not needed for normal builds |\n\nIf WinApp CLI is missing or older than 0.7, install or upgrade it using `winui-setup` without asking (it needs no admin rights) and tell the user. Ask before installing anything that needs admin rights — the .NET SDK, Developer Mode, or the [Native AOT toolchain](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fdotnet\u002Fcore\u002Fdeploying\u002Fnative-aot\u002F); do not work around them.\n\n### Critical Rules\n\n- Keep **packaged** as the default and use project-mode `winapp run` for activation.\n- Only for an **explicitly requested unpackaged\u002Fdebug experiment**, set `WindowsPackageType=None`; package-identity-dependent APIs may fail and runtime requirements still apply. Do not use this as a silent launch workaround. Preserve the manifest and restore the original packaged setting after the experiment.\n- Do not delete `Package.appxmanifest`.\n- ❌ NEVER use `AnyCPU` — always x64 or ARM64\n\n### References\n\n- `winui-packaging` — release packaging directly from the project; no development registration required.\n",{"name":5,"description":7},"main","1fe910277860e8dbb38bfbeef7e8bdb039d6ee41","plugins\u002Fwinui\u002Fagent-plugin\u002Fskills\u002Fwinui-dev-workflow",96,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FwinappCli","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-14 07:14:37",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add microsoft\u002FwinappCli --skill winui-dev-workflow",{"tool":61,"command":62},"bunx","bunx skills add microsoft\u002FwinappCli --skill winui-dev-workflow",{"tool":64,"command":65},"pnpm","pnpm dlx skills add microsoft\u002FwinappCli --skill winui-dev-workflow","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FwinappCli\u002Fblob\u002Fmain\u002Fplugins\u002Fwinui\u002Fagent-plugin\u002Fskills\u002Fwinui-dev-workflow\u002FSKILL.md",true,[],[70,93,124,145,163,192],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":41},"01M699M75MK9AADQV8PQQQ6NEV","winui-wpf-migration","Migrate or port a WPF app to WinUI 3: namespaces (System.Windows to Microsoft.UI.Xaml), control mapping (DataGrid, WrapPanel, TabControl), Dispatcher to DispatcherQueue, imaging, MVVM with CommunityToolkit.Mvvm, ThemeResource. Use when converting WPF code or fixing migration build errors.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FwinappCli\u002Fblob\u002Fmain\u002Fplugins\u002Fwinui\u002Fagent-plugin\u002Fskills\u002Fwinui-wpf-migration\u002FSKILL.md",[],[77,21,78,79,9,38,80,81,82,83,84,85,86,87,32,88,89,90,26,91,92],"winui wpf migration","wpf","migration","dispatcher","code","xaml","ui","migrate","system","use","mvvm","mapping","port","imaging","namespaces","when",{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":109,"publishedAt":41},"01M699M4W3GKSVVT9CRR1E3KSW","winui-ui-testing","Write and run automated UI tests for Windows desktop apps (WinUI 3, WPF, WinForms, Win32) with the winapp ui harness: one batch script, assertions, input, file pickers, dialogs, screenshots, locally or in Windows Sandbox. Use when asked for UI tests or to verify a feature end to end.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FwinappCli\u002Fblob\u002Fmain\u002Fplugins\u002Fwinui\u002Fagent-plugin\u002Fskills\u002Fwinui-ui-testing\u002FSKILL.md",[99,104],{"categoryNo":100,"categoryName":101,"taxonomyType":102,"taxonomyTypeDesc":103},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":105,"categoryName":106,"taxonomyType":107,"taxonomyTypeDesc":108},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[110,111,21,83,112,113,114,38,36,115,116,117,118,119,120,30,121,29,122,123,92],"testing","winui ui testing","ui testing","screenshots","sandbox","win32","harness","batch","write","feature","end","input","desktop apps","for",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":133,"publishedAt":41},"01M699M2KTEYJZBDW7JBHM94K0","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.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FwinappCli\u002Fblob\u002Fmain\u002Fplugins\u002Fwinui\u002Fagent-plugin\u002Fskills\u002Fwinui-setup\u002FSKILL.md",[130],{"categoryNo":131,"categoryName":132,"taxonomyType":107,"taxonomyTypeDesc":108},"01JBSEEDCAT000000000000030","开发工程师",[134,135,21,35,114,40,38,136,137,138,86,139,140,141,142,28,143,27,144,92],"winui setup","setup","SET","verify","install","up","repair","requirements","missing","toolchain","mode",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":154,"publishedAt":41},"01M699KZWEZ84A4J3291E6R65B","winui-packaging","MSIX packaging, signing, and Microsoft Store publishing for WinUI 3 apps with WinApp CLI 0.7+: project packaging, Native AOT, certificates, self-contained deployment, CI\u002FCD. Use when releasing or publishing a WinUI app. Not for WPF, WinForms, or Electron apps that only reference the Windows App SDK.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FwinappCli\u002Fblob\u002Fmain\u002Fplugins\u002Fwinui\u002Fagent-plugin\u002Fskills\u002Fwinui-packaging\u002FSKILL.md",[151],{"categoryNo":152,"categoryName":153,"taxonomyType":102,"taxonomyTypeDesc":103},"01JBSEEDCAT000000000000011","运维与部署",[155,21,156,35,40,39,9,157,38,158,159,160,34,161,33,32,30,29,28,162,27,123,92],"winui packaging","packaging","msix","windows app sdk","ci","certificates","self","CI\u002FCD",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":179,"publishedAt":41},"01M699KV0Q6NE5EET5EDBH33NM","winui-design","Read before writing or changing WinUI 3 XAML: choosing controls, pages and navigation, layout, Fluent Design, theming, accessibility, x:Bind, real samples, and checking that APIs exist with winapp find-api. Not for WPF or WinForms UI, even if the app uses the Windows App SDK.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FwinappCli\u002Fblob\u002Fmain\u002Fplugins\u002Fwinui\u002Fagent-plugin\u002Fskills\u002Fwinui-design\u002FSKILL.md",[169,172,175,176],{"categoryNo":170,"categoryName":171,"taxonomyType":102,"taxonomyTypeDesc":103},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":173,"categoryName":174,"taxonomyType":102,"taxonomyTypeDesc":103},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":105,"categoryName":106,"taxonomyType":107,"taxonomyTypeDesc":108},{"categoryNo":177,"categoryName":178,"taxonomyType":107,"taxonomyTypeDesc":108},"01JBSEEDCAT000000000000036","内容创作者",[180,181,21,182,40,183,184,38,158,78,82,83,185,186,187,188,189,32,29,190,123,191],"design","winui design","writing","accessibility","fluent","api","read","layout","pages","bind","controls","fluent design",{"skillNo":193,"name":194,"nameZh":6,"description":195,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":196,"categories":197,"keywords":202,"publishedAt":41},"01M699KR63WV521C7JT7FQMADN","winui-code-review","Review WinUI 3 code or changes for quality: MVVM, x:Bind correctness, accessibility, theming, security, performance, and WinUI analyzer findings. Use when asked to review or audit a WinUI app or its pending changes, or before committing. Catches issues the compiler and UI tests miss.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FwinappCli\u002Fblob\u002Fmain\u002Fplugins\u002Fwinui\u002Fagent-plugin\u002Fskills\u002Fwinui-code-review\u002FSKILL.md",[198,201],{"categoryNo":199,"categoryName":200,"taxonomyType":102,"taxonomyTypeDesc":103},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":131,"categoryName":132,"taxonomyType":107,"taxonomyTypeDesc":108},[203,204,205,81,21,206,207,183,208,209,210,86,87,211,189,32,212,213,123,214,215,92],"code review","review","winui code review","security","performance","issues","winui app","compiler","tests","theming","correctness","changes","pending"]