See Latest Screenshot
My most used command this month is three words to Claude: see latest screenshot. Here's the workflow, the ten-line skill behind it, and the places its eyes still aren't great.
The command I've run the most this month isn't a git command. It's three words I say to Claude: see latest screenshot.
Here's the whole workflow. I'm building a UI. Something looks off. A button is cut off, a modal is sitting two pixels too high, the mobile layout did something creative. I hit cmd shift 4, grab the broken part of the screen, go back to the terminal and type "see latest screenshot." Claude pulls the newest file out of my screenshots folder, looks at it, tells me what's wrong, and then I say the second most used phrase in my vocabulary: fix it.
Then I watch it work. That's it. That's the post. But let me show you why it's better than the obvious alternative, and where it falls on its face.
Why a picture beats a sentence
The old way was describing the bug in words. "The submit button is overflowing its container on small screens." That sentence is a lossy compression of what I'm actually seeing, and Claude has to decompress it back into a guess about the DOM. Half the time the guess is wrong, not because it's dumb but because my sentence was.

A screenshot is the bug. No translation. It sees the button, sees the container, sees the three other things I didn't mention because I'd stopped noticing them. More than once it's come back with "also, your label text is wrapping on the second card" and it was right, and I'd been staring past that for a week.
The skill is dumber than you think
If you haven't used them, a skill is just a saved set of instructions Claude can trigger by name. Mine is about ten lines. Find the newest .png in my screenshots folder. Read it. Describe the UI in one paragraph. List anything that looks broken, misaligned, clipped, or inconsistent with the rest of the app. Then stop and wait for me.
That last line matters. It doesn't fix anything on its own. I want to see the diagnosis first, because sometimes the "defect" it finds is a design choice I made on purpose, and I'd rather say "leave that" than revert it after.
Yes, there are skills now that do this whole loop automatically. They watch the folder, or they drive the browser themselves and snap it, then iterate until it looks right. Those are genuinely good and I use them on bigger passes. But for day-to-day building I still like being the one who decides something is wrong. The manual trigger keeps me in the loop without making me do the boring part.
Where its eyes aren't great
Vision is impressive and it is not pixel perfect. You need to know both.

It'll tell me something is centered when it's six pixels off. It misses low contrast stuff, a light gray border on a white card. It struggles with tiny text. Every so often it reads a label that isn't there, or confidently fixes the wrong element because two buttons look alike. None of that is a dealbreaker. It just means the first screenshot is a conversation starter, not a verdict.
So the rule is: screenshot again after the fix. Always. Trust the second picture, not the first explanation. If it says "fixed the alignment" and the new screenshot still looks wrong, it's wrong, and we go another round. Usually it lands by round two.
Tips if you want to steal this
- Crop tight. The less screen it has to look at, the better it looks at it.
- One problem per screenshot. Three bugs in one image gets you one and a half fixes.
- Name the element if you can. "The blue button" beats "the button" and it costs you four words.
- Say the viewport. "This is at 375 wide" saves it from guessing why things are stacked.
- Re-screenshot after every change. The loop is the feature.
- Keep the skill dumb. Mine describes and waits. The moment I let it auto-fix, it started fixing things I liked.
None of this is clever. It's a keyboard shortcut and three words. But it's turned the most annoying part of building UI, the describe-the-bug part, into the part I skip. Take a picture, say the words, watch it work.
Want to talk about what you're building?
Get in touch


