TL;DR
- AI builders average their training data, so every site lands on the same Inter, gradient and rounded-card look
- Adjectives like "unique" or "premium" only shift the average; real constraints (tokens, type, radius, layout) change the output
- Fix it in about an hour: lock the copy, replace the visual language, add a motion layer, then make four manual edits
You shipped a site in Lovable, v0, Bolt or Cursor in an afternoon, and now you can't stand to look at it. Nothing is broken. It just looks like every other AI-built site: Inter everywhere, a soft gradient hero, rounded-2xl cards, pill buttons, a three-column feature grid, and a page that doesn't move. People call it AI slop. It has a structural cause, and you can fix it in about an hour without rebuilding anything.
Why every AI-built site looks the same
Language models produce the most likely continuation of a prompt. Ask one for "a SaaS landing page" and it doesn't pick one reference and copy it. It blends thousands of them and returns the middle. That middle is dominated by a few very influential sites (Stripe, Linear, Vercel, the Tailwind UI templates) and the long tail of sites that imitate them.
So the AI look isn't ugly. It's competent and average, and it averages the same way for everyone:
Each default is fine on its own. The problem is that they're fine in exactly the same way as everyone else's.
Why "make it unique" doesn't work
The first instinct is to fight the average with adjectives: "make it premium", "make it different", "make it stand out". That moves the model to a slightly different average. "Premium" becomes a darker palette, a serif heading and more whitespace. It's still the middle of a distribution, just a more expensive-looking one.
Style comes from constraints the model wouldn't have picked on its own. A real design team chooses colors, spacing and type pairings the average wouldn't choose, and each choice pulls the result away from the middle. Your AI tool has no constraints beyond "landing page" plus your copy, so it returns the middle. Give it different constraints and the most likely page changes with them.
The two layers of AI slop
AI slop on a website comes in two layers, and they need fixing in this order.
Fix the visual layer first. Smooth motion on a generic design just makes a generic design move.
Step 1: lock your copy
The most common reason a redesign goes wrong in Lovable is that "make it look better" also rewrites every sentence. The model regenerates whole components, and components include their text. Before any design prompt, paste this:
Do not modify any user-visible text. Headings, body copy, button labels, testimonials and pricing copy are locked. Only change visual properties: tokens, component styling, layout and spacing.That one instruction prevents most copy regressions. When the redesign is done, open the old and new versions side by side and read the headlines and buttons in order. Anything that changed without your approval is a regression to fix before shipping.
Step 2: replace the visual language
Ask for token-level changes, not "a redesign". Be specific about what replaces each default:
You can write these by hand, or paste in a ready-made design system pack such as Rottoways, which includes a renovation prompt that keeps your copy untouched. Either way, this step removes most of the AI-made feeling. The site stops looking generated and starts looking opinionated.
Step 3: replace the motion
Once the design is coherent, the next thing the eye notices is that nothing moves, or that everything moves the same way. AI tools need explicit motion rules to do better: spring values per interaction type, stagger on lists, coordinated entrance and exit, and a reduced-motion fallback.
A motion prompt gives the model those rules in one paste. Our UI Motion Prompts cover hover, press, entrance, route transitions and micro-interactions, each with the React code they produce, and they work in Claude Code, Lovable, Cursor and Codex. For the step-by-step version, see add animations to vibe-coded apps.
Step 4: four edits the AI won't make for you
Even after the design system and motion paste-ins, four small manual edits push the site further from the default:
Check the result
Send the site to three people who haven't seen it and ask: "Does this look AI-generated?" Better still, ask them to circle anything that looks like every other AI site. Common circles are rounded-2xl on every element, the same gradient on every button, three-column grids regardless of content, and identical avatar shapes in every testimonial.
If two of the three still say it looks generated, you've probably kept the default font, the default radius or the default three-column grid. Go back to step 2.
Don't rebuild
The usual reaction to a generic AI site is to "rebuild it properly": weeks of Figma, weeks of implementation, and a result that ships too late to matter. The point of vibe coding is speed. Keep it by upgrading the inputs instead of redoing the output:
That's about an hour from AI default to a site that looks like yours.
UI Motion Prompts fixes the motion layer in Claude Code, Lovable, Cursor and Codex. Pair it with a real design system for the visual layer, and your AI-built site stops looking like everyone else's.
More articles
Best Vibecoding Tips: Add Animations to Vibe-Coded Apps
The shortest path from static AI output to apps that feel alive: where to add motion, what spring values to use, and how to make it consistent across components.
Animated Icons in React: 5 Ways to Add Them (CSS, SVG, Motion, Lottie, Rive)
How to add animated icons to a React or Next.js app: CSS hover transitions, animated SVG, Motion, Lottie and Rive, with code for each and a guide to picking the right one.
Icon Hover Animation with CSS: 8 Effects with Copy-Paste Code
Eight CSS icon hover effects (spring scale, tilt, bell ring, wiggle, bounce, spin, stroke draw-on and colour sweep) with copy-paste code that stays smooth and accessible.