alt Hacker NewsI created pages with Claude before and it's very very obvious when you see one. From the font choice to the color palette, and the style of the boxes. In fact if anyone has an effective prompt that says "please don't make this look like the average Claude page" please post it!
Replies
Not sure that's necessarily any bigger a deal than when every Web site had the "Bootstrap look."
Anthropic's own frontend-design skill attempts to do that. You can install it in Claude Code, or you can tweak it to be closer to your own style:
https://github.com/anthropics/claude-code/blob/main/plugins/...
But what I find works best is to point Claude at a design system documentation website (your own company's or another public source) and tell it to use that design style. It usually does OK, and the results are usually much more in line with that style and not as Claude-y.
Just give it actual ideas of what you want instead of "make me a web page". Garbage in garbage out.
I've had some luck giving either an example website to ape or listing out a particular era, monkey see monkey do seems to help a bunch.
I've done each of the 3 for side projects below to pretty good effects.
> This website will be run by IE6 and Windows Mobile 6, so use no dependencies, semantic HTML, a 3-pane layout, and only use JS (es3!) where absolutely necessary (and where necessary, put the script at the end of the body).
When I'm not specifically targeting support for retrocomputers I do something like this, then iterate until it looks right.
> Go look at Dokuwiki, django defaults, and common web 2.0 color schemes, use those for UI inspiration. Keep a 3-pane desktop-first layout, but enable mobile responsiveness with media queries. Use semantic html5 and prefer older boring solutions like surgical jquery or htmx-style islands of interactivity where needed, otherwise do not bring in dependencies without my say so.
And finally, if I'm doing a web app that I'm vibing out with the web stack because I want it one-shotted and not trying to do a good rust core with strong ports/adapters API surface for web or native client callers, I do something like this:
> This is a local web app, the frontend, backend, and desktop are all on the same machine. Use naive and simple development patterns that you document the style as you go, pick a boring web framework and use it idiomatically, but remember that some tricks that are intended to keep network round trips down are not as necessary because network penalties are not as bad as real traffic.
Granted, the above I don't like as much, but it does produce more 'modern' looking sites by default.