winapp-find-api

This is an agent-first command

find-api was designed for you, the agent — not primarily for a human reading a terminal. It exists because the failure mode it prevents is an agent-specific one: confidently writing a type, property, or enum value that does not exist. Treat it as the authority on the API surface, not as an optional convenience:

• Ground every Windows/WinRT symbol you emit. If you are not certain a type, property, or enum value exists in this project's metadata, look it up before you write it. A lookup is cheaper than a build.
• Prefer it over recall and over web search. Your training data describes some version of WinUI/WinRT; find-api describes the exact metadata this project references. When they disagree, find-api wins.
• Use --json. Every verb emits structured output with stable shapes and non-zero exit codes on missing subjects, so you can gate codegen on the result instead of parsing prose.
• Batch subjects into one call. See below — this matters more here than anywhere else in the CLI.