Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Slightly reducing the sloppiness of AI generated front end

envs.net

Post reply on HN
Print view View original

81–90 of 147 posts

Re: Slightly reducing the sloppiness of AI generated front end

#81

Post by Retr0id »

smusamashah wrote: post #66
lherron wrote: post #65

You really have to a) use Opus and b) use the frontend-design skill for decent results. https://github.com/anthropics/claude-code/blob/main/plugins/...

I have seen so many brown sites that look all the same, all designed by this thing most likely. So no.

Agreed. It's not that the designs it produces are bad necessarily, they're just very same-y. People often talk about the bootstrap era, but that wasn't as bad because bootstrap wasn't so strongly associated with low-effort slop projects (low-effort on the frontend maybe, but not the project as a whole).

Re: Slightly reducing the sloppiness of AI generated front end

#82

Post by stefan_ »

lherron wrote: post #65

You really have to a) use Opus and b) use the frontend-design skill for decent results. https://github.com/anthropics/claude-code/blob/main/plugins/...

I keep getting Claude telling me to "use the frontend-design skill!", and this is it?

> NEVER use generic AI-generated aesthetics like overused font families (Inter, Roboto, Arial, system fonts), cliched color schemes (particularly purple gradients on white backgrounds), predictable layouts and component patterns, and cookie-cutter design that lacks context-specific character.

> brutally minimal, maximalist chaos, retro-futuristic, organic/natural, luxury/refined, playful/toy-like, editorial/magazine, brutalist/raw, art deco/geometric, soft/pastel, industrial/utilitarian

> React, Vue

Sorry, but this is garbage.

Re: Slightly reducing the sloppiness of AI generated front end

#84

Post by re-thc »

Retr0id wrote: post #81
smusamashah wrote: post #66

Earlier quoted context omitted.

I have seen so many brown sites that look all the same, all designed by this thing most likely. So no.

Agreed. It's not that the designs it produces are bad necessarily, they're just very same-y. People often talk about the bootstrap era, but that wasn't as bad because bootstrap wasn't so strongly associated with low-effort slop projects (low-effort on the frontend maybe, but not the project as a whole).

> but that wasn't as bad because bootstrap wasn't so strongly associated with low-effort slop projects (low-effort on the frontend maybe, but not the project as a whole)

They were, at least for that era. Just maybe not at AI-scale.

Re: Slightly reducing the sloppiness of AI generated front end

#85

Post by viccis »

lherron wrote: post #65

You really have to a) use Opus and b) use the frontend-design skill for decent results. https://github.com/anthropics/claude-code/blob/main/plugins/...

I've had better results with this, when it comes to functional UIs rather than marketing sites: https://github.com/Dammyjay93/interface-design

Found it on reddit after Claude produced the lamest looking generic forms for all the pages on a project I had it build. This did a pass over it and basically fixed it all one shot.

Re: Slightly reducing the sloppiness of AI generated front end

#87

Post by mschuster91 »

kordlessagain wrote: post #71
mynameisvlad wrote: post #47

Earlier quoted context omitted.

Is that a problem?

HN has huge issues right now with AI generated code or design. I have a friend who is a graphic designer/market strategy guy and he's been using Anthropic to build sites and even did an agent on his own page that helps guide the user through onboarding. I reviewed the code a few times and gave him some tips and it looks pretty good and works flawlessly. He maintain a lot of customer's sites (design wise) and all the…

> HN has huge issues right now with AI generated code or design.

Yes, because for those of us who enjoy scrolling through /new despite the deluge of spam that has always been a problem, we now have to sift through not just the obvious AI generated stuff that we can discard after a few sentences, but also the stuff where it only becomes obvious after already sinking in 10, 15 minutes of your time that it is undisclosed AI slop with a touch of human effort (or a non-OpenAI/Anthropic model).

And there have been cases here where someone submitted AI vibed stuff and in the comments it became pretty obvious they had zero understanding of what they were doing. The amount of collective time wasted in this thread is absurd.

Personally, I'd love to see HN adopt something like r/amateurradio:

> Moderation feels that this is the best course of action in response from the community. It prevents people from just shoving out stuff they vibecoded the night before but allows for those apps that gain traction a chance to be shared.

[1] https://www.reddit.com/r/amateurradio/comments/1t6n8xk/updat...

Re: Slightly reducing the sloppiness of AI generated front end

#89

Post by PaulHoule »

iSnow wrote: post #16

Obviously this is a personal preference, but the multiple layers of beveled grey on the Qt UI is not something I like, as it forces a lot of grouping on the eye where it doesn't serve any purpose. I would go with the original, Apple or the Win11 one. Material would be good, what's with the lavender shades? I always try to reduce the palette: say two background shades max, no drop shadows, only as many foreground colo…

At this point I dunno if Win11 has an “original” UI. Up until Win 8 Microsoft kept introducing new widget sets. I think the official answer for how you are supposed to develop desktop apps is “use Electron” so far as I can tell… or better yet make a web application.

Re: Slightly reducing the sloppiness of AI generated front end

#90

Post by PaulHoule »

re-thc wrote: post #84
Retr0id wrote: post #81

Earlier quoted context omitted.

Agreed. It's not that the designs it produces are bad necessarily, they're just very same-y. People often talk about the bootstrap era, but that wasn't as bad because bootstrap wasn't so strongly associated with low-effort slop projects (low-effort on the frontend maybe, but not the project as a whole).

> but that wasn't as bad because bootstrap wasn't so strongly associated with low-effort slop projects (low-effort on the frontend maybe, but not the project as a whole) They were, at least for that era. Just maybe not at AI-scale.

Like you had to know a little HTML in the bootstrap era. I made what I thought was a pretty nifty landing page but I got endless complaints because “it looked like bootstrap”
Post reply on HN