winapp-find-ui

This is an agent-first command

find-ui was designed for you, the agent — not primarily for a human browsing a gallery. It exists because the failure mode it prevents is an agent-specific one: writing plausible-looking XAML for a control whose real markup, properties, or namespace differ from what you recall. Treat it as the source of truth for WinUI markup:

• Fetch a real sample before writing WinUI markup. If you are about to hand-write XAML for a control you have not just looked at, search for it first and fetch the scenario with --id. The returned code comes from the shipping WinUI 3 Gallery and Windows Community Toolkit, so it compiles.
• Prefer it over recall and over web search. It returns code from a pinned, cached corpus of the real galleries rather than a blog post of unknown vintage.
• Use --json. Search, --id, and --list all emit stable structured shapes, and every failure — including parser errors — is a flat {"error": "..."} on stdout with a non-zero exit code, so you can branch on the result on every path.
• Pair it with winapp find-api. find-ui gives you working markup; find-api verifies any property you then change or add.