MAKE IT LOOK RIGHT
Point at a page and say what feels wrong
Most design feedback never makes it into a ticket, because writing it down is more work than the change itself. You know the hero is doing too much and the third section should not exist, but turning that into prose takes ten minutes. Saying it while scrolling takes forty seconds, and it arrives with the pointer attached.
Quick answer
To give an AI agent design feedback on a real page, record yourself scrolling it with Clipy, pointing at each thing you want changed and saying what is wrong and what you want instead. Paste the link into Claude Code, Codex or Cursor. The agent gets your pointer, the frames and your reasoning in one link, with no design file in between.
What to record
Open the real page, not a mockup.
Scroll through it at reading speed, section by section.
Stop on each thing you want changed and point at it.
Say what is wrong and what you want instead, in that order.
Say this while you record
Give the reason, not only the instruction. "Cut this, it repeats the headline" lets the agent make the same call on the next section. "Cut this" does not.
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 walking through a page and saying what I want changed. Give me back a numbered list of the changes I asked for, in the order I asked, each one naming the specific element from the recording. Do not start editing. Show me the list first so I can correct it. Then work through it one change at a time in this repo, and tell me where my feedback was too vague to act on.
Feedback recordings almost always contain one instruction you did not realize was ambiguous. The list surfaces it before any code moves.
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 | |
|---|---|---|
| Getting feedback out of your head | A ticket you keep meaning to write. | Forty seconds of talking over the page. |
| "This section" | Ambiguous in any page with more than three sections. | Resolved by the pointer evidence and the frame. |
| The reasoning behind the change | Lost, so the next similar decision goes the wrong way. | In the transcript, where the agent reads it. |
| Handing the same feedback to a designer | Rewrite it for a human. | Same link, they watch it. |
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.
Say what you want, not only what you dislike
A list of complaints produces a list of deletions. If you know what should be there instead, say it, even roughly.
Order the pass by importance, not by scroll position
If the third thing you mention is the one that matters, say so. Otherwise it lands in the middle of a list and gets treated like the rest.
One page per recording
A recording that covers four pages produces a change list too long to review properly. Split it.
Common questions
Do I need a design system for this to work?
No, but it helps a lot. If your project has tokens or a component library, tell the agent to use them in the prompt. Otherwise it will invent values, and they will be nearly right, which is worse.
Can I give feedback on a page that is not mine?
You can record any page you can open. Whether the agent can change it depends on whether the code is in your repo.
How specific do I have to be about sizes and spacing?
Less than you think. "Too tight" and "give it about twice this" usually produce the right change, because the agent has the frame to look at. If you have an exact value, say it.
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.