[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M699K14VEBBPGC47CND2GDDE":3,"skill-same:01M699K14VEBBPGC47CND2GDDE":98},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":6,"ownerHtmlUrl":54,"ownerBlogUrl":55,"ownerDescription":56,"updatedAt":57,"install":58,"resources":71},"01M699K14VEBBPGC47CND2GDDE","winapp-manifest",null,"Create or edit Package.appxmanifest or appxmanifest.xml for any app type (GUI, console, service): execution aliases, file associations, protocols, capabilities, identity, app icons\u002Ftiles from one image. Use when changing what the manifest declares or replacing icons. Not for packaging or signing.","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-manifest\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"winapp manifest","manifest","when","image","for","signing","gui","type","app","use","packaging","edit","execution","file","protocols","package","capabilities","icons","create","identity","2026-11-10 10:12:30",false,"---\nname: winapp-manifest\ndescription: \"Create or edit Package.appxmanifest or appxmanifest.xml for any app type (GUI, console, service): execution aliases, file associations, protocols, capabilities, identity, app icons\u002Ftiles from one image. Use when changing what the manifest declares or replacing icons. Not for packaging or signing.\"\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- **Creating `Package.appxmanifest`** for a project that doesn't have one yet\n- **Generating app icon assets** from a single source image\n- **Understanding manifest structure** for package identity and capabilities\n\n## Prerequisites\n\n- winapp CLI installed\n- Optional: a source image (PNG or SVG, at least 400x400 pixels) for custom app icons\n\n## Key concepts\n\n**`Package.appxmanifest`** is the key prerequisite for most winapp commands — it's more important than `winapp.yaml`. It declares:\n- **Package identity** — name, publisher, version\n- **App entry point** — which executable to launch\n- **Capabilities** — what the app can access (internet, file system, etc.)\n- **Visual assets** — icons for Start menu, taskbar, installers\n- **Extensions** — share target, startup tasks, file associations, etc.\n\n**Two manifest templates:**\n- **`packaged`** (default) — for full MSIX distribution\n- **`sparse`** — for desktop apps that need package identity without full MSIX containment (uses `AllowExternalContent`)\n\n**`winapp init` also generates a manifest** as part of full project setup. Use `winapp manifest generate` when you only need the manifest without SDK setup or `winapp.yaml`.\n\n## Usage\n\n### Generate a new manifest\n\n```powershell\n# Defaults — uses current folder name, current user as publisher\nwinapp manifest generate\n\n# Into a specific directory\nwinapp manifest generate .\u002Fmy-project\n\n# Customize identity\nwinapp manifest generate --package-name \"MyApp\" --publisher-name \"CN=Contoso\" --version \"2.0.0.0\"\n\n# Set entry point and description\nwinapp manifest generate --executable myapp.exe --description \"My awesome app\"\n\n# Generate a sparse manifest (for desktop apps needing identity without full MSIX)\nwinapp manifest generate --template sparse\n\n# Overwrite existing manifest\nwinapp manifest generate --if-exists overwrite\n```\n\nOutput:\n- `Package.appxmanifest` — the manifest file\n- `Assets\u002F` — default app icons in required sizes (Square44x44Logo, Square150x150Logo, Wide310x150Logo, etc.)\n\n### Update app icons from a source image\n\n```powershell\n# Generate all required icon sizes from one source image\nwinapp manifest update-assets .\u002Fmy-logo.png\n\n# SVG source images produce the best quality at all sizes\nwinapp manifest update-assets .\u002Fmy-logo.svg\n\n# Specify manifest location (if not in current directory)\nwinapp manifest update-assets .\u002Fmy-logo.png --manifest .\u002Fpath\u002Fto\u002FPackage.appxmanifest\n\n# Generate light theme variants from a separate image\nwinapp manifest update-assets .\u002Fmy-logo.png --light-image .\u002Fmy-logo-light.png\n\n# Use the same image for both (generates all MRT light theme qualifiers)\nwinapp manifest update-assets .\u002Fmy-logo.png --light-image .\u002Fmy-logo.png\n```\n\nThe source image should be at least 400x400 pixels (PNG or SVG recommended). The command reads the manifest to determine which asset sizes are needed and generates:\n- **5 scale variants** per asset (100%, 125%, 150%, 200%, 400%)\n- **14 plated + 14 unplated targetsize variants** for the app icon (44x44)\n- **app.ico** — multi-resolution ICO file for shell integration. If an existing `.ico` file is present in the assets directory, it is replaced in-place (preserving the original filename)\n- With `--light-image`: light theme variants using the correct MRT qualifiers per asset type\n\n### Add an execution alias\n\nExecution aliases let users launch the app by typing its name in a terminal (e.g. `myapp`).\n\n```powershell\n# Add alias inferred from the Executable attribute in the manifest\nwinapp manifest add-alias\n\n# Specify the alias name explicitly\nwinapp manifest add-alias --name myapp\n\n# Target a specific manifest file\nwinapp manifest add-alias --manifest .\u002Fpath\u002Fto\u002FPackage.appxmanifest\n```\n\nThis adds a `uap5:AppExecutionAlias` extension to the manifest. If the alias already exists, the command reports it and exits successfully.\n\n> **When combined with `winapp run --with-alias`** or the `WinAppRunUseExecutionAlias` MSBuild property, this enables apps to run in the current terminal with inherited stdin\u002Fstdout\u002Fstderr instead of opening a new window.\n\n## Manifest structure overview\n\nA typical `Package.appxmanifest` looks like:\n\n```xml\n\u003C?xml version=\"1.0\" encoding=\"utf-8\"?>\n\u003CPackage xmlns=\"http:\u002F\u002Fschemas.microsoft.com\u002Fappx\u002Fmanifest\u002Ffoundation\u002Fwindows10\"\n         xmlns:uap=\"http:\u002F\u002Fschemas.microsoft.com\u002Fappx\u002Fmanifest\u002Fuap\u002Fwindows10\"\n         xmlns:rescap=\"http:\u002F\u002Fschemas.microsoft.com\u002Fappx\u002Fmanifest\u002Ffoundation\u002Fwindows10\u002Frestrictedcapabilities\">\n  \u003CIdentity Name=\"MyApp\" Publisher=\"CN=MyPublisher\" Version=\"1.0.0.0\" \u002F>\n  \u003CProperties>\n    \u003CDisplayName>My App\u003C\u002FDisplayName>\n    \u003CPublisherDisplayName>My Publisher\u003C\u002FPublisherDisplayName>\n    \u003CLogo>Assets\\StoreLogo.png\u003C\u002FLogo>\n  \u003C\u002FProperties>\n  \u003CResources>\n    \u003CResource Language=\"en-us\" \u002F>\n  \u003C\u002FResources>\n  \u003CApplications>\n    \u003CApplication Id=\"App\" Executable=\"myapp.exe\" EntryPoint=\"Windows.FullTrustApplication\">\n      \u003Cuap:VisualElements DisplayName=\"My App\" Description=\"My Application\"\n        Square150x150Logo=\"Assets\\Square150x150Logo.png\"\n        Square44x44Logo=\"Assets\\Square44x44Logo.png\" BackgroundColor=\"transparent\" \u002F>\n    \u003C\u002FApplication>\n  \u003C\u002FApplications>\n  \u003CCapabilities>\n    \u003Crescap:Capability Name=\"runFullTrust\" \u002F>\n  \u003C\u002FCapabilities>\n\u003C\u002FPackage>\n```\n\nKey fields to edit:\n- `Identity.Name` — unique package name (no spaces)\n- `Identity.Publisher` — must match your certificate exactly\n- `Application.Executable` — your app's exe filename\n- `Capabilities` — add capabilities as needed (`internetClient`, `broadFileSystemAccess`, etc.)\n\n## Tips\n\n- Always ensure `Identity.Publisher` matches your signing certificate — use `winapp cert generate --manifest` to auto-match\n- The `sparse` template adds a `\u003Cuap10:AllowExternalContent>true\u003C\u002Fuap10:AllowExternalContent>` element (under `\u003CProperties>`) for apps that need identity but run outside the MSIX container\n- You can manually edit `Package.appxmanifest` after generation — it's a standard XML file\n- Image assets must match the paths referenced in the manifest — `update-assets` handles this automatically\n- For logos, transparent PNGs or SVGs work best. SVG source images are rendered as vectors directly at each target size, producing pixel-perfect results. Use a square image for best results across all sizes.\n- **`$targetnametoken$` placeholder:** When `winapp manifest generate` creates `Package.appxmanifest`, it sets `Application.Executable` to `$targetnametoken$.exe` by default. This is a valid placeholder that gets automatically resolved by `winapp package --executable \u003Cname>` at packaging time — you rarely need to override it during manifest generation. If `--executable` is provided to `winapp manifest generate`, winapp reads `FileVersionInfo` from the actual exe to auto-fill package name, description, publisher, and extract an icon, so the exe must already exist on disk.\n\n## Related skills\n\n- After generating a manifest, see `winapp-signing` for certificate setup and `winapp-package` to create the MSIX installer\n- Not sure which command to use? See `winapp-troubleshoot` for a command selection flowchart\n\n## Troubleshooting\n| Error | Cause | Solution |\n|-------|-------|----------|\n| \"Manifest already exists\" | `Package.appxmanifest` present | Use `--if-exists overwrite` to replace, or edit existing file directly |\n| \"Invalid source image\" | Image too small or wrong format | Use PNG or SVG, at least 400x400 pixels |\n| \"Publisher mismatch\" during packaging | Manifest publisher ≠ cert publisher | Edit `Identity.Publisher` in manifest, or regenerate cert with `--manifest` |\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- **Creating `Package.appxmanifest`** for a project that doesn't have one yet\n- **Generating app icon assets** from a single source image\n- **Understanding manifest structure** for package identity and capabilities\n\n## Prerequisites\n\n- winapp CLI installed\n- Optional: a source image (PNG or SVG, at least 400x400 pixels) for custom app icons\n\n## Key concepts\n\n**`Package.appxmanifest`** is the key prerequisite for most winapp commands — it's more important than `winapp.yaml`. It declares:\n- **Package identity** — name, publisher, version\n- **App entry point** — which executable to launch\n- **Capabilities** — what the app can access (internet, file system, etc.)\n- **Visual assets** — icons for Start menu, taskbar, installers\n- **Extensions** — share target, startup tasks, file associations, etc.\n\n**Two manifest templates:**\n- **`packaged`** (default) — for full MSIX distribution\n- **`sparse`** — for desktop apps that need package identity without full MSIX containment (uses `AllowExternalContent`)\n\n**`winapp init` also generates a manifest** as part of full project setup. Use `winapp manifest generate` when you only need the manifest without SDK setup or `winapp.yaml`.\n\n## Usage\n\n### Generate a new manifest\n\n```powershell\n# Defaults — uses current folder name, current user as publisher\nwinapp manifest generate\n\n# Into a specific directory\nwinapp manifest generate .\u002Fmy-project\n\n# Customize identity\nwinapp manifest generate --package-name \"MyApp\" --publisher-name \"CN=Contoso\" --version \"2.0.0.0\"\n\n# Set entry point and description\nwinapp manifest generate --executable myapp.exe --description \"My awesome app\"\n\n# Generate a sparse manifest (for desktop apps needing identity without full MSIX)\nwinapp manifest generate --template sparse\n\n# Overwrite existing manifest\nwinapp manifest generate --if-exists overwrite\n```\n\nOutput:\n- `Package.appxmanifest` — the manifest file\n- `Assets\u002F` — default app icons in required sizes (Square44x44Logo, Square150x150Logo, Wide310x150Logo, etc.)\n\n### Update app icons from a source image\n\n```powershell\n# Generate all required icon sizes from one source image\nwinapp manifest update-assets .\u002Fmy-logo.png\n\n# SVG source images produce the best quality at all sizes\nwinapp manifest update-assets .\u002Fmy-logo.svg\n\n# Specify manifest location (if not in current directory)\nwinapp manifest update-assets .\u002Fmy-logo.png --manifest .\u002Fpath\u002Fto\u002FPackage.appxmanifest\n\n# Generate light theme variants from a separate image\nwinapp manifest update-assets .\u002Fmy-logo.png --light-image .\u002Fmy-logo-light.png\n\n# Use the same image for both (generates all MRT light theme qualifiers)\nwinapp manifest update-assets .\u002Fmy-logo.png --light-image .\u002Fmy-logo.png\n```\n\nThe source image should be at least 400x400 pixels (PNG or SVG recommended). The command reads the manifest to determine which asset sizes are needed and generates:\n- **5 scale variants** per asset (100%, 125%, 150%, 200%, 400%)\n- **14 plated + 14 unplated targetsize variants** for the app icon (44x44)\n- **app.ico** — multi-resolution ICO file for shell integration. If an existing `.ico` file is present in the assets directory, it is replaced in-place (preserving the original filename)\n- With `--light-image`: light theme variants using the correct MRT qualifiers per asset type\n\n### Add an execution alias\n\nExecution aliases let users launch the app by typing its name in a terminal (e.g. `myapp`).\n\n```powershell\n# Add alias inferred from the Executable attribute in the manifest\nwinapp manifest add-alias\n\n# Specify the alias name explicitly\nwinapp manifest add-alias --name myapp\n\n# Target a specific manifest file\nwinapp manifest add-alias --manifest .\u002Fpath\u002Fto\u002FPackage.appxmanifest\n```\n\nThis adds a `uap5:AppExecutionAlias` extension to the manifest. If the alias already exists, the command reports it and exits successfully.\n\n> **When combined with `winapp run --with-alias`** or the `WinAppRunUseExecutionAlias` MSBuild property, this enables apps to run in the current terminal with inherited stdin\u002Fstdout\u002Fstderr instead of opening a new window.\n\n## Manifest structure overview\n\nA typical `Package.appxmanifest` looks like:\n\n```xml\n\u003C?xml version=\"1.0\" encoding=\"utf-8\"?>\n\u003CPackage xmlns=\"http:\u002F\u002Fschemas.microsoft.com\u002Fappx\u002Fmanifest\u002Ffoundation\u002Fwindows10\"\n         xmlns:uap=\"http:\u002F\u002Fschemas.microsoft.com\u002Fappx\u002Fmanifest\u002Fuap\u002Fwindows10\"\n         xmlns:rescap=\"http:\u002F\u002Fschemas.microsoft.com\u002Fappx\u002Fmanifest\u002Ffoundation\u002Fwindows10\u002Frestrictedcapabilities\">\n  \u003CIdentity Name=\"MyApp\" Publisher=\"CN=MyPublisher\" Version=\"1.0.0.0\" \u002F>\n  \u003CProperties>\n    \u003CDisplayName>My App\u003C\u002FDisplayName>\n    \u003CPublisherDisplayName>My Publisher\u003C\u002FPublisherDisplayName>\n    \u003CLogo>Assets\\StoreLogo.png\u003C\u002FLogo>\n  \u003C\u002FProperties>\n  \u003CResources>\n    \u003CResource Language=\"en-us\" \u002F>\n  \u003C\u002FResources>\n  \u003CApplications>\n    \u003CApplication Id=\"App\" Executable=\"myapp.exe\" EntryPoint=\"Windows.FullTrustApplication\">\n      \u003Cuap:VisualElements DisplayName=\"My App\" Description=\"My Application\"\n        Square150x150Logo=\"Assets\\Square150x150Logo.png\"\n        Square44x44Logo=\"Assets\\Square44x44Logo.png\" BackgroundColor=\"transparent\" \u002F>\n    \u003C\u002FApplication>\n  \u003C\u002FApplications>\n  \u003CCapabilities>\n    \u003Crescap:Capability Name=\"runFullTrust\" \u002F>\n  \u003C\u002FCapabilities>\n\u003C\u002FPackage>\n```\n\nKey fields to edit:\n- `Identity.Name` — unique package name (no spaces)\n- `Identity.Publisher` — must match your certificate exactly\n- `Application.Executable` — your app's exe filename\n- `Capabilities` — add capabilities as needed (`internetClient`, `broadFileSystemAccess`, etc.)\n\n## Tips\n\n- Always ensure `Identity.Publisher` matches your signing certificate — use `winapp cert generate --manifest` to auto-match\n- The `sparse` template adds a `\u003Cuap10:AllowExternalContent>true\u003C\u002Fuap10:AllowExternalContent>` element (under `\u003CProperties>`) for apps that need identity but run outside the MSIX container\n- You can manually edit `Package.appxmanifest` after generation — it's a standard XML file\n- Image assets must match the paths referenced in the manifest — `update-assets` handles this automatically\n- For logos, transparent PNGs or SVGs work best. SVG source images are rendered as vectors directly at each target size, producing pixel-perfect results. Use a square image for best results across all sizes.\n- **`$targetnametoken$` placeholder:** When `winapp manifest generate` creates `Package.appxmanifest`, it sets `Application.Executable` to `$targetnametoken$.exe` by default. This is a valid placeholder that gets automatically resolved by `winapp package --executable \u003Cname>` at packaging time — you rarely need to override it during manifest generation. If `--executable` is provided to `winapp manifest generate`, winapp reads `FileVersionInfo` from the actual exe to auto-fill package name, description, publisher, and extract an icon, so the exe must already exist on disk.\n\n## Related skills\n\n- After generating a manifest, see `winapp-signing` for certificate setup and `winapp-package` to create the MSIX installer\n- Not sure which command to use? See `winapp-troubleshoot` for a command selection flowchart\n\n## Troubleshooting\n| Error | Cause | Solution |\n|-------|-------|----------|\n| \"Manifest already exists\" | `Package.appxmanifest` present | Use `--if-exists overwrite` to replace, or edit existing file directly |\n| \"Invalid source image\" | Image too small or wrong format | Use PNG or SVG, at least 400x400 pixels |\n| \"Publisher mismatch\" during packaging | Manifest publisher ≠ cert publisher | Edit `Identity.Publisher` in manifest, or regenerate cert with `--manifest` |\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-manifest",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":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add microsoft\u002FwinappCli --skill winapp-manifest",{"tool":64,"command":65},"bunx","bunx skills add microsoft\u002FwinappCli --skill winapp-manifest",{"tool":67,"command":68},"pnpm","pnpm dlx skills add microsoft\u002FwinappCli --skill winapp-manifest","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FwinappCli\u002Fblob\u002Fmain\u002Fplugins\u002Fwinapp\u002Fskills\u002Fwinapp-manifest\u002FSKILL.md",true,[72,78,82,88,94],{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"examples\u002Freminders-cli\u002FPackage.swift","OTHER","其他",259,"https:\u002F\u002Fgithub.com\u002Fmattwag05\u002Fmw-plugins\u002Fblob\u002Fmain\u002Fclient-adapters\u002Fclaude-code\u002Fplugins\u002Fmacos-automation\u002Fskills\u002Freminders-automation\u002Fexamples\u002Freminders-cli\u002FPackage.swift",{"path":79,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":80,"sourceHtmlUrl":81},"examples\u002Freminders-cli\u002FSources\u002Fmain.swift",2570,"https:\u002F\u002Fgithub.com\u002Fmattwag05\u002Fmw-plugins\u002Fblob\u002Fmain\u002Fclient-adapters\u002Fclaude-code\u002Fplugins\u002Fmacos-automation\u002Fskills\u002Freminders-automation\u002Fexamples\u002Freminders-cli\u002FSources\u002Fmain.swift",{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"examples\u002Freminders-wrapper.ts","SCRIPT","脚本",2202,"https:\u002F\u002Fgithub.com\u002Fmattwag05\u002Fmw-plugins\u002Fblob\u002Fmain\u002Fclient-adapters\u002Fclaude-code\u002Fplugins\u002Fmacos-automation\u002Fskills\u002Freminders-automation\u002Fexamples\u002Freminders-wrapper.ts",{"path":89,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Feventkit-requirements.md","REFERENCE","参考文档",1192,"https:\u002F\u002Fgithub.com\u002Fmattwag05\u002Fmw-plugins\u002Fblob\u002Fmain\u002Fclient-adapters\u002Fclaude-code\u002Fplugins\u002Fmacos-automation\u002Fskills\u002Freminders-automation\u002Freferences\u002Feventkit-requirements.md",{"path":95,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Fswift-cli-pattern.md",1062,"https:\u002F\u002Fgithub.com\u002Fmattwag05\u002Fmw-plugins\u002Fblob\u002Fmain\u002Fclient-adapters\u002Fclaude-code\u002Fplugins\u002Fmacos-automation\u002Fskills\u002Freminders-automation\u002Freferences\u002Fswift-cli-pattern.md",[99,123,154,179,199,213],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":44},"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",[],[106,107,108,109,9,110,111,112,113,114,115,116,33,117,32,118,119,120,121,122,26],"winui wpf migration","winui","wpf","migration","windows","dispatcher","code","xaml","ui","migrate","system","mvvm","mapping","port","imaging","errors","namespaces",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":137,"publishedAt":44},"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",[129,132],{"categoryNo":130,"categoryName":131,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":133,"categoryName":134,"taxonomyType":135,"taxonomyTypeDesc":136},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[138,139,107,114,140,141,142,110,143,144,145,146,147,148,149,150,151,152,153,28,26],"testing","winui ui testing","ui testing","screenshots","sandbox","run","win32","harness","batch","write","feature","end","apps","input","winforms","desktop apps",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":163,"publishedAt":44},"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",[160],{"categoryNo":161,"categoryName":162,"taxonomyType":135,"taxonomyTypeDesc":136},"01JBSEEDCAT000000000000030","开发工程师",[164,165,107,166,142,167,110,168,169,170,33,171,172,173,174,175,176,177,178,26],"winui setup","setup","cli","sdk","SET","verify","install","up","repair","requirements","missing","native","toolchain","winapp cli","mode",{"skillNo":180,"name":181,"nameZh":6,"description":182,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":183,"categories":184,"keywords":188,"publishedAt":44},"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",[185],{"categoryNo":186,"categoryName":187,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",[189,107,34,166,167,190,9,191,110,192,193,194,195,196,197,32,150,152,175,198,177,28,26],"winui packaging","electron","msix","windows app sdk","ci","certificates","only","self","project","CI\u002FCD",{"skillNo":200,"name":201,"nameZh":6,"description":202,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":203,"categories":204,"keywords":205,"publishedAt":44},"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",[],[206,207,107,208,209,166,167,190,110,42,143,210,195,197,32,211,150,152,175,177,121,212],"workflow","winui dev workflow","dev","dev workflow","fix","diagnosis","new",{"skillNo":214,"name":215,"nameZh":6,"description":216,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":217,"categories":218,"keywords":229,"publishedAt":44},"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",[219,222,225,226],{"categoryNo":220,"categoryName":221,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":223,"categoryName":224,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":133,"categoryName":134,"taxonomyType":135,"taxonomyTypeDesc":136},{"categoryNo":227,"categoryName":228,"taxonomyType":135,"taxonomyTypeDesc":136},"01JBSEEDCAT000000000000036","内容创作者",[230,231,107,232,167,233,234,110,192,108,113,114,235,236,237,238,239,32,152,240,28,241],"design","winui design","writing","accessibility","fluent","api","read","layout","pages","bind","controls","fluent design"]