[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M699JYYNBF1RFMNV4W8XCCZT":3,"skill-same:01M699JYYNBF1RFMNV4W8XCCZT":162},{"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":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":51,"ownerDescription":52,"updatedAt":53,"install":54,"resources":67},"01M699JYYNBF1RFMNV4W8XCCZT","winapp-identity",null,"Give a desktop app (WPF, WinForms, Electron, C++, Rust) package identity so identity-only Windows APIs work: push notifications, background tasks, share target, startup tasks. Use when adding such a feature, running or debugging with identity, or running parallel worktrees side by side.","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\u002Fwinapp\u002Fskills\u002Fwinapp-identity\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39],"identity","winapp identity","work","running","when","parallel worktrees","winforms","app","feature","c++","desktop app","worktrees","only","rust","parallel","notifications","push","tasks","debugging","windows","electron","2026-11-10 10:12:30",false,"---\nname: winapp-identity\ndescription: \"Give a desktop app (WPF, WinForms, Electron, C++, Rust) package identity so identity-only Windows APIs work: push notifications, background tasks, share target, startup tasks. Use when adding such a feature, running or debugging with identity, or running parallel worktrees side by side.\"\n---\n\n**If you can't run `winapp` yourself** (no shell, or the command is denied), give the user the exact `winapp` command(s) for their project instead of only describing the steps.\n\n## When to use\n\nUse this skill when:\n- **Running packaged worktrees side by side** — opt into `winapp run --unique-identity`\n- **The exe is separate from your app code** — e.g., Electron apps where `electron.exe` is in `node_modules`, not your build output\n- **Testing sparse package behavior** specifically — `AllowExternalContent`, `TrustedLaunch`, etc.\n- **Registering identity without copying files** — `create-debug-identity` leaves the exe in place\n\n> **Prefer `winapp run` for most frameworks.** If your exe is inside your build output folder (.NET, C++, Rust, Flutter, Tauri), use `winapp run \u003Cbuild-output>` instead — it registers a full loose layout package and launches the app, simulating an MSIX install. Use `create-debug-identity` only when `winapp run` doesn't fit your scenario.\n\n## Parallel packaged worktrees\n\n```powershell\nwinapp run . --unique-identity --no-launch --json\nwinapp unregister .\n```\n\nUse this only when the user wants copies of an app to stay registered side by side.\nPass the same input for every run, and the same project, `.cs`, or folder for cleanup (for a solution, the project it ran). Read names from the returned\n`Identity` and aliases instead of guessing them. Never resolve a registration conflict\nby removing another checkout's package.\n\nCheck the [unique identity reference](https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FWinAppCli\u002Fblob\u002Fmain\u002Fdocs\u002Fusage.md#unique-identity-for-parallel-checkouts) for\nsupported packages and limits. For guest execution, also use `winapp-sandbox`.\n\n## Prerequisites\n\nFor the sparse `create-debug-identity` workflow below:\n\n1. **`Package.appxmanifest`** in your project — from `winapp init` or `winapp manifest generate`\n2. **Built executable** — the `.exe` your app runs from\n\n## What is package identity?\n\nWindows package identity enables your app to use restricted APIs and OS integration features:\n- **Push notifications** (WNS)\n- **Background tasks**\n- **Share target** \u002F share source\n- **App startup tasks**\n- **Taskbar pinning**\n- **Windows AI APIs** (Phi Silica, OCR, etc.)\n- **File type associations** registered properly in Settings\n\nA standard `.exe` (from `dotnet build`, `cmake`, etc.) does **not** have identity. `create-debug-identity` registers a *sparse package* with Windows — the exe stays in its original location and Windows associates identity with it via `Add-AppxPackage -ExternalLocation`. This is different from `winapp run`, which copies files into a loose layout package.\n\n## Usage\n\n### Basic usage\n\n```powershell\n# Register sparse package for your exe (manifest auto-detected from current dir)\nwinapp create-debug-identity .\u002Fbin\u002FRelease\u002Fmyapp.exe\n\n# Specify manifest location\nwinapp create-debug-identity .\u002Fbin\u002FRelease\u002Fmyapp.exe --manifest .\u002FPackage.appxmanifest\n```\n\n### Keep the original package identity\n\n```powershell\n# By default, '.debug' is appended to the package name to avoid conflicts with\n# an installed MSIX version. Use --keep-identity to keep the manifest identity as-is.\nwinapp create-debug-identity .\u002Fmyapp.exe --keep-identity\n```\n\n### Generate without installing\n\n```powershell\n# Create the sparse package layout but don't register it with Windows\nwinapp create-debug-identity .\u002Fmyapp.exe --no-install\n```\n\n## What the command does\n\n1. **Reads `Package.appxmanifest`** — extracts identity, capabilities, and assets\n2. **Creates a sparse package layout** in a temp directory\n3. **Appends `.debug`** to the package name (unless `--keep-identity`) to avoid conflicts\n4. **Registers with Windows** via `Add-AppxPackage -ExternalLocation` — makes your exe \"identity-aware\"\n\nAfter running, launch your exe normally — Windows will recognize it as having package identity.\n\n## Recommended workflow\n\n1. **Setup** — `winapp init . --use-defaults` (creates `Package.appxmanifest`)\n2. **Generate development certificate** — `winapp cert generate`\n3. **Build** your app\n4. **Register identity** — `winapp create-debug-identity .\u002Fbin\u002Fmyapp.exe`\n5. **Run** your app — identity-requiring APIs now work\n6. **Re-run step 4** whenever you change `Package.appxmanifest` or `Assets\u002F`\n\n## Tips\n\n- You must re-run `create-debug-identity` (or `winapp run`) after any changes to `Package.appxmanifest` or image assets; both read them only when they register the package\n- The debug identity persists across reboots until explicitly removed\n- To remove this sparse registration: `winapp unregister --manifest .\\Package.appxmanifest`\n- If you have both a debug identity and an installed MSIX, they may conflict — use `--keep-identity` carefully\n- For Electron apps, use `npx winapp node add-electron-debug-identity` instead (handles Electron-specific paths)\n\n## Debugging: `winapp run` vs `create-debug-identity`\n\n| | `winapp run` | `create-debug-identity` |\n|---|---|---|\n| **What it registers** | Full loose layout package (entire folder) | Sparse package (single exe) |\n| **How the app launches** | Launched by winapp (AUMID activation or execution alias) | You launch the exe yourself (command line, IDE, etc.) |\n| **Simulates MSIX install** | Yes — closest to production behavior | No — sparse identity only |\n| **Files stay in place** | Copied to an AppX layout directory | Yes — exe stays at its original path |\n| **Debugger-friendly** | Attach to PID after launch, or use `--no-launch` then launch via alias | Launch directly from your IDE's debugger — the exe has identity regardless |\n| **Console app support** | Launched through an execution alias automatically, so stdin\u002Fstdout stay in this terminal | Run exe directly in terminal |\n| **Best for** | Most frameworks (.NET, C++, Rust, Flutter, Tauri) | Electron, or when you need full IDE debugger control (F5 startup debugging) |\n\n### When to use which\n\n**Default to `winapp run`** for most development — normal identity mode simulates a real MSIX install with full identity, capabilities, and file associations:\n\n```powershell\nwinapp run .\\build\\output          # GUI and console apps alike; a console app\n                                   # gets an execution alias automatically\n```\n\n**Use `create-debug-identity` when:**\n- **Debugging startup code** — your IDE launches + debugs the exe directly; identity is attached from the first instruction\n- **Exe is separate from build output** — e.g., Electron where `electron.exe` is in `node_modules\u002F`\n- **Testing sparse package behavior** — `AllowExternalContent`, `TrustedLaunch`\n\n```powershell\nwinapp create-debug-identity .\\bin\\Debug\\myapp.exe\n# Now launch any way you like — F5, terminal, script — the exe has identity\n```\n\n### Common debugging scenarios\n\n| Scenario | Command | Notes |\n|----------|---------|-------|\n| **Just run with identity** | `winapp run .\\build\\Debug` | Simplest workflow; a console app gets an execution alias automatically |\n| **Attach debugger to running app** | `winapp run .\\build\\Debug`, then attach to PID | Misses startup code |\n| **Register identity, launch via AUMID** | `winapp run .\\build\\Debug --no-launch` | Launch with `start shell:AppsFolder\\\u003CAUMID>` or the execution alias (not the exe directly) |\n| **F5 startup debugging** | `winapp create-debug-identity .\\bin\\myapp.exe` | IDE controls process from first instruction; best for debugging activation\u002Fstartup code |\n| **Capture debug output** | `winapp run .\\build\\Debug --debug-output` | Captures `OutputDebugString`; on crash, writes minidump and analyzes managed exceptions automatically. **Blocks other debuggers** (one debugger per process) |\n| **Run and auto-clean** | `winapp run .\\build\\Debug --unregister-on-exit` | Unregisters the dev package after the app exits |\n| **Launch and detach (CI)** | `winapp run .\\build\\Debug --detach` | Returns immediately after launch; use `--json` to get PID for scripting |\n| **Clean up this app's registration** | `winapp unregister .` | Pass the same project, `.cs`, or folder as `run` (for a solution, the project it ran); works with or without `--unique-identity` |\n\n> **Using Visual Studio with a packaging project?** VS already handles identity, AUMID activation, and debugger attachment from F5. These workflows are most useful for VS Code, terminal-based development, and frameworks VS doesn't natively package (Rust, Flutter, Tauri, Electron, C++).\n\nFor full details including IDE setup examples, see the [Debugging Guide](https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FWinAppCli\u002Fblob\u002Fmain\u002Fdocs\u002Fdebugging.md).\n\n## Production sparse packaging (`init --sparse` \u002F `pack` \u002F `embed-identity`)\n\n`create-debug-identity` is for **developer-time debugging** (requires Developer Mode, registers a raw manifest). For **production** — shipping identity to an app distributed by an existing installer (Inno Setup, WiX, NSIS) — use the sparse packaging workflow, which produces a signed identity-only `.msix`:\n\n```powershell\n# 1. Create the sparse identity manifest for your exe (skips SDK install)\nwinapp init --exe .\u002Fbin\u002FRelease\u002FMyApp.exe --sparse --use-defaults\n\n# 2. Build and sign the identity-only .msix (just the manifest, no binaries)\nwinapp pack .\u002Fsparse\u002Fappxmanifest.xml --cert .\u002Fdevcert.pfx\n\n# 3. Embed the \u003Cmsix> identity element into the exe's fusion manifest\nwinapp embed-identity .\u002Fbin\u002FRelease\u002FMyApp.exe\n```\n\nThen your installer registers the package against the install directory:\n`Add-AppxPackage -Path MyApp.identity.msix -ExternalLocation \u003Cinstall-dir>`.\n\nAssets are resolved from the external (install) location at runtime, **not** bundled into the `.msix`. `winapp embed-identity` also supports an XML mode (`winapp embed-identity .\u002Fapp.manifest`) for updating a checked-in side-by-side manifest. See the [Sparse Packaging Guide](https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FWinAppCli\u002Fblob\u002Fmain\u002Fdocs\u002Fguides\u002Fsparse.md) and the [sparse-app sample](https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FWinAppCli\u002Ftree\u002Fmain\u002Fsamples\u002Fsparse-app).\n\n## Related skills\n- Need a manifest? See `winapp-manifest` to generate `Package.appxmanifest`\n- Need a certificate? See `winapp-signing` — a trusted cert is required for identity registration\n- Ready for full MSIX distribution? See `winapp-package` to create an installer\n- Having issues? See `winapp-troubleshoot` for common error solutions\n\n## Troubleshooting\n| Error | Cause | Solution |\n|-------|-------|----------|\n| \"Package.appxmanifest not found\" | No manifest in current directory | Run `winapp init` or `winapp manifest generate`, or pass `--manifest` |\n| \"Failed to add package identity\" | Previous registration stale or cert untrusted | Run `winapp unregister` to remove stale packages, then `winapp cert install .\u002Fdevcert.pfx` (admin) |\n| \"Access denied\" | Cert not trusted or permission issue | Run `winapp cert install .\u002Fdevcert.pfx` as admin |\n| APIs still fail after registration | App launched before registration completed | Close app, re-run `create-debug-identity`, then relaunch |\n\n## CLI reference\n\nRun `winapp \u003Ccommand> --help` for current command options, or `winapp --cli-schema` for the complete machine-readable command schema.\n","**If you can't run `winapp` yourself** (no shell, or the command is denied), give the user the exact `winapp` command(s) for their project instead of only describing the steps.\n\n## When to use\n\nUse this skill when:\n- **Running packaged worktrees side by side** — opt into `winapp run --unique-identity`\n- **The exe is separate from your app code** — e.g., Electron apps where `electron.exe` is in `node_modules`, not your build output\n- **Testing sparse package behavior** specifically — `AllowExternalContent`, `TrustedLaunch`, etc.\n- **Registering identity without copying files** — `create-debug-identity` leaves the exe in place\n\n> **Prefer `winapp run` for most frameworks.** If your exe is inside your build output folder (.NET, C++, Rust, Flutter, Tauri), use `winapp run \u003Cbuild-output>` instead — it registers a full loose layout package and launches the app, simulating an MSIX install. Use `create-debug-identity` only when `winapp run` doesn't fit your scenario.\n\n## Parallel packaged worktrees\n\n```powershell\nwinapp run . --unique-identity --no-launch --json\nwinapp unregister .\n```\n\nUse this only when the user wants copies of an app to stay registered side by side.\nPass the same input for every run, and the same project, `.cs`, or folder for cleanup (for a solution, the project it ran). Read names from the returned\n`Identity` and aliases instead of guessing them. Never resolve a registration conflict\nby removing another checkout's package.\n\nCheck the [unique identity reference](https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FWinAppCli\u002Fblob\u002Fmain\u002Fdocs\u002Fusage.md#unique-identity-for-parallel-checkouts) for\nsupported packages and limits. For guest execution, also use `winapp-sandbox`.\n\n## Prerequisites\n\nFor the sparse `create-debug-identity` workflow below:\n\n1. **`Package.appxmanifest`** in your project — from `winapp init` or `winapp manifest generate`\n2. **Built executable** — the `.exe` your app runs from\n\n## What is package identity?\n\nWindows package identity enables your app to use restricted APIs and OS integration features:\n- **Push notifications** (WNS)\n- **Background tasks**\n- **Share target** \u002F share source\n- **App startup tasks**\n- **Taskbar pinning**\n- **Windows AI APIs** (Phi Silica, OCR, etc.)\n- **File type associations** registered properly in Settings\n\nA standard `.exe` (from `dotnet build`, `cmake`, etc.) does **not** have identity. `create-debug-identity` registers a *sparse package* with Windows — the exe stays in its original location and Windows associates identity with it via `Add-AppxPackage -ExternalLocation`. This is different from `winapp run`, which copies files into a loose layout package.\n\n## Usage\n\n### Basic usage\n\n```powershell\n# Register sparse package for your exe (manifest auto-detected from current dir)\nwinapp create-debug-identity .\u002Fbin\u002FRelease\u002Fmyapp.exe\n\n# Specify manifest location\nwinapp create-debug-identity .\u002Fbin\u002FRelease\u002Fmyapp.exe --manifest .\u002FPackage.appxmanifest\n```\n\n### Keep the original package identity\n\n```powershell\n# By default, '.debug' is appended to the package name to avoid conflicts with\n# an installed MSIX version. Use --keep-identity to keep the manifest identity as-is.\nwinapp create-debug-identity .\u002Fmyapp.exe --keep-identity\n```\n\n### Generate without installing\n\n```powershell\n# Create the sparse package layout but don't register it with Windows\nwinapp create-debug-identity .\u002Fmyapp.exe --no-install\n```\n\n## What the command does\n\n1. **Reads `Package.appxmanifest`** — extracts identity, capabilities, and assets\n2. **Creates a sparse package layout** in a temp directory\n3. **Appends `.debug`** to the package name (unless `--keep-identity`) to avoid conflicts\n4. **Registers with Windows** via `Add-AppxPackage -ExternalLocation` — makes your exe \"identity-aware\"\n\nAfter running, launch your exe normally — Windows will recognize it as having package identity.\n\n## Recommended workflow\n\n1. **Setup** — `winapp init . --use-defaults` (creates `Package.appxmanifest`)\n2. **Generate development certificate** — `winapp cert generate`\n3. **Build** your app\n4. **Register identity** — `winapp create-debug-identity .\u002Fbin\u002Fmyapp.exe`\n5. **Run** your app — identity-requiring APIs now work\n6. **Re-run step 4** whenever you change `Package.appxmanifest` or `Assets\u002F`\n\n## Tips\n\n- You must re-run `create-debug-identity` (or `winapp run`) after any changes to `Package.appxmanifest` or image assets; both read them only when they register the package\n- The debug identity persists across reboots until explicitly removed\n- To remove this sparse registration: `winapp unregister --manifest .\\Package.appxmanifest`\n- If you have both a debug identity and an installed MSIX, they may conflict — use `--keep-identity` carefully\n- For Electron apps, use `npx winapp node add-electron-debug-identity` instead (handles Electron-specific paths)\n\n## Debugging: `winapp run` vs `create-debug-identity`\n\n| | `winapp run` | `create-debug-identity` |\n|---|---|---|\n| **What it registers** | Full loose layout package (entire folder) | Sparse package (single exe) |\n| **How the app launches** | Launched by winapp (AUMID activation or execution alias) | You launch the exe yourself (command line, IDE, etc.) |\n| **Simulates MSIX install** | Yes — closest to production behavior | No — sparse identity only |\n| **Files stay in place** | Copied to an AppX layout directory | Yes — exe stays at its original path |\n| **Debugger-friendly** | Attach to PID after launch, or use `--no-launch` then launch via alias | Launch directly from your IDE's debugger — the exe has identity regardless |\n| **Console app support** | Launched through an execution alias automatically, so stdin\u002Fstdout stay in this terminal | Run exe directly in terminal |\n| **Best for** | Most frameworks (.NET, C++, Rust, Flutter, Tauri) | Electron, or when you need full IDE debugger control (F5 startup debugging) |\n\n### When to use which\n\n**Default to `winapp run`** for most development — normal identity mode simulates a real MSIX install with full identity, capabilities, and file associations:\n\n```powershell\nwinapp run .\\build\\output          # GUI and console apps alike; a console app\n                                   # gets an execution alias automatically\n```\n\n**Use `create-debug-identity` when:**\n- **Debugging startup code** — your IDE launches + debugs the exe directly; identity is attached from the first instruction\n- **Exe is separate from build output** — e.g., Electron where `electron.exe` is in `node_modules\u002F`\n- **Testing sparse package behavior** — `AllowExternalContent`, `TrustedLaunch`\n\n```powershell\nwinapp create-debug-identity .\\bin\\Debug\\myapp.exe\n# Now launch any way you like — F5, terminal, script — the exe has identity\n```\n\n### Common debugging scenarios\n\n| Scenario | Command | Notes |\n|----------|---------|-------|\n| **Just run with identity** | `winapp run .\\build\\Debug` | Simplest workflow; a console app gets an execution alias automatically |\n| **Attach debugger to running app** | `winapp run .\\build\\Debug`, then attach to PID | Misses startup code |\n| **Register identity, launch via AUMID** | `winapp run .\\build\\Debug --no-launch` | Launch with `start shell:AppsFolder\\\u003CAUMID>` or the execution alias (not the exe directly) |\n| **F5 startup debugging** | `winapp create-debug-identity .\\bin\\myapp.exe` | IDE controls process from first instruction; best for debugging activation\u002Fstartup code |\n| **Capture debug output** | `winapp run .\\build\\Debug --debug-output` | Captures `OutputDebugString`; on crash, writes minidump and analyzes managed exceptions automatically. **Blocks other debuggers** (one debugger per process) |\n| **Run and auto-clean** | `winapp run .\\build\\Debug --unregister-on-exit` | Unregisters the dev package after the app exits |\n| **Launch and detach (CI)** | `winapp run .\\build\\Debug --detach` | Returns immediately after launch; use `--json` to get PID for scripting |\n| **Clean up this app's registration** | `winapp unregister .` | Pass the same project, `.cs`, or folder as `run` (for a solution, the project it ran); works with or without `--unique-identity` |\n\n> **Using Visual Studio with a packaging project?** VS already handles identity, AUMID activation, and debugger attachment from F5. These workflows are most useful for VS Code, terminal-based development, and frameworks VS doesn't natively package (Rust, Flutter, Tauri, Electron, C++).\n\nFor full details including IDE setup examples, see the [Debugging Guide](https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FWinAppCli\u002Fblob\u002Fmain\u002Fdocs\u002Fdebugging.md).\n\n## Production sparse packaging (`init --sparse` \u002F `pack` \u002F `embed-identity`)\n\n`create-debug-identity` is for **developer-time debugging** (requires Developer Mode, registers a raw manifest). For **production** — shipping identity to an app distributed by an existing installer (Inno Setup, WiX, NSIS) — use the sparse packaging workflow, which produces a signed identity-only `.msix`:\n\n```powershell\n# 1. Create the sparse identity manifest for your exe (skips SDK install)\nwinapp init --exe .\u002Fbin\u002FRelease\u002FMyApp.exe --sparse --use-defaults\n\n# 2. Build and sign the identity-only .msix (just the manifest, no binaries)\nwinapp pack .\u002Fsparse\u002Fappxmanifest.xml --cert .\u002Fdevcert.pfx\n\n# 3. Embed the \u003Cmsix> identity element into the exe's fusion manifest\nwinapp embed-identity .\u002Fbin\u002FRelease\u002FMyApp.exe\n```\n\nThen your installer registers the package against the install directory:\n`Add-AppxPackage -Path MyApp.identity.msix -ExternalLocation \u003Cinstall-dir>`.\n\nAssets are resolved from the external (install) location at runtime, **not** bundled into the `.msix`. `winapp embed-identity` also supports an XML mode (`winapp embed-identity .\u002Fapp.manifest`) for updating a checked-in side-by-side manifest. See the [Sparse Packaging Guide](https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FWinAppCli\u002Fblob\u002Fmain\u002Fdocs\u002Fguides\u002Fsparse.md) and the [sparse-app sample](https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FWinAppCli\u002Ftree\u002Fmain\u002Fsamples\u002Fsparse-app).\n\n## Related skills\n- Need a manifest? See `winapp-manifest` to generate `Package.appxmanifest`\n- Need a certificate? See `winapp-signing` — a trusted cert is required for identity registration\n- Ready for full MSIX distribution? See `winapp-package` to create an installer\n- Having issues? See `winapp-troubleshoot` for common error solutions\n\n## Troubleshooting\n| Error | Cause | Solution |\n|-------|-------|----------|\n| \"Package.appxmanifest not found\" | No manifest in current directory | Run `winapp init` or `winapp manifest generate`, or pass `--manifest` |\n| \"Failed to add package identity\" | Previous registration stale or cert untrusted | Run `winapp unregister` to remove stale packages, then `winapp cert install .\u002Fdevcert.pfx` (admin) |\n| \"Access denied\" | Cert not trusted or permission issue | Run `winapp cert install .\u002Fdevcert.pfx` as admin |\n| APIs still fail after registration | App launched before registration completed | Close app, re-run `create-debug-identity`, then relaunch |\n\n## CLI reference\n\nRun `winapp \u003Ccommand> --help` for current command options, or `winapp --cli-schema` for the complete machine-readable command schema.\n",{"name":5,"description":7},"main","1fe910277860e8dbb38bfbeef7e8bdb039d6ee41","plugins\u002Fwinapp\u002Fskills\u002Fwinapp-identity",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":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add microsoft\u002FwinappCli --skill winapp-identity",{"tool":60,"command":61},"bunx","bunx skills add microsoft\u002FwinappCli --skill winapp-identity",{"tool":63,"command":64},"pnpm","pnpm dlx skills add microsoft\u002FwinappCli --skill winapp-identity","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FwinappCli\u002Fblob\u002Fmain\u002Fplugins\u002Fwinapp\u002Fskills\u002Fwinapp-identity\u002FSKILL.md",true,[68,74,80,84,88,92,96,100,104,108,114,118,122,126,130,134,138,142,146,150,154,158],{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},".claude-plugin\u002Fmarketplace.json","REFERENCE","参考文档",2631,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Farticle-to-prototype-cskill\u002F.claude-plugin\u002Fmarketplace.json",{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"assets\u002Fexamples\u002Fsample_input.md","ASSET","资产文件",1154,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Farticle-to-prototype-cskill\u002Fassets\u002Fexamples\u002Fsample_input.md",{"path":81,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":82,"sourceHtmlUrl":83},"assets\u002Fprompts\u002Fanalysis_prompt.txt",835,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Farticle-to-prototype-cskill\u002Fassets\u002Fprompts\u002Fanalysis_prompt.txt",{"path":85,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":86,"sourceHtmlUrl":87},"DECISIONS.md",12397,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Farticle-to-prototype-cskill\u002FDECISIONS.md",{"path":89,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":90,"sourceHtmlUrl":91},"README.md",8768,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Farticle-to-prototype-cskill\u002FREADME.md",{"path":93,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":94,"sourceHtmlUrl":95},"references\u002Fanalysis-methodology.md",2304,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Farticle-to-prototype-cskill\u002Freferences\u002Fanalysis-methodology.md",{"path":97,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":98,"sourceHtmlUrl":99},"references\u002Fextraction-patterns.md",3188,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Farticle-to-prototype-cskill\u002Freferences\u002Fextraction-patterns.md",{"path":101,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":102,"sourceHtmlUrl":103},"references\u002Fgeneration-rules.md",3486,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Farticle-to-prototype-cskill\u002Freferences\u002Fgeneration-rules.md",{"path":105,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":106,"sourceHtmlUrl":107},"requirements.txt",335,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Farticle-to-prototype-cskill\u002Frequirements.txt",{"path":109,"resourceType":110,"resourceTypeDesc":111,"sizeBytes":112,"sourceHtmlUrl":113},"scripts\u002F__init__.py","SCRIPT","脚本",172,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Farticle-to-prototype-cskill\u002Fscripts\u002F__init__.py",{"path":115,"resourceType":110,"resourceTypeDesc":111,"sizeBytes":116,"sourceHtmlUrl":117},"scripts\u002Fanalyzers\u002F__init__.py",519,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Farticle-to-prototype-cskill\u002Fscripts\u002Fanalyzers\u002F__init__.py",{"path":119,"resourceType":110,"resourceTypeDesc":111,"sizeBytes":120,"sourceHtmlUrl":121},"scripts\u002Fanalyzers\u002Fcode_detector.py",3926,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Farticle-to-prototype-cskill\u002Fscripts\u002Fanalyzers\u002Fcode_detector.py",{"path":123,"resourceType":110,"resourceTypeDesc":111,"sizeBytes":124,"sourceHtmlUrl":125},"scripts\u002Fanalyzers\u002Fcontent_analyzer.py",14354,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Farticle-to-prototype-cskill\u002Fscripts\u002Fanalyzers\u002Fcontent_analyzer.py",{"path":127,"resourceType":110,"resourceTypeDesc":111,"sizeBytes":128,"sourceHtmlUrl":129},"scripts\u002Fextractors\u002F__init__.py",359,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Farticle-to-prototype-cskill\u002Fscripts\u002Fextractors\u002F__init__.py",{"path":131,"resourceType":110,"resourceTypeDesc":111,"sizeBytes":132,"sourceHtmlUrl":133},"scripts\u002Fextractors\u002Fmarkdown_extractor.py",6272,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Farticle-to-prototype-cskill\u002Fscripts\u002Fextractors\u002Fmarkdown_extractor.py",{"path":135,"resourceType":110,"resourceTypeDesc":111,"sizeBytes":136,"sourceHtmlUrl":137},"scripts\u002Fextractors\u002Fnotebook_extractor.py",8285,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Farticle-to-prototype-cskill\u002Fscripts\u002Fextractors\u002Fnotebook_extractor.py",{"path":139,"resourceType":110,"resourceTypeDesc":111,"sizeBytes":140,"sourceHtmlUrl":141},"scripts\u002Fextractors\u002Fpdf_extractor.py",16216,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Farticle-to-prototype-cskill\u002Fscripts\u002Fextractors\u002Fpdf_extractor.py",{"path":143,"resourceType":110,"resourceTypeDesc":111,"sizeBytes":144,"sourceHtmlUrl":145},"scripts\u002Fextractors\u002Fweb_extractor.py",16745,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Farticle-to-prototype-cskill\u002Fscripts\u002Fextractors\u002Fweb_extractor.py",{"path":147,"resourceType":110,"resourceTypeDesc":111,"sizeBytes":148,"sourceHtmlUrl":149},"scripts\u002Fgenerators\u002F__init__.py",379,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Farticle-to-prototype-cskill\u002Fscripts\u002Fgenerators\u002F__init__.py",{"path":151,"resourceType":110,"resourceTypeDesc":111,"sizeBytes":152,"sourceHtmlUrl":153},"scripts\u002Fgenerators\u002Flanguage_selector.py",4572,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Farticle-to-prototype-cskill\u002Fscripts\u002Fgenerators\u002Flanguage_selector.py",{"path":155,"resourceType":110,"resourceTypeDesc":111,"sizeBytes":156,"sourceHtmlUrl":157},"scripts\u002Fgenerators\u002Fprototype_generator.py",14388,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Farticle-to-prototype-cskill\u002Fscripts\u002Fgenerators\u002Fprototype_generator.py",{"path":159,"resourceType":110,"resourceTypeDesc":111,"sizeBytes":160,"sourceHtmlUrl":161},"scripts\u002Fmain.py",7386,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Farticle-to-prototype-cskill\u002Fscripts\u002Fmain.py",[163,187,219,244,263,278],{"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":169,"publishedAt":40},"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",[],[170,171,172,173,9,38,174,175,176,177,178,179,180,181,26,182,183,184,185,186,23],"winui wpf migration","winui","wpf","migration","dispatcher","code","xaml","ui","migrate","system","use","mvvm","mapping","port","imaging","errors","namespaces",{"skillNo":188,"name":189,"nameZh":6,"description":190,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":191,"categories":192,"keywords":203,"publishedAt":40},"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",[193,198],{"categoryNo":194,"categoryName":195,"taxonomyType":196,"taxonomyTypeDesc":197},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":199,"categoryName":200,"taxonomyType":201,"taxonomyTypeDesc":202},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[204,205,171,177,206,207,208,38,209,210,211,212,213,27,214,215,216,25,217,218,23],"testing","winui ui testing","ui testing","screenshots","sandbox","run","win32","harness","batch","write","end","apps","input","desktop apps","for",{"skillNo":220,"name":221,"nameZh":6,"description":222,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":223,"categories":224,"keywords":228,"publishedAt":40},"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",[225],{"categoryNo":226,"categoryName":227,"taxonomyType":201,"taxonomyTypeDesc":202},"01JBSEEDCAT000000000000030","开发工程师",[229,230,171,231,208,232,38,233,234,235,180,236,237,238,239,240,241,242,243,23],"winui setup","setup","cli","sdk","SET","verify","install","up","repair","requirements","missing","native","toolchain","winapp cli","mode",{"skillNo":245,"name":246,"nameZh":6,"description":247,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":248,"categories":249,"keywords":253,"publishedAt":40},"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",[250],{"categoryNo":251,"categoryName":252,"taxonomyType":196,"taxonomyTypeDesc":197},"01JBSEEDCAT000000000000011","运维与部署",[254,171,255,231,232,39,9,256,38,257,258,259,31,260,261,26,215,25,240,262,242,218,23],"winui packaging","packaging","msix","windows app sdk","ci","certificates","self","project","CI\u002FCD",{"skillNo":264,"name":265,"nameZh":6,"description":266,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":267,"categories":268,"keywords":269,"publishedAt":40},"01M699KXTHG9FHK4X3JSZ4SV8J","winui-dev-workflow","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.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FwinappCli\u002Fblob\u002Fmain\u002Fplugins\u002Fwinui\u002Fagent-plugin\u002Fskills\u002Fwinui-dev-workflow\u002FSKILL.md",[],[270,271,171,272,273,231,232,39,38,274,209,275,31,261,26,276,215,25,240,242,185,277],"workflow","winui dev workflow","dev","dev workflow","create","fix","diagnosis","new",{"skillNo":279,"name":280,"nameZh":6,"description":281,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":282,"categories":283,"keywords":294,"publishedAt":40},"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",[284,287,290,291],{"categoryNo":285,"categoryName":286,"taxonomyType":196,"taxonomyTypeDesc":197},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":288,"categoryName":289,"taxonomyType":196,"taxonomyTypeDesc":197},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":199,"categoryName":200,"taxonomyType":201,"taxonomyTypeDesc":202},{"categoryNo":292,"categoryName":293,"taxonomyType":201,"taxonomyTypeDesc":202},"01JBSEEDCAT000000000000036","内容创作者",[295,296,171,297,232,298,299,38,257,172,176,177,300,301,302,303,304,26,25,305,218,306],"design","winui design","writing","accessibility","fluent","api","read","layout","pages","bind","controls","fluent design"]