How to review AI-generated UI for slop
By Imran Sheikh · 2026-11-12 · AI in practice · 4 min read
Key points
- Slop is a default that no one chose on purpose.
- Review for gradients, emoji labels, glow, uneven spacing and filler copy.
- Fix it by deciding a direction first, then editing in order.
AI coding agents build interfaces quickly, and many of those interfaces look alike. Purple gradients. Glowing cards. Emoji in place of icons. Headlines that could belong to any product. This is what designers have started calling slop.
Slop is a default that nobody chose on purpose. Agents reach for the most common pattern in their training, and the most common pattern is generic. Your job in review is to catch those defaults and replace them with decisions.
The usual tells
Once you learn the signs, you see them everywhere. None of them is wrong in isolation. The problem is the pile-up, which signals that no person made choices.
- Gradients, especially purple to blue, on backgrounds, buttons and headline text.
- Glows and soft colored shadows around cards and buttons.
- Emoji used as labels, icons or section markers.
- Badges that say New or Beta with a sparkle on everything.
- Small uppercase labels with wide letter spacing above every heading.
- Cards inside cards, each with a large radius and a faint border.
- Spacing that drifts, with gaps that differ for no reason.
- Copy full of filler such as Welcome back or Get started today.
If a screen shows four or five of these, it was likely accepted as it came out. That is the moment to slow down.
Start by finding a direction
Slop fixes fail when they begin with surface tweaks. Swapping a gradient for a flat color does not give a product character. Start from the product itself. Who uses it, in what mood, for what purpose.
A prayer times app under living skies should feel quiet and spacious. An arcade getaway game should feel loud, fast and a bit dangerous. A cozy block puzzle with cats should feel soft and warm. We make products like these, and each one wants a different palette, type and motion. Write a few words about the feeling you want. Use them as a filter for every choice.
Edit in a fixed order
A reliable order keeps the work from sprawling. Start with the foundations and finish with the flourishes. Each step makes the next easier.
- Spacing and layout. Pick a scale, align to it and remove the stray gaps.
- Color. Define a small palette with a clear role for each color.
- Type. Choose one or two typefaces, set a scale and fix the hierarchy.
- Icons. Use one consistent icon set and replace every emoji label.
- Copy. Rewrite headings and buttons so they say something specific.
- Details. Align radii, borders and shadows to a single system.
- Motion. Add movement only where it explains a change.
Do not skip ahead to motion and polish. A glow will not rescue a layout with uneven spacing. Foundations first.
Fix the specific offenders
Take each tell and ask what it was doing. Then do that job honestly.
A gradient usually stands in for depth or emphasis. Ask which one you need. Emphasis can come from size, weight and contrast. Depth can come from a quiet surface color and a thin line. Most gradients can simply go.
A glow tries to signal importance or energy. Replace it with contrast. If an element matters, make it larger or darker, or give it more room. Reserve any glow for a place where light is part of the story, such as a night sky.
Emoji labels are a shortcut around icon design. Use a real icon set with a consistent stroke, or use plain text. Emoji render differently across platforms, and they carry a tone that rarely matches your brand.
Filler copy hides the absence of a point. Write what the screen is for. Replace Get started with the actual action, such as Add your first reminder. Specific words are the cheapest upgrade in the whole interface.
Teach the agent your taste
You can reduce slop at the source. Put your design rules in a notes file that the agent reads. List the tokens, the palette, the type scale and the banned patterns. State the rules directly. Keep gradients off text, replace emoji labels with icons and use the existing icon set.
Point the agent at real components. Ask it to reuse the existing button, card and input before inventing new ones. The more of your system it can see, the less it fills with generic defaults. When it repeats a mistake, add a line to the file.
Use a review checklist
A short checklist keeps reviews consistent, especially when you review many agent changes a day.
- Does this screen look like our product, or like any product.
- Can I name the purpose of every color on it.
- Is the spacing on a scale.
- Does every icon come from the same set.
- Does each line of copy say something specific.
- Does motion explain something, or only decorate.
- Does it hold up at large text sizes and in dark mode.
Run the checklist on a real device, not only in a screenshot. Slop hides well in a static frame and shows itself in use.
Agents will keep getting better at making screens that look finished. That makes your eye more valuable. Someone has to say this is generic, this is off and this could be ours. That person is the designer in the review.
Anyone can generate a screen. Someone still has to choose it.
Review every generated screen as if a stranger made it, and keep only the parts you would defend. What remains will look like your product, because you decided that it should.