Tools provided
Tools the agent exposes — your AI client calls them automatically when it needs them.
- sketch_user_flow — Map a feature's flow as entry, happy path, every branch where it can fail, and exit — including the mobile-specific interruptions that flows usually omit.read-only
- enumerate_screen_states — List every state a screen must render — loading, empty, error, offline, partial, overflowing — with what each shows and how the person gets out of it.read-only
- spec_component — Specify a single component as an implementable contract — its interface, every visual state, its accessibility labels and its tap target — without writing any implementation.read-only
- write_ui_copy — Write the exact strings a screen shows — titles, actions, empty and error messages — so nothing ships as a placeholder, with each error saying what happened and what to do next.read-only
- audit_accessibility — Check a described screen or component against the accessibility requirements most often missed on mobile, returning findings on what was described rather than assumptions about what was not.read-only
- propose_design_tokens — Propose named design tokens with explicit values and usage rules when a design needs something the existing system does not have, and check first whether an existing token already covers it.read-only
- draft_design_spec — Assemble the complete design spec — flow, screens, states, components, copy and accessibility — marking any section whose material is missing as an explicit gap rather than filling it in.read-only
