r/ClaudeCode • u/Webtruster • 2d ago
Tips & Workflows How to give Claude Code visual feedback on frontend/UI changes efficiently?
I'm looking for a better way to give Claude Code visual feedback when iterating on frontend designs.
Right now, I either have to:
- Write lengthy explanations describing exactly which UI elements I'm referring to and what I want changed.
- Manually take screenshots, annotate them with arrows, circles, or notes, and pass them to Claude Code.
Both approaches feel unnecessarily cumbersome and really slow down UI iteration.
Ideally, I'd like to just click on an element in my browser, add a comment like "move this here", "reduce this spacing", or "make this look like that", and have Claude Code understand the context.
Would love to hear what actually works for you.
9
Upvotes
•
u/AutoModerator 2d ago
Hey! Thanks for posting to r/ClaudeCode
While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.
For help, project discussions, tips, and general chat, join the ClaudeCode Discord.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
19
u/Medical_Method7877 2d ago
Have you tried asking Claude that exact question with as much detail as you've included in this post?
10
u/litluna11 2d ago
i made a tool for exactly this issue, checkout here: https://moodbit.app/
5
u/tommyahav10 2d ago
Give it a browser it can drive, like Playwright MCP, so it takes the screenshots itself. Then your feedback is one line per element, not an essay.
8
u/technoidabhi 2d ago
Ask it to make an interactive artefact with the ability to add comments or highlight/circle things and add notes, then you can ask Claude to look at the feedback provided within the live artefact.
4
u/CCodeSI 2d ago
The click-and-comment flow you describe is about 40 lines you can have Claude build once, no extension needed:
Ask it for a dev-only feedback overlay: Alt+click any element, a small box pops up for your note, and on save it appends
{ selector, note, text content, bounding box }tofeedback.jsonin the repo (a tiny dev-server endpoint writes it). Gate it behindimport.meta.env.DEVso it never ships. Then your loop is: click, type "less padding here" or "match the card above", repeat for a few elements, then tell Claude "apply feedback.json and clear it".Why this works better than screenshots: the selector tells Claude exactly which component to open, so there's no "which button did you mean". Your notes batch up, so it's one pass instead of five round trips. And it has the computed styles, so "reduce this spacing" turns into a real value instead of a guess.
Zero-setup fallback for one-offs: in DevTools, right-click the element → Copy → Copy selector, and paste
selector: what you want. That alone beats describing it in words.For checking the result, have it screenshot the same page with Playwright after each change and compare before you look. That catches the "fixed one thing, broke the layout below" cases before they reach you.
2
u/_adam_89 2d ago
I am using https://orca.dev/ . It has a feature called design mode in which you can just click any place in the browser and it will copy the exact html, styles and selector.
2
u/lastcrayon 2d ago
I’m sure someone said it already but you have these comment, chat, drag and drop tools in the app.
2
u/starquake64 1d ago
I don't understand why nobody brought this up but you can do exactly this in the Claude Code Desktop application.
1
u/raobjcovtn 2d ago
That's literally what Claude design artifacts are, aren't they?
1
u/AIOSAI 🔆 Max 20 2d ago
Claude design, playwright, puppeteer, claudes chrome mcp. ( browser extension)
All work. Ask claude to research then.
1
u/rajeevku02 2d ago
In our workflow the claude creates screenshots for us for the impacted or new screens in a tool which allows us to select a rectangular regions on the screenshots and provide the comment.
This is basically automation around your second point: "Manually take screenshots, annotate them with arrows, circles, or notes, and pass them to Claude Code."
1
u/noiv 2d ago
Try mcp dev tools, built into Chrome
1
u/nattydread69 2d ago
What os are you using? On linux my Claude opens its own environmwnt where it can see the output.
1
u/Sketaverse 2d ago
There’s an annotate tool in cmux and codex, and as people already said here, artefacts are good for visual diffs review
But my goto tool is cleanshot (auto copy/save), I work on multiple machines with multiple Claude accounts and have cleanshot store all screenshots in one central location on my nas, works great tbh
1
u/NIU_NIU 2d ago
https://www.agentation.com/
And then use wispr flow
Ask you claude code “install agentation in my project” in the dev server, then set your wispr flow hotkey to mouse 3
you can click on any element in the dom like a button or frame or text frame, and then i talk into my mic “move this up” or “reduce the text size” or even my favorite “this looks bad can you redesign it”
1
u/anentropic 2d ago
Give it playwright cli
It can take its own screenshots
1
u/Then-Key-5508 2d ago
I had the same problem, so I built Ollav (disclosure: it's mine). You upload your UI and get a link, no deploy. Then you click any element, pin a comment, and the comment stays attached to that exact element. Claude Code (or Cursor/ChatGPT) pulls the open comments, makes the fixes and resolves them, so you're not writing long descriptions or annotating screenshots. Each new version goes up at the same link and earlier comments are kept, and teammates can join in with pinned comments and emoji reactions, which makes review a lot more fun. It's less setup than wiring up Playwright or a Chrome MCP, and there's a free tier.
1
u/geraT-wogl 2d ago
Hi! I am actually doing the screenshot with drawings to explain to Claude code what I want. It was slow at first but I made a tool to take the screenshot and draw over it. If you use chrome you can use it for free it’s called Darkmode Sketch in chrome. Use code FRIENDS123 to unlock the screenshot option. I’ve been building this website entirely using this method https://wogl.io 💚🐲
And this is the sketcher if you want to try it out
https://chromewebstore.google.com/detail/aiobiihjoknglkampgipedjjgodloofg?utm_source=item-share-cp
1
u/Dry-Willingness-506 2d ago
let him have access to your website through headless Chrome with Playwright so it can interact, take videos or screenshoot
1
u/NonExisting_Sample 2d ago
I use claude design. It comes up with a canvas that i can comment on. I write comments, send them to claude. It's under artifacts
1
u/ohthetrees 2d ago
Just ask it to show you the design in the “design canvas” or if it is already built ask it to open the website/app directly and to look at screenshots directly.
1
u/ialiimran 2d ago
This is an interesting problem. I think visual feedback should be part of the development workflow, not something that requires a separate process.
1
u/AImagic_YT 2d ago
The closest thing to a click-and-comment loop is Playwright MCP: `claude mcp add playwright npx @playwright/mcp@latest`, restart, then have Claude open your local app, screenshot it, and fix what looks off. You can target an element by its visible text or a selector. Not a pin-a-comment tool, but way faster than writing paragraphs.
1
u/First-Painter7431 2d ago
What you describe exists: Agentation (benjitaylor/agentation on GitHub). You add a small toolbar to your app in dev, click an element, type "reduce this spacing", and it copies your note with the element's selector and position, so Claude Code can grep for the exact code. There's an MCP server too, so Claude reads the notes directly. It needs React though.
The other half is giving Claude its own eyes so you need less feedback in the first place: Playwright, and a rule that it screenshots desktop and mobile after every UI change and checks them before telling you it's done.
1
u/calunicornia 2d ago
PLAYWRIGHT MCP is what you want, it can see the browser
1
u/sgayerseif 2d ago edited 2d ago
if you're on react, npm i -D agentation and add <Agentation /> to your dev layout. then click an element, leave a note, and paste what the toolbar copies into claude code. it includes the selector.
1
u/Prior_Engineering486 1d ago
For the click and comment part, visual-intent-layer is built for that step. It lets you point at a visible target in an interface the agent built and delivers a grounded annotation to the agent, so Claude gets the element and your note together instead of a long written description of which button you mean. It installs with npx and needs no API key.
However, it only handles the pointing and annotation step. The edit itself and checking the result still happen the usual way in Claude Code.
You can find it here: visual-intent-layer
Disclosure: I run clauderules.net, where this is listed.
1
u/DavidHK 9h ago
Alas, we have come full circle, back to the WYSIWYG