Your app looks generic because the AI had nothing to copy. So it built the average of every app it has seen. Give it one design doc, your own components and a bar every screen has to clear, and your app stops looking like everyone else's. The free AI starter kit we build our own products with does this on every screen.
Why AI-built apps all look the same
When you ask for "a clean modern dashboard", the AI fills every gap with the most common choice. That's how you end up with the same font, the same purple gradient, three rounded cards and a big centered headline. Asking it to "make it nicer" doesn't help, because nicer just means more of the average.
What people feel as generic is usually something else, though. It's a button that does nothing for a second after you tap it, a list with no empty state, or spacing that changes from screen to screen. Those come from screens being built one at a time with nothing tying them together.
Write one design doc
Put one file in your project that says how your product looks and feels: your type scale, colors, spacing, how much motion, what a card looks like and what you never do. Keep it short and specific. "Generous whitespace" means nothing to the AI, but "16px inside cards, 32px between sections" does.
Point your AI at it in your project instructions (CLAUDE.md for Claude Code, rules for Cursor) so it reads the doc before every UI change. Keep it to one doc, because the same rule written in three places drifts.
Build every screen from your own components
Generic apps are full of one-off components. The AI makes a new button for the pricing page, another for settings and a third for onboarding, each slightly different.
Tell it to reuse or extend what's already in your component library, and to add any new piece to the library before using it on a screen. When each visual behavior has one owner, a fix in one place fixes every screen.
Finish every state
This is the biggest gap between a weekend project and an app that feels expensive. For every screen, check loading, empty, error, disabled, hover and focus, in light and dark mode, on a phone and on a wide screen. AI skips these unless you ask, and your users run into them straight away.
Two checks catch most of it:
- Every tap answers at once. The control shows it was pressed, then that it's working, then that it's done. A silent pause followed by a jump feels broken even when it works.
- Every result has a next step. After a success or a failure, the next action is right there, so nobody hits a dead end.
Cut until it's quiet
Products that look expensive say less. Cut words from buttons and headings, use an icon where the meaning is obvious, and use columns on desktop instead of one long stacked list. Drop any decoration that doesn't help someone get the job done.
Spot the generic look and fix it
| What you see | What's missing | Fix |
|---|---|---|
| Every page has a different button | One owner per component | Rebuild from your component library |
| The app freezes for a second after a tap | A pressed and working state | Show feedback on the control straight away |
| A blank screen when there's no data | An empty state | Say what goes here and give the next step |
| Spacing jumps between screens | A spacing scale | Put exact values in your design doc |
| The same purple gradient as every AI app | A design to copy | Write your colors and type into the doc |
Turn a few notes into one rule
When a screen looks off, don't just patch that screen. Look at every screen side by side, note what's wrong on a few of them, and turn those notes into one rule in your design doc, like "the same row height in every list". Then apply it everywhere, and the next round of notes gets smaller.
Get the design bar we use
We put all of this into the AI starter kit we build our own products with. Its design set gives your AI the bar every screen has to clear, builds from your own components, and turns your notes on a few screens into fixes on all of them. It works with Claude Code and Codex. Get the starter kit free on GitHub.
Questions
Why do AI-built apps all look the same?
With no design to follow, the AI picks the most common choices it has seen, so you get the same font, purple gradients, rounded cards and a big centered headline. Give it your own design doc and components and it has something better to copy.
Can I fix a generic-looking app without a full redesign?
Yes. Most of the generic feel comes from missing states, uneven spacing and one-off components. Write one design doc, rebuild screens from shared components, and check every screen against the same bar.
Does this work with Lovable, Bolt, Cursor and Claude Code?
Yes. Any tool that reads a file in your project can follow a design doc. Claude Code and Cursor read it on every change, so the rules hold across the whole app.
Originally published at wednesday.is.
Top comments (0)