UI Tool Discovery
Mission
Agents must not blindly attempt to use tools that are not configured or available. ui-tool-discovery forces an explicit evaluation phase to map out exactly what is executable in the current environment before orchestrating a V2 UI pipeline.
The Discovery Pipeline
For each UI task, the agent must execute:
DISCOVER → CLASSIFY → SELECT → ACTIVATE → VERIFY
Classification Matrix
Every tool, MCP server, integration, or skill MUST be classified into one of these four buckets:
- AVAILABLE + EXECUTABLE
- The tool is natively available and the agent has permission/capability to run it silently. (e.g.,
browser_subagent,run_commandfornpm).
- The tool is natively available and the agent has permission/capability to run it silently. (e.g.,
- AVAILABLE + MANUAL
- The tool is available but requires user intervention or approval to run.
- NOT AVAILABLE
- The tool does not exist in this environment. (e.g., A Figma MCP when no token is provided).
- REQUIRES USER SETUP
- The tool could be used, but the user must first configure it (e.g., setting an API key, providing a specific
.rivasset).
- The tool could be used, but the user must first configure it (e.g., setting an API key, providing a specific
Deterministic Verification
For libraries like Rive or Lottie, ui-tool-discovery MUST run a deterministic check before claiming AVAILABLE + EXECUTABLE.
- Web: Check
package.jsonfor@rive-app/react-canvas(or equivalent). - Flutter: Check
pubspec.yamlforrive. - Assets: Verify a
.rivor.jsonasset actually exists in the project. If the package is missing but the environment allows installation (e.g.npm install), the agent may install it if the user requested motion. If the asset is missing, it isREQUIRES USER SETUP(orNOT AVAILABLEif no installation is possible).
Execution Rules
- Never Fabricate Execution: Do not claim to have used a tool if it was classified as
NOT AVAILABLEorREQUIRES USER SETUP. - Honest Fallbacks: If a preferred external tool (e.g., Figma for reference analysis) is unavailable, explicitly state the fallback mechanism (e.g., "Figma unavailable → Code-first design direction").
- Final Report: The agent must output the discovery classification in its final execution report.


