How to Make Your Website Not Look AI-Generated: 9 Tells From Slopstrap's CSS
Mike Lacher built a CSS framework whose only job is to make your site look like an LLM wrote it in one prompt. It's called Slopstrap, it's at v4.2, and the stylesheet header claims it was "Scientifically averaged from 40
Mike Lacher built a CSS framework whose only job is to make your site look like an LLM wrote it in one prompt. It's called Slopstrap, it's at v4.2, and the stylesheet header claims it was "Scientifically averaged from 400,000+ Tailwind SaaS landing pages!" It's close to 300 points on Hacker News, and nobody there really disputed the look. The main complaint was that it parodies last season's slop.
So if you want your website to stop looking AI-generated, read Slopstrap's source. It's the most honest checklist of vibecoded design tells I've found, because every tell has a class name and most of them have a hex code.
Below are the nine I'd strip first, why models keep producing them, and how to undo each one in plain CSS or Tailwind v4.
Why every AI-generated site looks the same
Models produce the average of what they were trained on, and for a few years the average landing page was Tailwind with default colors, Inter, a dark background and some cards. Slopstrap's variables are commented like a confession: --slop-indigo: #6366f1 is "Default Tailwind indigo-500!", --slop-bg: #030712 is "Tailwind gray-950 void!", and --slop-text-muted: #94a3b8 is "Murky slate-400 body copy!"
Tailwind's co-founder Adam Wathan joked about it himself. On August 7, 2025 he posted on X that he'd "like to formally apologize for making every button in Tailwind UI use bg-indigo-500 five years ago, which caused every AI-generated interface on Earth to turn indigo." The theory that one default flooded the training data is plausible, but nobody has proven it. Either way, if you don't make a decision, the model makes the most common one for you. Most of the fixes below come down to making one.
The checklist: 9 AI design tells and how to undo them
1. Gradient text in the hero
Slopstrap's .slop-text-gradient goes from #ffffff to #c084fc to #38bdf8, and the CSS calls it "The #1 AI Tell!" I agree. A headline with bg-clip-text text-transparent bg-gradient-to-r from-indigo-500 to-purple-500 is the fastest way to look generated.
Fix: solid text in one color. If you need emphasis, use a heavier weight or tighter letter-spacing.
h1 { color: var(--ink); font-weight: 700; letter-spacing: -0.02em; }
2. Indigo, violet and purple accents
#6366f1, #8b5cf6, #a855f7. If your primary button is any of these, visitors have already seen it on a hundred other launch pages. In Tailwind v4 you can delete the default palette so nothing picks it up by accident:
@import "tailwindcss";
@theme {
--color-*: initial;
--color-ink: #1c1917;
--color-paper: #fafaf9;
--color-brand: #c2410c;
}
I ran this through the v4 CLI: bg-indigo-500 now generates no CSS at all, while bg-brand and text-ink work. It fails silently, so you'll see an unstyled button, not a build error. Arbitrary values like bg-[#6366f1] still get through, so grep for those in review. Pick the brand color from something real: your logo, the product, a photo you actually own.
3. The dark void with glowing orbs
Gray-950 background, a 48px grid overlay, and four blurred blobs (.slop-orb-purple, -cyan, -pink, -emerald) at blur(110px). It looks like a crypto launch from 2021.
Fix: a light or mid-tone background with real content in the hero, like a product screenshot, a photo or a code sample. If there's nothing to show yet, that's the actual problem, and a purple blob won't hide it.
4. Glassmorphism cards
Translucent slate surfaces, backdrop-filter: blur(16px), a 1px border at 10% white (rgba(255, 255, 255, 0.1)), a 4px lift on hover, and a .slop-card-nested class for cards inside cards. Frosted glass only means something when there's an interesting thing behind it. On a flat dark background it's a gray rectangle that costs GPU time.
Fix: solid surfaces, a real border, and no hover lift on things that aren't clickable.
.card { background: var(--paper); border: 1px solid #d6d3d1; border-radius: 6px; }
5. Emoji as icons
Slopstrap's .slop-icon-box is a 48px rounded square holding an emoji, and .slop-sparkle prepends "✨ " to text. Three-column feature grid, each card topped with ⚡ or 🚀 or 🔒. You know the page.
Fix: use one icon set at one stroke width, or drop icons and write a better heading. A sentence that says something specific does more for a feature card than any icon.
6. Everything is rounded-2xl and everything is a bento
The radius scale runs from 0.5rem to 1.75rem plus pill, and the comment reads "Sharp corners are strictly forbidden!" Every section gets the same card, radius and padding, and when in doubt, a 12-column bento grid (the docs heading for that one is unprintable here, but it ends with "Put It In a Bento Grid").
Fix: pick one small radius (4–6px) and use it everywhere. Then vary the sections. A pricing table, a long paragraph, a full-width image and a FAQ shouldn't share a layout just because they're all "content".
7. One italic serif word in a sans headline
"Build the future of work", with future in Instrument Serif italic at 1.12em inside an Inter headline, often with a hand-drawn marker underline under another word. HN user InexSquirrel pointed at "the individual word underline and serif-italic usage" as part of what makes these pages feel LLM-made, while adding that "individually most of these things are fine" and it's the aggregate that gives it away.
Fix: one typeface for headings, one for body, no mid-sentence font switches. If you want a serif, commit to it for the whole headline.
8. Fat colored left borders
--slop-border-width: 4px, in seven colors, plus a gradient and an animated rainbow version. It's the callout style models reach for on every "Note" and "Pro tip". skerit thought the framework was "kinda neat, except for the fat left borders."
Fix: if you need a callout, use a background tint and a label. If you have five callouts on one page, you need fewer callouts.
9. Fake proof: status dots, eyebrow pills, stats and logo walls
A pulsing green dot labeled "All Systems Operational" next to "NO BACKEND REQUIRED". An eyebrow pill reading "✨ Introducing v2.0 — Now with Agentic Workflows →". A counter showing "14.8M+" over the label "Users, probably". A marquee of OpenAI, Anthropic, Vercel and Stripe logos. Testimonials from "Dr. Sarah Chen (VP of Product at NexusAI)".
This is the one that costs you trust, because it's the one that's lying. Remove every number you can't source, every logo of a company that isn't a customer, and every status indicator that isn't wired to anything. One real quote from a real user beats six invented ones.
Your copy gives it away too
Slopstrap's own hero says "It's not just a CSS framework — it's a load-bearing accelerant". Readers spot that "not just X, it's Y" construction faster than a gradient, along with emoji in every heading, "10x faster" and "at scale". Read your headings out loud. If one could sit on any other product's page unchanged, rewrite it.
A prompt rule that stops your coding agent from doing this
If you generate UI with an agent, tell it what's banned. quinncom replied to the thread with "now I can show my agent and say 'these design tropes are forbidden'." Something like this in your project rules:
Design constraints:
- No gradients on text. No purple, violet or indigo unless I ask.
- No backdrop-filter, no blurred background blobs, no grid backgrounds.
- No emoji in headings, buttons or as icons.
- Border radius: 6px everywhere. No pill buttons.
- One font family for headings. No mixed serif/sans in one line.
- No invented stats, testimonials, logos or status indicators.
Leave a TODO placeholder instead.
- Use only colors defined in @theme.
The last line does the most work, because with the @theme reset from tell #2 the build enforces it and you're not relying on the model's memory. Only arbitrary values slip past.
This checklist is already out of date
The sharpest comments in the thread said Slopstrap is aiming at the old look. ChrisArchitect wrote "This isn't even it, this is like the previous incarnation of TailwindCSS themed things," and said the current standard is "small type sizing, serif fonts and beige / tan color schemes." s-zeng said it was "representative of slop sites a few months ago, but no longer of the current generation slop."
So if you follow this list and land on a cream background, Instrument Serif and tiny gray text, congratulations: you're on the newer slop. The tells move every time the default model's taste moves. A ban list helps, but what protects you is real content and a few design decisions you can explain. Gradients and rounded corners are fine on their own. They turn into a tell when they're on the page because nobody chose anything.
One contrarian point from the thread is worth keeping. robbles wrote, "Honestly, at least the AI slop designs have decent contrast and font sizes," and plenty of pre-LLM sites were worse. g-b-r disagreed in a reply, saying they "typically have minuscule font sizes, and have terrible contrast". Both have a point. Slopstrap's slate-400 body text on gray-950 is a parody, but I'd still take a generated page over a hand-built one with 12px light-gray body copy. Looking generated hurts your brand, but being unreadable hurts your users, which is worse.
Which design tell makes you close a tab because it screams "AI built this"? And are you already sick of the beige?
Sources
Originally published by Dev.to AI. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.