Why AI-generated interfaces all look the same, and how to make yours not
Ask any model for a landing page and you get the same purple gradient, three cards and rounded everything. Where that look comes from, and what stops it.
Ask for a landing page with no other instruction and you can predict the result before it renders: a violet-to-blue gradient behind a centred headline, three feature cards in a row with an icon, a title and two lines each, every corner rounded to the same radius, and a primary button in the same colour as half the page. It is not wrong. It is just nobody's.
The generic look is an average, not a style
A model asked for UI with no brief reaches for what is most common, because most common is the safest guess. The result is a composite of a great many products, which is exactly why it looks like none of them in particular. The fix is not a cleverer model. It is a brief that says what this product is, and just as importantly, what it is not.
Ten tells that a screen was generated
- A purple-to-blue gradient nobody chose.
- Every heading at the same weight, so nothing on the page is arguing.
- Emoji standing in for icons.
- Three identical cards in a row, each an icon, a title and two lines.
- One border radius on everything, whatever its size.
- Shadows used as decoration rather than to mean one thing is above another.
- Copy that could describe any product: unlock, empower, next level.
- The accent colour on more than the one action that matters.
- Animation that loops forever for no reason.
- A stock illustration of people at laptops where the product should be.
None of these is a bug on its own. Together they are the reason a reader decides, in about a second, that nobody designed this page.
What actually stops it: decisions written down
Every product that looks designed has made a small number of hard decisions and kept to them. Two colours and never a third. A serif for headlines and a monospace for every number. One accent, used on the primary action and nowhere else. Those decisions are cheap to write down and expensive to rediscover, and a model will not rediscover them on its own.
| Leave it to the model | Decide it once |
|---|---|
| Palette | Named tokens, and which colour means what |
| Type | Which face for display, reading and numbers |
| Accent | Exactly where it is allowed to appear |
| Radius and depth | Values by object size, not one for all |
| What is off limits | A short list of looks this product never uses |
The last row is the one people skip and the one that does the most work. A rule like no gloss, no glass, no neon removes a whole family of generic answers before Claude writes a line.
Put the decisions where Claude reads them every time
A prompt disappears at the end of a session. A Claude Code skill does not: its instructions are loaded whenever the work matches, in every session, for everyone on the project. That is why the decisions belong in a skill rather than in a message you have to remember to paste. How to build one is in give Claude Code your design system as a skill.
We sell three of them, each written from a live product and shown against it: Glass Instrument UI for dark, premium interfaces, macOS Native Dark UI for apps that should feel native on a Mac, and Editorial Ledger UI for pages that need to look credible rather than techy.
Questions
Why does AI-generated UI look generic?
Because a model with no brief picks the most common answer, and the most common answer is an average of every landing page it has seen. Nothing in the request tells it what this product is not, so it produces what most products are.
Will a better prompt fix it?
For one screen, sometimes. It does not hold across a project, because the prompt is gone by the next session. The look has to live somewhere Claude reads every time it builds UI, which is what a design skill is.
Is a design system skill the same as a UI component library?
No. A component library gives you parts. A design system skill tells Claude which parts to use, what they look like, and what is off limits, so the screens it writes next week match the ones it wrote today.
Keep reading
Or skip the afternoonand drop one in.
Every skill in the catalogue is a folder you drop into your skills directory. Each ships with its design rules, worked examples and a troubleshooting table, and downloads the moment you pay.