undefined | Better HN

0 pointsmarcus_holmes1mo ago0 comments

This is my experience too, but with all other aspects of the application. If you only loosely describe it, it comes out as a mess. You have to know what you're building to get the LLM to actually build something decent. I don't think this is purely a visual or design constraint.

0 comments

3 comments · 1 top-level

embedding-shape1mo ago· 2 in thread

When I'm using agents for programming, I can have a AGENTS.md outlining exactly what requirements, guidelines and constraints all the code need to follow, and the agent (codex in my case) will pretty much nail that.

I've tried doing the same for design work, just really outlining exactly how the UI and UX needs to look and work, but for some reason it struggles a whole bunch with it, regardless of how clear I am. Maybe it's I'm just worse at explaining and describing what UI and UX I'm actually after though, I suppose.

marcus_holmesOP1mo ago

I once worked at a startup where the CEO was originally a designer. He once spent two days huddled with the main designer for the product, trying to pick exactly the right font for the product. I have no idea how you'd have that kind of discussion with an LLM.

But then, I would not spend more than five minutes on this decision, so I'm probably the wrong audience for this ;)

embedding-shape1mo ago

Used to work in a designer-heavy company doing frontend work, one of the founders could spot by naked eye if you got the alignment of something wrong by 2-3 pixels during the reviews.

The UI and UX of the product was amazing, and took some time to get used to actually delivering pixel-perfect designs across three different browsers, but fun times regardless :) Probably takes a certain individual to enjoy that sort of experience though.

j / k navigate · click thread line to collapse