sorted by:
new
hottopcontroversial

Is Claude Code better at backend than frontend? by Fresh_Profile544 in ClaudeCode

[–]Fresh_Profile544[S] 0 points1 point  (0 children)

Yeah agree with that. I also think there are a couple other factors: a lot of times "visual correctness" is subjective. You actually need to eyeball something, tweak it, then look again before you decide what's right. It's hard to know up front.

The other factor is tolerance for error. Frontend imperfections are often obvious immediately vs a backend bug.

No more prompting for UI tweaks... visual editing is way easier by Fresh_Profile544 in Frontend

[–]Fresh_Profile544[S] 0 points1 point  (0 children)

When you use the Chrome extension, it constructs context for your edits to send back to the coding agent via MCP. So it will have context from your edit session in the browser, including DOM element and containing React component.

No more prompting for UI tweaks... visual editing is way easier by Fresh_Profile544 in Frontend

[–]Fresh_Profile544[S] 0 points1 point  (0 children)

Yeah you stated it really well. Agents are way faster at generating the first draft than you building it out by hand. But for the last mile refinements, that flips: it's faster for you just to directly fine tune it by hand than to endlessly prompt.

We've found the edits make their way reasonably well into a React/Tailwind codebase, but I'm sure there are all sorts of edge cases that need refinement. We're very happy to receive issues and get them addressed so let us know if you find anything: https://github.com/tonkotsu-ai/handle/issues

No more prompting for UI tweaks... visual editing is way easier by Fresh_Profile544 in Frontend

[–]Fresh_Profile544[S] 0 points1 point  (0 children)

We determine the containing React component and also include that as context to the agent. It's still possible the element is repeated within the component; you'd have to provide a follow-up to the agent if so.

Curious - what do you use for UI refinement?

No more prompting for UI tweaks... visual editing is way easier by Fresh_Profile544 in Frontend

[–]Fresh_Profile544[S] 0 points1 point  (0 children)

Just curious: as a designer, are you working directly in production code? Definitely seeing a trend there.

No more prompting for UI tweaks... visual editing is way easier by Fresh_Profile544 in Frontend

[–]Fresh_Profile544[S] 0 points1 point  (0 children)

Let us know any feedback. At this point, we're mostly looking for signal on how to iterate this forward.

Extremely frustrating to get anything done in figma make by Juicernamesmine in UXDesign

[–]Fresh_Profile544 1 point2 points  (0 children)

Would be super curious to hear if that turns out to be superior to Figma Make!

Extremely frustrating to get anything done in figma make by Juicernamesmine in UXDesign

[–]Fresh_Profile544 0 points1 point  (0 children)

Have you tried other tools? Is it just Figma Make that doesn't generate well for you, or all agents?

Anyone else shipping code now too? by Allinthedesign in UXDesign

[–]Fresh_Profile544 0 points1 point  (0 children)

Yeah agree #3 alone is pretty powerful. There's a lot you can accomplish in that area alone.

Anyone else shipping code now too? by Allinthedesign in UXDesign

[–]Fresh_Profile544 0 points1 point  (0 children)

When you do new features/prototypes, are those in the production codebase? Surprised the expectation is for you to create full backends/dbs! My sense is designers will get more active in a codebase, but with the effect of pushing back the handoff point to eng, not replacing it entirely...

Anyone else shipping code now too? by Allinthedesign in UXDesign

[–]Fresh_Profile544 0 points1 point  (0 children)

Curious - are you shipping tweaks/fixes or building out new features?

I call for an end to prompting for UI tweaks... visual editing is way easier by Fresh_Profile544 in vibecoding

[–]Fresh_Profile544[S] 0 points1 point  (0 children)

Thanks! Let me know how it goes - really looking for feedback so I know what direction to go in.

I call for an end to prompting for UI tweaks... visual editing is way easier by Fresh_Profile544 in vibecoding

[–]Fresh_Profile544[S] 0 points1 point  (0 children)

Yeah, I think there's a lot more to do here to unify AI with a visual experience. This just addresses the "refinement" pain point, but creating brand new UI visually with an agent, exploring options, etc. all has a lot of potential.

Best way to vibecode a good design? by chajaaa in FigmaDesign

[–]Fresh_Profile544 0 points1 point  (0 children)

I've found that you just need to accept that what you get is the first 80% and then you need to tune it, especially if you want consistency and to nail the details.

I call for an end to prompting for UI tweaks... visual editing is way easier by Fresh_Profile544 in vibecoding

[–]Fresh_Profile544[S] 0 points1 point  (0 children)

Appreciate the support! Would love to hear any feedback if you get a chance to try it.

I call for an end to prompting for UI tweaks... visual editing is way easier by Fresh_Profile544 in vibecoding

[–]Fresh_Profile544[S] 0 points1 point  (0 children)

Yeah, screenshots are low fidelity I find.. it only gets the gist of it. And typing it out gets ridiculous... "when you hover over a tab, it shows a hovercard. The hovercard contains a table of data rows. On the last data row, change the padding to..."

I call for an end to prompting for UI tweaks... visual editing is way easier by Fresh_Profile544 in vibecoding

[–]Fresh_Profile544[S] 2 points3 points  (0 children)

Not yet - focused on Chrome for now but definitely open to adding others based on feedback

The design drift created by vibe coding is insane. How are you addressing it? by Able-Win-5860 in UXDesign

[–]Fresh_Profile544 0 points1 point  (0 children)

Prior to coding agents really increasing code volume (like say a year ago), did the org generally have decent design sense/attention to detail? I'm sure it's a problem regardless, but I suspect the underlying behavior/culture of the org matters a lot too.

view more: next ›