> Asked for frontend work without design direction, Claude Opus 5.5 falls back on a few default styles, and a general instruction such as "avoid a generic AI look" mostly swaps one default for another. It responds well to instructions that name specific patterns to avoid, as in the following example. Work iteratively: check which styles the first result used instead, and extend the list if needed.
I hardly ever read tips for prompting etc. because things change too quickly, the writeups are kindof big. Glad I read this one, because I often did exactly what they assume users would do. I write "don't make it look like generic ai slop" and that seemed to work nicely. Now I know why there was still a chance of seeing similar styles across apps. I reckon doing some manual work in terms of scouting dribbble/behance for nice layouts will yield better results.
I really find it strange though. How does an AI know what "AI slop" is? Is it reasonable to tell a child not to do "wrong" if you haven't told them what things are wrong?
Bishonen88 · · focus · HN ↗
> Asked for frontend work without design direction, Claude Opus 5.5 falls back on a few default styles, and a general instruction such as "avoid a generic AI look" mostly swaps one default for another. It responds well to instructions that name specific patterns to avoid, as in the following example. Work iteratively: check which styles the first result used instead, and extend the list if needed.
I hardly ever read tips for prompting etc. because things change too quickly, the writeups are kindof big. Glad I read this one, because I often did exactly what they assume users would do. I write "don't make it look like generic ai slop" and that seemed to work nicely. Now I know why there was still a chance of seeing similar styles across apps. I reckon doing some manual work in terms of scouting dribbble/behance for nice layouts will yield better results.
skeledrew · · focus · HN ↗
byzantinegene · · focus · HN ↗
Sharlin · · focus · HN ↗