Best API

Handle $ARGUMENTS.

Own the public call-site decision. This is a taste and decision skill, not an implementation engine. It picks or judges a public call shape and leaves adoption to the Plan playbook. VISION.md holds Plate's product and API direction, so read it and cite it instead of restating it. Whether a direction earns any work at all is verdict's question, answered through the Verdict playbook.

Modes

Infer the mode when it is omitted. Do not invent more modes for workflow stages that another skill already owns.

• design: choose the smallest materially justified API for a new or redesigned surface, and return one call-shape decision. When the work continues into an API plan, the Plan playbook runs pstack:architect under the api-plan reviews row.
• review: judge one current or proposed API, diff or plan, recommend the better target and rank its findings on the architecture reference's P0 to P3 scale (.agents/playbooks/references/architecture.md#priority), which the Babysit playbook's P0 and P1 gate reads.
• repair: edit the one Vision owner, then fix every example, recipe, check and doc that still teaches the rejected shape. See Repair.

A design or review verdict goes on a page, per AGENTS.md's Plan pages: the active plan's, or a one-off plan's.

Inputs

Read only what can change the decision: