MAKE IT LOOK RIGHT

Fix spacing and alignment without a design file

Spacing and type problems are individually too small to file and collectively the reason a page looks unfinished. They are also the easiest thing in the world to point at and the hardest thing to write down. One pass down the page, pointing and talking, collects the whole set in under a minute.

Quick answer

To fix spacing and typography without a design file, record one pass down the page with Clipy, pointing at each spacing, size or alignment problem and saying which way it should move. Paste the link into an AI agent like Claude Code, Codex or Cursor, and it fixes them in one change using your project's existing spacing and type scales.

Product walkthrough. Tap for sound.

What to record

  1. Open the page and go top to bottom without skipping.

  2. Stop at each spacing, size or alignment problem and point at it.

  3. Say which direction it should move: tighter, looser, smaller, aligned to what.

  4. Name a reference where you can: "match the card above" beats a number you invented.

Say this while you record

Relative instructions are better than absolute ones. "Half of what it is now" and "line this up with the heading" both survive a design system that does not use your numbers.

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 a pass over one page pointing out spacing, size and alignment problems. List every change I asked for, each one naming the element and the direction of the change.

Then apply them using this project's existing spacing scale and type scale. Do not introduce new one-off values. If something I asked for has no equivalent in the scale, tell me and give me the nearest two options.

The instruction about the scale is what keeps this from producing thirty arbitrary pixel values.

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 downRecording it instead
Filing these at allMostly they do not get filed.One recording covers the whole page.
Consistency of the fixValues invented per instruction.Constrained to the project's scale by the prompt.
Review afterwardsYou re-check every value.You check the list matches what you said.

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.

  • Pick a reference instead of a number

    Guessed pixel values fight the design system. Pointing at something already correct and saying "match that" gives the agent a target it can resolve to a real token.

  • Zoom does not travel

    If you have the browser at 150 percent while recording, everything looks bigger in the frames than it is. Record at 100 percent so relative judgements hold.

  • Paste the link once the transcript shows

    The transcript, summary and key moments appear on the watch page moments after Stop.

Common questions

Will the agent know my spacing scale?

It can read it out of the project, the same way it reads anything else. Telling it to use the existing scale in the prompt is what makes it look rather than guess.

Can I do this across several pages?

You can, but review quality drops with list length. One page per recording keeps the change reviewable.

Does it work for dark mode issues?

Yes, and it is a good use of a recording, because switching between the two on camera shows the contrast problem in a way a single screenshot does not.

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.