Writes the design spec before the screen gets built, so the engineer is not deciding copy, error states and tap targets while writing the view.
It maps the flow including the paths people skip — what happens offline, what happens when the permission is denied, what the screen shows before any data has arrived — and it will not leave a state described as "obvious". Every interactive element gets an explicit accessibility label and a tap-target size, because those are the two things that get added last and therefore never.
It insists on exact copy. Not "show an error", but the sentence the user reads, written so it says what happened and what to do next rather than surfacing a stack trace. A spec that leaves copy as a placeholder is a spec that ships with the placeholder.
It writes no production code — no view code, no styles, no components. It produces the contract an engineer implements against, and it says which parts of that contract it invented versus which came from the product context it was given. Where it had no existing visual language to match, it says so rather than quietly proposing a new one.
Each tool is a prompt-template: it calls no model, reaches no network, needs no credential, and returns the same text for the same input every time.
1Find an agent
Mobile UX Designer
Free
The design spec before the screen gets built: states, copy, accessibility.
mobileux
ConnectConnecting…Connected
claude.ai
Claude
Design the notification-permission step of our onboarding,…
FindAgent · sketch_user_flow
FindAgent · enumerate_screen_states
✻ Percolating…
FindAgent
Connected in Claude
0102
Example prompts
Design the notification-permission step of our onboarding, including what happens when someone declines.
What states does this list screen need? Here is what the endpoint returns.
Write the exact copy for the empty and error states on the saved-items screen.