21–30 of 67 posts
Earlier quoted context omitted.
Same thing would happen if you had asked a human intern.
This is almost a meme reply on HN: absolving the LLM by comparing it to an inexperienced human.
I think user interface design is a very cursed task for an LLM. They are skilled at giving you high quality CSS and design patterns, but they're horrible at actual layout and composition. I can say "add a status strip to the form with blah blah" and it will work perfectly. However if I ask for something like "a modern UI for gathering customer details" I'm guaranteed to get a pile of shit.
If you want good results with a specific output, the operator needs to be giving specific instructions. Asking for vague results will only give you something that vaguely resembles the thing you wanted, but it’s not going to produce perfect results the first time.
1/ Use a standard CSS library - Tailwind 2/ Use a common React component library such as Radix UI (don't reinvent the wheel) 3/ Avoid inventing new UI patterns. 4/ Use Storybook so you can isolate all custom UI elements and test/polish them in all states 5/ Develop enough taste over the years of what is good UI to ask CC/Codex to iterate on details that you don't like.
Earlier quoted context omitted.
Same thing would happen if you had asked a human intern.
[dead]
Spec it out providing your needs, objectives, guidelines etc and you'll get better output... exactly like with an LLM.
Earlier quoted context omitted.
Same thing would happen if you had asked a human intern.
This is almost a meme reply on HN: absolving the LLM by comparing it to an inexperienced human.
Everyone who uses LLMs knows that it’s an iterative process where you need to provide specific instructions. It’s only the LLM naysayers who think that pointing out that “Generate a modern UI for me” doesn’t create perfect results on the first pass is an indictment of LLMs.
1) Using the prompt provided by anthropic here to avoid the typical AI look: https://platform.claude.com/cookbook/coding-prompting-for-fr...
2) If I don't like something, I will copy paste a screenshot and then ask it to change things in a specific way. I think the screenshot helps it calibrate how to adjust stuff, as it usually can't "see" the results of the UI changes.
Not to self-promote, but I am working on what I think is the right solution to this problem. I'm creating an AI-native browser for designers: https://matry.design
I have lots of ideas for features, but the core idea is that you expose the browser to Claude Code, OpenCode, or any other coding agent you prefer. By integrating them into a browser, you have lots of seamless UX possibilities via CDP as well as local filesystem access.
Since LLMs are almost AGI, all you have to do is feed one a screenshot of a few UIs that you like and ask it to duplicate it for your own application, saying "Please style the application like this, while observing best practices for internationalization, assistive technologies and Fitts' Law." If you have problems with this workflow, it's because you're not using an-up-to-date LLM. All the old ones are garbage.
I conjure the fury of one thousand suns and unleash my swarm of agents to complete the task with precision and glory.