winapp-find-ui

Search WinUI 3 Gallery and Windows Community Toolkit samples for working XAML and C# control code.

1.2k|74|Updated Jul 30, 2025
One-click install
npx skills add https://github.com/microsoft/winappCli --skill winapp-find-ui
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: winapp-find-ui
Source: https://github.com/microsoft/winappCli/tree/main/plugins/winapp/skills/winapp-find-ui
Command: npx skills add https://github.com/microsoft/winappCli --skill winapp-find-ui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When building a WinUI 3 app, developers often don't know which control fits a UI intent or how to write its XAML and C# correctly. This Skill searches the WinUI 3 Gallery, Windows Community Toolkit, and curated core patterns to return real, working code examples without leaving the CLI.

Core Features & Use Cases

  • Natural-intent search: Query with phrases like "tabbed layout" or "swipeable list rows" to discover matching controls and scenario ids.
  • Full code retrieval: Fetch complete XAML and/or C# snippets by scenario id, with batch fetching of multiple scenarios at once.
  • Offline-capable corpus: The Gallery/Toolkit corpus ships inside the CLI and works with no network, with optional refresh from GitHub and a per-user cache.
  • Agent-friendly JSON output: Use --json to get structured results with stable, case-insensitive scenario ids and script-friendly exit codes.
  • Use Case: While building a settings page in a WinUI 3 app, search "settings card", pick the best Toolkit scenario, fetch its XAML with --id, and paste the working code directly into your project.

Quick Start

Ask the assistant to search WinUI 3 controls for a tabbed layout and fetch the full XAML and C# example for the best matching scenario.

Frequently Asked Questions about winapp-find-ui

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find WinUI 3 control examples from the command line?

Run winapp find-ui with a natural-language query like "tabbed layout" to get matching controls and scenario ids, then fetch the full XAML and C# with winapp find-ui --id <scenario-id>. Add --json for structured output an agent can parse.

What sources does winapp find-ui search for UI samples?

It searches the WinUI 3 Gallery, the Windows Community Toolkit, and curated built-in core patterns. The microsoft-ui-reactor ReactorGallery is opt-in and only searched when you pass --source reactor, since its samples are C#-only declarative WinUI.

Does winapp find-ui work for WPF or WinForms apps?

No. The corpus is WinUI 3 only, covering the WinUI 3 Gallery, Windows Community Toolkit, and opt-in Reactor samples. It does not include WPF, WinForms, or other UI frameworks.

Can I search WinUI samples offline without network access?

Yes. The Gallery, Toolkit, and Reactor corpus ships embedded in the CLI, so search, --list, and --id all work with no network. When GitHub is reachable the CLI refreshes and caches per-user, and --source core never touches the network.

What is the difference between winapp find-ui and winapp ui search?

winapp find-ui discovers controls and sample code for writing a WinUI 3 UI. winapp ui search inspects and automates the UI tree of an already running app via UI Automation, which is a different task.

Why are Reactor samples missing from my search results?

Reactor is excluded from normal searches by default because its C#-only declarative samples do not fit standard XAML plus code-behind apps. Pass --source reactor to search it, or fetch a reactor-<control>-<n> id directly with --id.