MAKE IT LOOK RIGHT
Make a form less annoying to fill in
You cannot review a form by looking at it. The problems are in the filling: the field that validates too early, the error that appears below the fold, the tab order that skips, the label that makes sense only to whoever wrote the schema. Record one honest run and the friction shows itself.
Quick answer
To make a form easier to fill in, record yourself filling it in at normal speed with test data, mistakes included, and say what confuses you as it happens. Paste the Clipy link into an AI agent like Claude Code, Codex or Cursor. It lists the friction points in order and proposes changes to field order, labels, help text, validation timing and error placement.
Product walkthrough. Tap for sound.
What to record
Fill it in at normal speed with test data, keyboard where you would use the keyboard.
Make the mistakes a real person makes, and let the validation react.
Say what confused you the moment it confuses you, not afterwards.
Submit it and let the result land on screen.
Say this while you record
Narrate the hesitations. "I do not know what this field wants" is the single most valuable sentence in a form recording.
The prompt to paste
Replace the link with your own recording's share URL, then paste this into Claude Code, Cursor, Codex, or whichever agent you connected.
Read https://clipy.online/video/<id> It is me filling in a form and saying where it gets in the way. List the friction points in the order they happen, with what I said about each one. Then propose changes in this repo: field order, labels, help text, validation timing and error placement. Separate the changes that are safe and obvious from the ones that change what gets submitted, and do not touch the second group without asking me.
Splitting cosmetic from behavioral changes keeps a form tidy-up from quietly altering what your backend receives.
What the agent gets from that link
A summary of what happened
A short written account of the recording, so the agent starts with the shape of the request rather than a wall of raw text.
A timestamped transcript
Your narration with times against it, when audio was captured and processed. This is where your reasoning lives, and it is usually the part that decides whether the agent fixes the right thing.
Key moments with frames
Selected instants from the recording with an image of the screen at that point, so the agent can look at the state you were describing instead of guessing at it.
Pointer and click evidence
Where you clicked and what you were pointing at, with the control's accessibility label when the capture recorded one. It turns "this button" into a specific element.
What changes
| Writing it down | Recording it instead | |
|---|---|---|
| Finding the friction | A usability session you never schedule. | One honest run, recorded. |
| Validation timing problems | Nearly invisible in a static review. | Obvious in a recording, because you react to them. |
| Risky changes | Bundled in with the cosmetic ones. | Separated, because the prompt asked for that. |
Tips
Connect your agent once
Run the setup at /agent-setup once. After that every Clipy share link works in the same session you are already in.
Never use real personal data
Everything you type appears in the recording. Test data only, always.
Do not fix your own mistakes silently
If you fumble a field, leave it and say so. That fumble is data. Re-recording a clean run hides the exact thing you are trying to find.
Paste the link once the transcript shows
The transcript, summary and key moments appear on the watch page moments after Stop.
Common questions
Should I record someone else using it instead?
That is better data if you can get it, and the workflow is identical. Ask permission, use test data, and let them narrate.
What about accessibility problems?
Record a keyboard-only run and say what you cannot reach. The pointer evidence will be sparse, which is itself the finding, and your narration carries it.
Can the agent tell me which field failed validation?
It can see the error in the frames and hear what you said about it. For the underlying rule, it reads your code.
Other jobs
The same job, elsewhere on Clipy
This page is the job. These cover the same ground for a specific agent, a specific team, or as a tool you can open right now.
The full list is on the use-case index. If your agent is not connected yet, start at agent setup.