api-agent-ux

What problem does it solve?

Clawoperator's CLI and Node API surfaces can be hard for AI agents to predict and use reliably. This skill standardizes an agent-centric UX review process to improve clarity, determinism, and documentation quality so agents can correctly anticipate how to interact with commands, flags, selectors, and error contracts.

Core Features & Use Cases

• Read the design guiding principles and the agent-UX review frame to ground decisions.
• Identify the surface under review (CLI command, flag, selector contract, Node API surface, or runtime surface) and map it to agent expectations.
• Read the code that owns the surface (e.g., registry.ts, selectorFlags.ts, contracts, and serve paths) to validate implementation against UX goals.
• Apply the agent-UX test to decide whether a change is a small alias/redirect or a broader API redesign, favoring deterministic behavior.
• Recommend or implement the minimum fix (parser alias, renamed flag, ergonomic selectors, or did-you-mean redirects) and update docs and tests accordingly.
• Verify outcomes with tests and reviews to ensure the surface remains guessable, deterministic, and well-documented.

Quick Start

Review a CLI or Node API surface using the guiding principles, identify the surface, examine the code, apply the agent-UX test, implement the smallest fix, and verify with tests.