Test18 November 20267 min read

I tested 3 "anti AI slop" design skills on the same page. Only one changed the design

Four screenshots of the same coffee roaster landing page. A, C and D share a cream background, a serif headline with an orange italic phrase and a picture of a cup. B has a dark teal hero, tall condensed type and a chalkboard list of this week's coffees.
The first screen of each version at 1440 px wide. Score = signs of AI slop out of 10.

You can usually tell when a website was made by AI. The same cream background, the same serif headline with one word in italics, the same row of cards with an emoji on top. People call it "AI slop". Skills are text files you give to a coding agent to change how it works, and some of them promise to fix exactly this. So I tested three.

The idea came from a post by @BenjaminUIX on X listing "10 skills that kill AI slop" (it has about 7,600 likes). The post ends with good advice: "Install 2 or 3, not all 10." But which 2 or 3? The post doesn't show what the skills actually do. So I picked three from the list that are plain text instructions and ran the same job with each.

The test

The brief was one sentence, the kind a busy person would really type: build a single-file HTML landing page for Harbour Coffee Roasters, a small local coffee roaster with a cafe and an online shop for beans. No details about colours, hours or prices. The AI had to decide everything.

I built it four times. Each version was made by a fresh agent (Claude Opus 5.5 in Claude Code) that saw only the brief, plus one skill file for B to D. No agent could see the others' work. The same rules applied to all four: one HTML file, no photos (only CSS, inline SVG or emoji), and Google Fonts allowed.

VersionWhat the agent gotWhat the skill is about
AThe brief onlyNothing, this is the baseline
BBrief + Anthropic's Frontend Design skillMaking a distinct visual design. It even lists the looks AI tends to repeat and asks the agent to avoid them.
CBrief + Vercel's Web Design GuidelinesA long checklist of interface rules: accessibility, focus states, forms, typography details. It is written for reviewing code, so I asked the agent to follow it while building and then check its own file once.
DBrief + Emil Kowalski's design engineering skillMostly animation and interaction: easing curves, timing, press states, when not to animate.

Then I took screenshots of every version with headless Chrome at desktop size (1440 px wide) and phone size (390 px wide), in light mode.

The checklist (written before I saw any result)

Before looking at the pages, I wrote down 10 signs of AI slop. Each sign present is one point. Lower is better.

  1. A gradient used as decoration in the hero
  2. Emoji used as icons
  3. Vague marketing copy ("elevate your experience", "more than just coffee")
  4. Everything centered
  5. A row of identical cards, each with an icon, a title and one line
  6. Low-contrast text
  7. No real details: missing at least two of opening hours, address and prices
  8. Broken or cramped on a phone
  9. Fade-in on every section, or every card lifting on hover
  10. A small ALL-CAPS label above every section heading

The results

SignA: plainB: Frontend DesignC: VercelD: Emil
Decorative gradient in heroyesnoyesyes
Emoji as iconsyesnoyesyes
Vague marketing copynononono
Everything centerednononono
Identical icon cardsyes (4)noyes (4)yes (3)
Low-contrast textnonono*no
No hours, address or pricesnononono
Cramped on phonenonoyesno
Motion or hover lift everywhereyesnoyesyes
ALL-CAPS label on every sectionyesnonoyes
Total (lower is better)5055

* C has a dark mode. In dark mode, its cafe section turns light blue while the text stays near-white, which is very hard to read. I scored the light mode, which is what most visitors see.

Two things surprised me. First, the plain prompt was not bad. None of the four versions wrote anything like "elevate your experience", and all four invented useful details: opening hours, an address, prices per 250 g bag. The old slop signs are gone. New ones took their place.

Second, A, C and D are almost the same page. Look at the fonts: all three picked Fraunces for headings and Inter for text. All three have a cream background, a dark serif headline with an orange italic phrase, two rounded buttons and a row of three stats under them ("48h", "12 kg"). Here are their feature cards side by side:

The feature card rows from versions A, C and D. All three use rounded cards on cream with a seedling, a flame and a box emoji in the same order, then a serif title and a short line of grey text.
A, C and D each built a row of emoji cards. Same seedling, flame and box, in the same order.

Three agents, three different skill files, no contact between them, and they all reached for 🌱 🔥 📦. That is what "AI slop" really is: not ugly, just the same.

What each skill changed

A: plain prompt

Version A on desktop and phone: cream page, serif headline 'Coffee roasted by the water, poured with care', orange circle with a coffee cup.

A clean, friendly page that would be fine for a real cafe. It has a menu with prices, opening hours and an address. But it uses the default kit: a gradient circle behind a cup, emoji icons, a small uppercase label above every heading, and cards that lift when you hover them.

B: Anthropic Frontend Design

Version B on desktop and phone: dark teal hero with very tall condensed headline 'Roasted on the quay, poured at the counter' and a chalkboard listing this week's roasts by day.

The only version that looks like someone made a choice. The agent picked a harbour-and-chalkboard idea and ran with it: tall condensed headings, a teal and yellow palette, and a "roasted this week" board with the day each coffee is roasted. The coffee bags are flat colour blocks, not emoji. The order steps are numbered 1 to 4 because they really are steps.

This makes sense when you read the skill. It asks the agent to start from the subject (a harbour, a roaster) instead of a template, to plan the colours and fonts first, and then to check that plan against a list of looks that AI repeats. That list describes A, C and D quite closely. It also asks for restraint: one bold idea, the rest quiet.

It isn't perfect. On a phone, the four coffee bags become very tall coloured blocks, which is a lot of scrolling. And there is a small bug: the empty "added to bag" message box peeks up from the bottom edge of the screen before you click anything.

C: Vercel Web Design Guidelines

Version C on desktop and phone: cream page with serif headline 'Small-Batch Coffee, Roasted by the Sea' and a sunset illustration of a cup by the sea.

Visually, almost the same as A. Under the hood, it's the most careful version. It is the only one with a "skip to content" link for keyboard users, balanced line breaks in headings, numbers formatted with the browser's own locale tools, and clear focus outlines. Following the guidelines' "Title Case" rule made the buttons read "Shop Fresh Beans" and "Add to Bag", which is fine but slightly stiff.

On a phone, the header is cramped: the shop name is cut off as "Harbour Coffee Ro…". And as noted above, its dark mode has a real contrast bug. So the checklist didn't catch everything, but that's expected: it's a list of rules, not a design brief.

D: Emil Kowalski's design engineering

Version D on desktop and phone: cream page with serif headline 'Small-batch coffee, roasted by the water' and a teal sea scene with a cup and a fresh-roast badge.

Again the same family as A. What changed is how it moves. Buttons shrink slightly when pressed, transitions use custom easing curves, hover effects only run on devices with a mouse, and motion is turned down for people who ask for less. There is also a filter for the bean list and a weekly / fortnightly / monthly switch for the subscription. Those details feel nice when you use the page, but they don't show in a screenshot.

It also fades in each section as you scroll, which is the one animation habit most likely to feel "AI". And a small layout slip: prices like "£11.50 / 250 g" break so the "g" lands on its own line.

What you can't see in the screenshots

I also searched each file for a few things the skills talk about. Numbers are how many times each appears in the code.

DetailABCD
"Skip to content" link0020
Visible keyboard focus styles1242
Respects "reduce motion"yesyesyesyes
Custom easing curves0003
Press feedback on buttons0014
Hover effects only on mouse devices0004
Even-width numbers for prices0141
FontsFraunces + InterBig Shoulders + Source SerifFraunces + InterFraunces + Inter

So each skill did its own job. It's just that only one of them has "make it look different" as its job.

Verdict: which 2 to install

  1. Anthropic's Frontend Design, if your problem is "it looks like every other AI site". In this test it was the only skill that changed the design, and it was the only page with zero slop signs.
  2. Vercel's Web Design Guidelines, as a second pass. Run it as it was meant to be used: ask the agent to review the finished page against it. It catches accessibility and detail problems that a design skill ignores.

Emil Kowalski's skill is worth having when you build interactive parts: menus, drawers, toasts, anything that moves. For a mostly static landing page, it changes very little you can see.

Limits of this test

Sources

Written by Tabish Hassan, a software developer. Found a mistake? Email hello@tabishapps.com.