[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M699JTCAG0PAAVB63VHJPE9Y":3,"skill-same:01M699JTCAG0PAAVB63VHJPE9Y":275},{"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},"01M699JTCAG0PAAVB63VHJPE9Y","winapp-find-ui",null,"Find the right WinUI 3 control and a real, compiling sample from the WinUI Gallery or Community Toolkit with winapp find-ui. Use when building WinUI UI and unsure which control fits (cards, tabs, swipe lists, inline messages) or when asked for a sample. Not for WPF, WinForms, or a running app.","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-find-ui\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"ui","find","winapp find ui","control","running","when","inline","for","which","gallery","with","swipe","app","sample","community","use","messages","wpf","winui","toolkit","2026-11-10 10:12:30",false,"---\nname: winapp-find-ui\ndescription: Find the right WinUI 3 control and a real, compiling sample from the WinUI Gallery or Community Toolkit with winapp find-ui. Use when building WinUI UI and unsure which control fits (cards, tabs, swipe lists, inline messages) or when asked for a sample. Not for WPF, WinForms, or a running app.\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## This is an agent-first command\n\n`find-ui` was designed for **you, the agent** — not primarily for a human browsing a\ngallery. It exists because the failure mode it prevents is an agent-specific one:\nwriting plausible-looking XAML for a control whose real markup, properties, or\nnamespace differ from what you recall. Treat it as the source of truth for WinUI\nmarkup:\n\n- **Fetch a real sample before writing WinUI markup.** If you are about to hand-write\n  XAML for a control you have not just looked at, search for it first and fetch the\n  scenario with `--id`. The returned code comes from the shipping WinUI 3 Gallery and\n  Windows Community Toolkit, so it compiles.\n- **Prefer it over recall and over web search.** It returns code from a pinned,\n  cached corpus of the real galleries rather than a blog post of unknown vintage.\n- **Use `--json`.** Search, `--id`, and `--list` all emit stable structured shapes,\n  and *every* failure — including parser errors — is a flat `{\"error\": \"...\"}` on\n  stdout with a non-zero exit code, so you can branch on the result on every path.\n- **Pair it with `winapp find-api`.** `find-ui` gives you working markup; `find-api`\n  verifies any property you then change or add.\n\nHumans can and do run it directly, and everything below works fine typed by hand. But\nthe ergonomics (compact search → `--id` fetch, `--json`, exit codes) are tuned for\nagent loops.\n\n## When to use\n\nUse this skill when building a **WinUI 3** UI and you need to discover which\ncontrol fits an intent and get a real, working code example — without leaving the\nCLI or guessing at control names and APIs.\n\n`winapp find-ui` searches the **WinUI 3 Gallery** and the **Windows Community\nToolkit** (plus a few curated **core** patterns) and returns a working code\nsnippet plus where it came from. A third source, the **microsoft-ui-reactor\nReactorGallery**, is **opt-in**: it is excluded from a normal search and is only\nsearched when you pass `--source reactor`.\n\n- **WinUI-only.** The corpus is WinUI 3 Gallery + Windows Community Toolkit (+\n  Reactor when opted in). It does **not** cover WPF, WinForms, or other UI\n  frameworks.\n- **The Toolkit contributes more than controls.** Its helpers, converters,\n  behaviors, and extensions are searchable and fetchable the same way.\n  Converters, behaviors, and triggers are grouped under an umbrella entry\n  (`Converters`, `Behaviors`, `Header Behaviors`, `Triggers`) whose samples are\n  named for the specific type; helpers and extensions are not grouped, and each\n  is a top-level entry under its own name (`NetworkHelper`, `TextBoxExtensions`).\n  All are indexed by\n  the words in those type names, so `FileSizeToFriendlyStringConverter`,\n  `converters`, and `convert bool to visibility` all land. A description that\n  shares no words with the type name does not — `check internet connection`\n  misses `NetworkHelper`. Fall back to the **type name** or `--list`.\n- **Reactor is opt-in and for Reactor projects only.** Reactor is a C#-only\n  declarative\u002FMVU framework — its samples can't paste into a standard `dotnet new\n  winui` XAML + code-behind app, so a default search deliberately omits it. Only\n  reach for `--source reactor` when you're actually building a Reactor app.\n- **Result shape varies by source.** Gallery and Toolkit scenarios return XAML,\n  C#, or both (one-sided samples are kept); Reactor scenarios are C#-only\n  declarative WinUI (no XAML). If an upstream Gallery-style sample still contains\n  unresolved `$(Name)` substitution placeholders, `find-ui` suppresses that\n  language block rather than presenting it as pasteable code.\n- Distinct from `winapp ui search`, which searches a *running app's* UI tree via\n  UI Automation — unrelated to control\u002Fsample discovery.\n\n**Front-load lookups, then code.** Search for each feature you need up front, pick\nthe right control and scenario id, fetch its full code with `--id`, then write your\nXAML — don't interleave search-and-code.\n\n## Workflow\n\n```bash\n# 1. Search compactly to find the control + its scenario ids (WinUI-only)\nwinapp find-ui \"tabbed layout\"\n\n# 2. Fetch the full XAML + C# (and prerequisite notes) for the best match\nwinapp find-ui --id gallery-tabview-1\n\n# 3. Batch: fetch several scenarios at once\nwinapp find-ui --id gallery-tabview-1 --id toolkit-tabbedcommandbar-1\n```\n\n## Examples\n\n```bash\n# Natural-intent search\nwinapp find-ui \"a card with an image and title\"\nwinapp find-ui \"swipeable list rows\"\n\n# Restrict to one source\nwinapp find-ui \"settings card\" --source toolkit\nwinapp find-ui \"color picker\" --source gallery\n\n# Reactor is opt-in: excluded from a normal search, only searched with --source reactor\n# (use this only for a Reactor\u002FMVU project — its C#-only samples don't fit standard XAML apps)\nwinapp find-ui \"flex layout\" --source reactor\n\n# Return more candidates\nwinapp find-ui \"navigation\" --max 6\n\n# Browse everything (heavy — prefer search; excludes opt-in Reactor)\nwinapp find-ui --list\n\n# Force a corpus refresh from GitHub\nwinapp find-ui \"info bar\" --refresh\n\n# Search the built-in core patterns fully offline (no network, no fetch)\nwinapp find-ui \"file picker\" --source core\n```\n\n## Agent-friendly output\n\nAdd `--json` for a structured, grounded result an agent can consume in one shot:\n\n```bash\nwinapp find-ui \"color picker\" --json\n```\n\n- **Search** → `{ query, matchCount, matches: [ { source, control, score, description?, scenarios: [ { id, header } ] } ] }` — compact; use the `id` values to fetch code.\n- **`--id`** → `{ results: [ { id, found, content } ] }` — `content` is the code markdown block (XAML and\u002For C# for Gallery\u002FToolkit; C# only for Reactor).\n- **`--list`** → `{ count, items: [ { id, header } ] }`.\n- On error, `--json` emits `{ \"error\": \"...\" }` on stdout with a non-zero exit code.\n\n## Notes & tips\n\n- **One mode at a time.** A search query, `--id`, and `--list` are mutually\n  exclusive — combining them is rejected. `--source` applies to search only.\n- **Reactor is opt-in.** A normal search and `--list` cover Gallery + Toolkit +\n  core only. Pass `--source reactor` to search Reactor (reactor-only results);\n  a `reactor-\u003Ccontrol>-\u003Cn>` `--id` still fetches even without the flag. Skipping\n  Reactor by default keeps its C#-only samples from outranking usable controls in\n  a standard XAML app.\n- **Add the `Namespace:` imports yourself.** Sample C# is a class-body fragment, so\n  its `using` directives are listed on a `**Namespace:**` line above the code rather\n  than inside it. Add each entry as a `using` in your C# file, and each `**Setup:**`\n  `xmlns` entry to your XAML root — without them the snippet won't resolve its types.\n  Treat the line as the non-obvious imports, not a complete set.\n- **An `Undefined handlers:` line means \"wire this up\", not \"this sample is broken\".**\n  A sample's XAML can hook an event\n  (`ScrollAnimationStarting=\"ScrollView_ScrollAnimationStarting\"`) to a method that\n  lives in the gallery's page code-behind, which isn't published. The attribute is\n  kept because it's what the sample teaches; the line lists each one. Add a method\n  with that name (or rename the attribute) in your code-behind. Entries are matched\n  by shape, so a rare one may not be an event at all — ignore it.\n- **Everything works offline.** The Gallery\u002FToolkit\u002FReactor corpus ships inside the\n  CLI, so search, `--list`, and `--id` all work with no network access — including\n  on a first run in a sandbox or behind a proxy that blocks\n  `raw.githubusercontent.com`. When GitHub is reachable the CLI refreshes from it\n  and caches per-user under `\u003Cglobal .winapp>\u002Fcache\u002Ffind-ui` (refreshed at most\n  every 24 hours, or on demand with `--refresh`); the built-in corpus is a floor,\n  never a ceiling, so live data always wins. `--source core` searches the curated\n  built-in patterns and never touches the network at all.\n- **Check the corpus provenance when it matters.** `--json` carries `\"corpus\"`:\n  `\"network\"` (fetched this run), `\"cache\"` (this machine's earlier fetch), or\n  `\"embedded\"` (served from a corpus built into the CLI — a core-only request\n  (`--source core`, or an `--id` set that is all core patterns), or a\n  Gallery\u002FToolkit\u002FReactor result whose fetch failed or whose local cache predates\n  the bake). A Gallery\u002FToolkit\u002FReactor `\"embedded\"` result may lag upstream — re-run\n  with `--refresh` if a sample looks out of date; core patterns ship with the CLI and\n  `--refresh` cannot change them. The field is absent only when no corpus could be\n  loaded at all.\n- **Scenario ids** are stable within a cached corpus and **case-insensitive** —\n  `GALLERY-TABVIEW-1` resolves the same as `gallery-tabview-1`. Gallery\u002FToolkit\u002FReactor ids\n  look like `gallery-\u003Ccontrol>-\u003Cn>` \u002F `toolkit-\u003Ccontrol>-\u003Cn>` \u002F\n  `reactor-\u003Ccontrol>-\u003Cn>`; the `\u003Csource>-` prefix disambiguates controls that\n  exist in more than one gallery (e.g. `ColorPicker`). Curated **core** patterns\n  use a plain descriptive id with **no** `\u003Csource>-\u003Ccontrol>-\u003Cn>` shape (e.g.\n  `file-picker-desktop`, `live-charts`); fetch them the same way with `--id`, and\n  browse them with `--source core`.\n- **`--json` is always JSON.** With `--json`, every failure — including argument\u002Fparser\n  errors such as a non-integer `--max` — is emitted as a flat `{\"error\": \"...\"}` object\n  on stdout with a non-zero exit code, so an agent can parse the result on every path.\n- **Exit codes** are script-friendly: `0` on a hit, `1` on no match \u002F error.\n- Keep queries **focused** (one feature per query) — the lexical ranker rewards\n  specific phrasing. Batch multiple focused queries rather than one broad one.\n\n## Upstream is the source of truth\n\nWhich samples exist is upstream's call. winapp adds no samples of its own to the\nGallery or Toolkit corpus and does not rewrite an individual sample's\nimplementation to its own taste.\n\nSnippets are still processed: they're cleaned of names that only\nresolve inside the gallery apps, but substance is never deleted. Samples are returned in full — nothing is cut\nshort. So treat a result as **upstream's sample, mechanically extracted** — not as a\nbyte-for-byte copy of the file in their repo. Most samples paste and compile as-is\nonce you add the `Namespace:` imports; a few also reference a page or type of their\nown that you'll need to define.\n\nWhere a control has a known pitfall, or two controls are easy to confuse, the CLI\nsays so in the **Important** and **Family** notes attached to the result. Read\nthose — they carry guidance that isn't in the sample itself, and they're winapp's,\nnot upstream's.\n\nIf a sample is missing or genuinely wrong **upstream**, report it against the\nsource the result is tagged with: `[gallery]` →\n[WinUI-Gallery](https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FWinUI-Gallery\u002Fissues), `[toolkit]` →\n[Windows Community Toolkit](https:\u002F\u002Fgithub.com\u002FCommunityToolkit\u002FWindows\u002Fissues).\nIf the defect looks like a cut-off snippet or markup that won't\nparse, that's winapp's extraction — report it here instead.\n\n## Related skills\n\n- **winapp-ui-automation** — inspect and drive a *running* app's UI tree (a\n  different job from discovering controls to write).\n\n## CLI reference\n\nRun `winapp find-ui --help` for current command options, or `winapp --cli-schema`\nfor 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## This is an agent-first command\n\n`find-ui` was designed for **you, the agent** — not primarily for a human browsing a\ngallery. It exists because the failure mode it prevents is an agent-specific one:\nwriting plausible-looking XAML for a control whose real markup, properties, or\nnamespace differ from what you recall. Treat it as the source of truth for WinUI\nmarkup:\n\n- **Fetch a real sample before writing WinUI markup.** If you are about to hand-write\n  XAML for a control you have not just looked at, search for it first and fetch the\n  scenario with `--id`. The returned code comes from the shipping WinUI 3 Gallery and\n  Windows Community Toolkit, so it compiles.\n- **Prefer it over recall and over web search.** It returns code from a pinned,\n  cached corpus of the real galleries rather than a blog post of unknown vintage.\n- **Use `--json`.** Search, `--id`, and `--list` all emit stable structured shapes,\n  and *every* failure — including parser errors — is a flat `{\"error\": \"...\"}` on\n  stdout with a non-zero exit code, so you can branch on the result on every path.\n- **Pair it with `winapp find-api`.** `find-ui` gives you working markup; `find-api`\n  verifies any property you then change or add.\n\nHumans can and do run it directly, and everything below works fine typed by hand. But\nthe ergonomics (compact search → `--id` fetch, `--json`, exit codes) are tuned for\nagent loops.\n\n## When to use\n\nUse this skill when building a **WinUI 3** UI and you need to discover which\ncontrol fits an intent and get a real, working code example — without leaving the\nCLI or guessing at control names and APIs.\n\n`winapp find-ui` searches the **WinUI 3 Gallery** and the **Windows Community\nToolkit** (plus a few curated **core** patterns) and returns a working code\nsnippet plus where it came from. A third source, the **microsoft-ui-reactor\nReactorGallery**, is **opt-in**: it is excluded from a normal search and is only\nsearched when you pass `--source reactor`.\n\n- **WinUI-only.** The corpus is WinUI 3 Gallery + Windows Community Toolkit (+\n  Reactor when opted in). It does **not** cover WPF, WinForms, or other UI\n  frameworks.\n- **The Toolkit contributes more than controls.** Its helpers, converters,\n  behaviors, and extensions are searchable and fetchable the same way.\n  Converters, behaviors, and triggers are grouped under an umbrella entry\n  (`Converters`, `Behaviors`, `Header Behaviors`, `Triggers`) whose samples are\n  named for the specific type; helpers and extensions are not grouped, and each\n  is a top-level entry under its own name (`NetworkHelper`, `TextBoxExtensions`).\n  All are indexed by\n  the words in those type names, so `FileSizeToFriendlyStringConverter`,\n  `converters`, and `convert bool to visibility` all land. A description that\n  shares no words with the type name does not — `check internet connection`\n  misses `NetworkHelper`. Fall back to the **type name** or `--list`.\n- **Reactor is opt-in and for Reactor projects only.** Reactor is a C#-only\n  declarative\u002FMVU framework — its samples can't paste into a standard `dotnet new\n  winui` XAML + code-behind app, so a default search deliberately omits it. Only\n  reach for `--source reactor` when you're actually building a Reactor app.\n- **Result shape varies by source.** Gallery and Toolkit scenarios return XAML,\n  C#, or both (one-sided samples are kept); Reactor scenarios are C#-only\n  declarative WinUI (no XAML). If an upstream Gallery-style sample still contains\n  unresolved `$(Name)` substitution placeholders, `find-ui` suppresses that\n  language block rather than presenting it as pasteable code.\n- Distinct from `winapp ui search`, which searches a *running app's* UI tree via\n  UI Automation — unrelated to control\u002Fsample discovery.\n\n**Front-load lookups, then code.** Search for each feature you need up front, pick\nthe right control and scenario id, fetch its full code with `--id`, then write your\nXAML — don't interleave search-and-code.\n\n## Workflow\n\n```bash\n# 1. Search compactly to find the control + its scenario ids (WinUI-only)\nwinapp find-ui \"tabbed layout\"\n\n# 2. Fetch the full XAML + C# (and prerequisite notes) for the best match\nwinapp find-ui --id gallery-tabview-1\n\n# 3. Batch: fetch several scenarios at once\nwinapp find-ui --id gallery-tabview-1 --id toolkit-tabbedcommandbar-1\n```\n\n## Examples\n\n```bash\n# Natural-intent search\nwinapp find-ui \"a card with an image and title\"\nwinapp find-ui \"swipeable list rows\"\n\n# Restrict to one source\nwinapp find-ui \"settings card\" --source toolkit\nwinapp find-ui \"color picker\" --source gallery\n\n# Reactor is opt-in: excluded from a normal search, only searched with --source reactor\n# (use this only for a Reactor\u002FMVU project — its C#-only samples don't fit standard XAML apps)\nwinapp find-ui \"flex layout\" --source reactor\n\n# Return more candidates\nwinapp find-ui \"navigation\" --max 6\n\n# Browse everything (heavy — prefer search; excludes opt-in Reactor)\nwinapp find-ui --list\n\n# Force a corpus refresh from GitHub\nwinapp find-ui \"info bar\" --refresh\n\n# Search the built-in core patterns fully offline (no network, no fetch)\nwinapp find-ui \"file picker\" --source core\n```\n\n## Agent-friendly output\n\nAdd `--json` for a structured, grounded result an agent can consume in one shot:\n\n```bash\nwinapp find-ui \"color picker\" --json\n```\n\n- **Search** → `{ query, matchCount, matches: [ { source, control, score, description?, scenarios: [ { id, header } ] } ] }` — compact; use the `id` values to fetch code.\n- **`--id`** → `{ results: [ { id, found, content } ] }` — `content` is the code markdown block (XAML and\u002For C# for Gallery\u002FToolkit; C# only for Reactor).\n- **`--list`** → `{ count, items: [ { id, header } ] }`.\n- On error, `--json` emits `{ \"error\": \"...\" }` on stdout with a non-zero exit code.\n\n## Notes & tips\n\n- **One mode at a time.** A search query, `--id`, and `--list` are mutually\n  exclusive — combining them is rejected. `--source` applies to search only.\n- **Reactor is opt-in.** A normal search and `--list` cover Gallery + Toolkit +\n  core only. Pass `--source reactor` to search Reactor (reactor-only results);\n  a `reactor-\u003Ccontrol>-\u003Cn>` `--id` still fetches even without the flag. Skipping\n  Reactor by default keeps its C#-only samples from outranking usable controls in\n  a standard XAML app.\n- **Add the `Namespace:` imports yourself.** Sample C# is a class-body fragment, so\n  its `using` directives are listed on a `**Namespace:**` line above the code rather\n  than inside it. Add each entry as a `using` in your C# file, and each `**Setup:**`\n  `xmlns` entry to your XAML root — without them the snippet won't resolve its types.\n  Treat the line as the non-obvious imports, not a complete set.\n- **An `Undefined handlers:` line means \"wire this up\", not \"this sample is broken\".**\n  A sample's XAML can hook an event\n  (`ScrollAnimationStarting=\"ScrollView_ScrollAnimationStarting\"`) to a method that\n  lives in the gallery's page code-behind, which isn't published. The attribute is\n  kept because it's what the sample teaches; the line lists each one. Add a method\n  with that name (or rename the attribute) in your code-behind. Entries are matched\n  by shape, so a rare one may not be an event at all — ignore it.\n- **Everything works offline.** The Gallery\u002FToolkit\u002FReactor corpus ships inside the\n  CLI, so search, `--list`, and `--id` all work with no network access — including\n  on a first run in a sandbox or behind a proxy that blocks\n  `raw.githubusercontent.com`. When GitHub is reachable the CLI refreshes from it\n  and caches per-user under `\u003Cglobal .winapp>\u002Fcache\u002Ffind-ui` (refreshed at most\n  every 24 hours, or on demand with `--refresh`); the built-in corpus is a floor,\n  never a ceiling, so live data always wins. `--source core` searches the curated\n  built-in patterns and never touches the network at all.\n- **Check the corpus provenance when it matters.** `--json` carries `\"corpus\"`:\n  `\"network\"` (fetched this run), `\"cache\"` (this machine's earlier fetch), or\n  `\"embedded\"` (served from a corpus built into the CLI — a core-only request\n  (`--source core`, or an `--id` set that is all core patterns), or a\n  Gallery\u002FToolkit\u002FReactor result whose fetch failed or whose local cache predates\n  the bake). A Gallery\u002FToolkit\u002FReactor `\"embedded\"` result may lag upstream — re-run\n  with `--refresh` if a sample looks out of date; core patterns ship with the CLI and\n  `--refresh` cannot change them. The field is absent only when no corpus could be\n  loaded at all.\n- **Scenario ids** are stable within a cached corpus and **case-insensitive** —\n  `GALLERY-TABVIEW-1` resolves the same as `gallery-tabview-1`. Gallery\u002FToolkit\u002FReactor ids\n  look like `gallery-\u003Ccontrol>-\u003Cn>` \u002F `toolkit-\u003Ccontrol>-\u003Cn>` \u002F\n  `reactor-\u003Ccontrol>-\u003Cn>`; the `\u003Csource>-` prefix disambiguates controls that\n  exist in more than one gallery (e.g. `ColorPicker`). Curated **core** patterns\n  use a plain descriptive id with **no** `\u003Csource>-\u003Ccontrol>-\u003Cn>` shape (e.g.\n  `file-picker-desktop`, `live-charts`); fetch them the same way with `--id`, and\n  browse them with `--source core`.\n- **`--json` is always JSON.** With `--json`, every failure — including argument\u002Fparser\n  errors such as a non-integer `--max` — is emitted as a flat `{\"error\": \"...\"}` object\n  on stdout with a non-zero exit code, so an agent can parse the result on every path.\n- **Exit codes** are script-friendly: `0` on a hit, `1` on no match \u002F error.\n- Keep queries **focused** (one feature per query) — the lexical ranker rewards\n  specific phrasing. Batch multiple focused queries rather than one broad one.\n\n## Upstream is the source of truth\n\nWhich samples exist is upstream's call. winapp adds no samples of its own to the\nGallery or Toolkit corpus and does not rewrite an individual sample's\nimplementation to its own taste.\n\nSnippets are still processed: they're cleaned of names that only\nresolve inside the gallery apps, but substance is never deleted. Samples are returned in full — nothing is cut\nshort. So treat a result as **upstream's sample, mechanically extracted** — not as a\nbyte-for-byte copy of the file in their repo. Most samples paste and compile as-is\nonce you add the `Namespace:` imports; a few also reference a page or type of their\nown that you'll need to define.\n\nWhere a control has a known pitfall, or two controls are easy to confuse, the CLI\nsays so in the **Important** and **Family** notes attached to the result. Read\nthose — they carry guidance that isn't in the sample itself, and they're winapp's,\nnot upstream's.\n\nIf a sample is missing or genuinely wrong **upstream**, report it against the\nsource the result is tagged with: `[gallery]` →\n[WinUI-Gallery](https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FWinUI-Gallery\u002Fissues), `[toolkit]` →\n[Windows Community Toolkit](https:\u002F\u002Fgithub.com\u002FCommunityToolkit\u002FWindows\u002Fissues).\nIf the defect looks like a cut-off snippet or markup that won't\nparse, that's winapp's extraction — report it here instead.\n\n## Related skills\n\n- **winapp-ui-automation** — inspect and drive a *running* app's UI tree (a\n  different job from discovering controls to write).\n\n## CLI reference\n\nRun `winapp find-ui --help` for current command options, or `winapp --cli-schema`\nfor the complete machine-readable command schema.\n",{"name":5,"description":7},"main","1fe910277860e8dbb38bfbeef7e8bdb039d6ee41","plugins\u002Fwinapp\u002Fskills\u002Fwinapp-find-ui",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-find-ui",{"tool":64,"command":65},"bunx","bunx skills add microsoft\u002FwinappCli --skill winapp-find-ui",{"tool":67,"command":68},"pnpm","pnpm dlx skills add microsoft\u002FwinappCli --skill winapp-find-ui","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FwinappCli\u002Fblob\u002Fmain\u002Fplugins\u002Fwinapp\u002Fskills\u002Fwinapp-find-ui\u002FSKILL.md",true,[72,78,84,88,92,96,100,104,108,112,116,120,124,128,132,136,140,144,150,154,158,162,166,170,174,178,182,186,190,194,198,204,207,211,215,219,223,227,231,235,239,243,247,251,255,259,263,267,271],{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},".claude-plugin\u002Fmarketplace.json","REFERENCE","参考文档",5098,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002F.claude-plugin\u002Fmarketplace.json",{"path":79,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":82,"sourceHtmlUrl":83},".gitignore","OTHER","其他",336,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002F.gitignore",{"path":85,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":86,"sourceHtmlUrl":87},"docs\u002FAGENTDB_LEARNING_FLOW_EXPLAINED.md",10365,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Fdocs\u002FAGENTDB_LEARNING_FLOW_EXPLAINED.md",{"path":89,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":90,"sourceHtmlUrl":91},"docs\u002FAGENTDB_VISUAL_GUIDE.md",16022,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Fdocs\u002FAGENTDB_VISUAL_GUIDE.md",{"path":93,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":94,"sourceHtmlUrl":95},"docs\u002FCHANGELOG.md",26207,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Fdocs\u002FCHANGELOG.md",{"path":97,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":98,"sourceHtmlUrl":99},"docs\u002FCLAUDE_SKILLS_ARCHITECTURE.md",8301,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Fdocs\u002FCLAUDE_SKILLS_ARCHITECTURE.md",{"path":101,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":102,"sourceHtmlUrl":103},"docs\u002FDECISION_LOGIC.md",9907,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Fdocs\u002FDECISION_LOGIC.md",{"path":105,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":106,"sourceHtmlUrl":107},"docs\u002FINTERNAL_FLOW_ANALYSIS.md",16536,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Fdocs\u002FINTERNAL_FLOW_ANALYSIS.md",{"path":109,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":110,"sourceHtmlUrl":111},"docs\u002FLEARNING_VERIFICATION_REPORT.md",15473,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Fdocs\u002FLEARNING_VERIFICATION_REPORT.md",{"path":113,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":114,"sourceHtmlUrl":115},"docs\u002FNAMING_CONVENTIONS.md",9951,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Fdocs\u002FNAMING_CONVENTIONS.md",{"path":117,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":118,"sourceHtmlUrl":119},"docs\u002FPIPELINE_ARCHITECTURE.md",19810,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Fdocs\u002FPIPELINE_ARCHITECTURE.md",{"path":121,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":122,"sourceHtmlUrl":123},"docs\u002FQUICK_VERIFICATION_GUIDE.md",5289,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Fdocs\u002FQUICK_VERIFICATION_GUIDE.md",{"path":125,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":126,"sourceHtmlUrl":127},"docs\u002FREADME.md",5652,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Fdocs\u002FREADME.md",{"path":129,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":130,"sourceHtmlUrl":131},"docs\u002FTRY_IT_YOURSELF.md",6347,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Fdocs\u002FTRY_IT_YOURSELF.md",{"path":133,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":134,"sourceHtmlUrl":135},"docs\u002FUSER_BENEFITS_GUIDE.md",11707,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Fdocs\u002FUSER_BENEFITS_GUIDE.md",{"path":137,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":138,"sourceHtmlUrl":139},"exports\u002F.gitignore",124,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Fexports\u002F.gitignore",{"path":141,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":142,"sourceHtmlUrl":143},"exports\u002FREADME.md",4161,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Fexports\u002FREADME.md",{"path":145,"resourceType":146,"resourceTypeDesc":147,"sizeBytes":148,"sourceHtmlUrl":149},"integrations\u002Fagentdb_bridge.py","SCRIPT","脚本",27501,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Fintegrations\u002Fagentdb_bridge.py",{"path":151,"resourceType":146,"resourceTypeDesc":147,"sizeBytes":152,"sourceHtmlUrl":153},"integrations\u002Fagentdb_real_integration.py",24775,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Fintegrations\u002Fagentdb_real_integration.py",{"path":155,"resourceType":146,"resourceTypeDesc":147,"sizeBytes":156,"sourceHtmlUrl":157},"integrations\u002Ffallback_system.py",20516,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Fintegrations\u002Ffallback_system.py",{"path":159,"resourceType":146,"resourceTypeDesc":147,"sizeBytes":160,"sourceHtmlUrl":161},"integrations\u002Flearning_feedback.py",15708,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Fintegrations\u002Flearning_feedback.py",{"path":163,"resourceType":146,"resourceTypeDesc":147,"sizeBytes":164,"sourceHtmlUrl":165},"integrations\u002Fvalidation_system.py",17375,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Fintegrations\u002Fvalidation_system.py",{"path":167,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":168,"sourceHtmlUrl":169},"README.md",73780,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002FREADME.md",{"path":171,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":172,"sourceHtmlUrl":173},"references\u002FACTIVATION_BEST_PRACTICES.md",16705,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Freferences\u002FACTIVATION_BEST_PRACTICES.md",{"path":175,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":176,"sourceHtmlUrl":177},"references\u002Factivation-patterns-guide.md",17933,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Freferences\u002Factivation-patterns-guide.md",{"path":179,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":180,"sourceHtmlUrl":181},"references\u002Factivation-quality-checklist.md",9773,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Freferences\u002Factivation-quality-checklist.md",{"path":183,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":184,"sourceHtmlUrl":185},"references\u002Factivation-testing-guide.md",13829,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Freferences\u002Factivation-testing-guide.md",{"path":187,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":188,"sourceHtmlUrl":189},"references\u002Fclaude-llm-protocols-guide.md",31374,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Freferences\u002Fclaude-llm-protocols-guide.md",{"path":191,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":192,"sourceHtmlUrl":193},"references\u002Fcontext-aware-activation.md",21484,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Freferences\u002Fcontext-aware-activation.md",{"path":195,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":196,"sourceHtmlUrl":197},"references\u002Fcross-platform-guide.md",10986,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Freferences\u002Fcross-platform-guide.md",{"path":199,"resourceType":200,"resourceTypeDesc":201,"sizeBytes":202,"sourceHtmlUrl":203},"references\u002Fexamples\u002Fexports\u002Fstock-analyzer-cskill-api-v1.0.0.zip","ASSET","资产文件",13890,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Freferences\u002Fexamples\u002Fexports\u002Fstock-analyzer-cskill-api-v1.0.0.zip",{"path":205,"resourceType":200,"resourceTypeDesc":201,"sizeBytes":202,"sourceHtmlUrl":206},"references\u002Fexamples\u002Fexports\u002Fstock-analyzer-cskill-desktop-v1.0.0.zip","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Freferences\u002Fexamples\u002Fexports\u002Fstock-analyzer-cskill-desktop-v1.0.0.zip",{"path":208,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":209,"sourceHtmlUrl":210},"references\u002Fexamples\u002Fexports\u002Fstock-analyzer-cskill-v1.0.0_INSTALL.md",5689,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Freferences\u002Fexamples\u002Fexports\u002Fstock-analyzer-cskill-v1.0.0_INSTALL.md",{"path":212,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":213,"sourceHtmlUrl":214},"references\u002Fexport-guide.md",13093,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Freferences\u002Fexport-guide.md",{"path":216,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":217,"sourceHtmlUrl":218},"references\u002Fmulti-intent-detection.md",28046,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Freferences\u002Fmulti-intent-detection.md",{"path":220,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":221,"sourceHtmlUrl":222},"references\u002Fphase1-discovery.md",11715,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Freferences\u002Fphase1-discovery.md",{"path":224,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":225,"sourceHtmlUrl":226},"references\u002Fphase2-design.md",6006,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Freferences\u002Fphase2-design.md",{"path":228,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":229,"sourceHtmlUrl":230},"references\u002Fphase3-architecture.md",7923,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Freferences\u002Fphase3-architecture.md",{"path":232,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":233,"sourceHtmlUrl":234},"references\u002Fphase4-detection.md",35897,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Freferences\u002Fphase4-detection.md",{"path":236,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":237,"sourceHtmlUrl":238},"references\u002Fphase5-implementation.md",24657,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Freferences\u002Fphase5-implementation.md",{"path":240,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":241,"sourceHtmlUrl":242},"references\u002Fphase6-testing.md",18620,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Freferences\u002Fphase6-testing.md",{"path":244,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":245,"sourceHtmlUrl":246},"references\u002Fquality-standards.md",19986,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Freferences\u002Fquality-standards.md",{"path":248,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":249,"sourceHtmlUrl":250},"references\u002Fsynonym-expansion-system.md",12972,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Freferences\u002Fsynonym-expansion-system.md",{"path":252,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":253,"sourceHtmlUrl":254},"references\u002Ftemplates\u002Fmarketplace-robust-template.json",8385,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Freferences\u002Ftemplates\u002Fmarketplace-robust-template.json",{"path":256,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":257,"sourceHtmlUrl":258},"references\u002Ftemplates\u002FREADME-activation-template.md",6090,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Freferences\u002Ftemplates\u002FREADME-activation-template.md",{"path":260,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":261,"sourceHtmlUrl":262},"references\u002Ftools\u002Factivation-tester.md",15734,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Freferences\u002Ftools\u002Factivation-tester.md",{"path":264,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":265,"sourceHtmlUrl":266},"references\u002Ftools\u002Fintent-analyzer.md",23841,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Freferences\u002Ftools\u002Fintent-analyzer.md",{"path":268,"resourceType":146,"resourceTypeDesc":147,"sizeBytes":269,"sourceHtmlUrl":270},"references\u002Ftools\u002Ftest-automation-scripts.sh",25364,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Freferences\u002Ftools\u002Ftest-automation-scripts.sh",{"path":272,"resourceType":146,"resourceTypeDesc":147,"sizeBytes":273,"sourceHtmlUrl":274},"scripts\u002Fexport_utils.py",23041,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002FFrancyJGLisboa-agent-skill-creator\u002Fscripts\u002Fexport_utils.py",[276,297,326,351,372,387],{"skillNo":277,"name":278,"nameZh":6,"description":279,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":280,"categories":281,"keywords":282,"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",[],[283,42,41,284,9,285,286,287,288,24,289,290,39,291,36,292,293,294,295,296,29],"winui wpf migration","migration","windows","dispatcher","code","xaml","migrate","system","mvvm","mapping","port","imaging","errors","namespaces",{"skillNo":298,"name":299,"nameZh":6,"description":300,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":301,"categories":302,"keywords":309,"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",[303,308],{"categoryNo":304,"categoryName":305,"taxonomyType":306,"taxonomyTypeDesc":307},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[310,311,42,24,312,313,314,285,315,316,317,318,319,320,321,322,323,324,325,31,29],"testing","winui ui testing","ui testing","screenshots","sandbox","run","win32","harness","batch","write","feature","end","apps","input","winforms","desktop apps",{"skillNo":327,"name":328,"nameZh":6,"description":329,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":330,"categories":331,"keywords":335,"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",[332],{"categoryNo":333,"categoryName":334,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师",[336,337,42,338,314,339,285,340,341,342,39,343,344,345,346,347,348,349,350,29],"winui setup","setup","cli","sdk","SET","verify","install","up","repair","requirements","missing","native","toolchain","winapp cli","mode",{"skillNo":352,"name":353,"nameZh":6,"description":354,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":355,"categories":356,"keywords":360,"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",[357],{"categoryNo":358,"categoryName":359,"taxonomyType":306,"taxonomyTypeDesc":307},"01JBSEEDCAT000000000000011","运维与部署",[361,42,362,338,339,363,9,364,285,365,366,367,368,369,370,36,322,324,347,371,349,31,29],"winui packaging","packaging","electron","msix","windows app sdk","ci","certificates","only","self","project","CI\u002FCD",{"skillNo":373,"name":374,"nameZh":6,"description":375,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":376,"categories":377,"keywords":378,"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",[],[379,380,42,381,382,338,339,363,285,383,315,384,368,370,36,385,322,324,347,349,295,386],"workflow","winui dev workflow","dev","dev workflow","create","fix","diagnosis","new",{"skillNo":388,"name":389,"nameZh":6,"description":390,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":391,"categories":392,"keywords":403,"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",[393,396,399,400],{"categoryNo":394,"categoryName":395,"taxonomyType":306,"taxonomyTypeDesc":307},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":397,"categoryName":398,"taxonomyType":306,"taxonomyTypeDesc":307},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":401,"categoryName":402,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000036","内容创作者",[404,405,42,406,339,407,408,285,365,41,288,24,409,410,411,412,413,36,324,414,31,415],"design","winui design","writing","accessibility","fluent","api","read","layout","pages","bind","controls","fluent design"]