How to Fix Generic "AI Slop" UI: A Subtraction Checklist for Coding Agents
Left unguided, language models converge on the same recognizable UI habits: a glowing eyebrow pill above every heading, cards nested inside cards, 4px colored left borders, and invented "+128% efficiency" badges tucked into the corner. Removing that generic AI look does not come from adding more shaders—it comes from subtracting those default habits and anchoring the layout in real domain material.
Key takeaways
Spot the telltale AI defaults early
ubiquitous eyebrow pills, 4px left accent bars, triple-nested cards, wide-tracked uppercase labels and invented KPI percentages.
Replace boxes with alignment and spacing
if two items already read as a group through proximity and type scale, delete the outer wrapper.
Takeaway 3
Ground every number in real product logic (actual tier prices, batch sizes or millisecond latencies) rather than filler marketing statistics.
Takeaway 4
Run Oil UI’s subtraction and readability checklists against 100% and 200% browser screenshots before shipping.

By the water.
Two days by hand.
Wedge the clay, shape a cup, and trim its rim. Spend two quiet days at a workbench by the water.
- Schedule
- Nov 14–15 · 14:00–18:00
- Availability
- 2 seats · Clay, glaze & firing included
- Location
- Waterside Atelier · Courtyard bench 02
Make Inspiration Tangible & Empower Your Craft
An all-in-one immersive workshop experience to unlock your endless creative potential.
Expert mentors · Premium materials · One-stop service
Six Habits That Instantly Give Away an Unedited AI Interface
What people call "AI slop" is rarely a single bad color—it is a cluster of filler widgets the model inserts when it does not know what should carry visual weight. Eliminating these six patterns changes the feel of a page immediately:
| Default AI habit | Why it hurts the interface | Oil UI replacement & subtraction |
|---|---|---|
| An eyebrow pill badge above every section heading | Twelve pills down a page flatten hierarchy so nothing feels important | Enter sections directly with a clear heading or numeral; save badges for real live statuses |
| Cards nested inside cards with 4px colored left borders | Stacked padding and parallel borders crowd out the actual content | Drop outer card wrappers; group content with grid alignment, whitespace and single hairline rules |
| Purple/indigo neon gradients and frosted glass everywhere | Applies the same crypto/SaaS palette to woodshops, clinics and developer tools alike | Derive surface and accent colors from the domain (raw oak & linen, dark bronze, paper & ink) |
| Invented "+240% velocity" or "99.98% accuracy" filler badges | Visitors spot fake numbers immediately, eroding trust in the real product | Display only genuine product figures (stool dimensions in cm, batch size of 24, real invoice rows) |
| Three identical equal-width cards with circle line icons | The "Fast / Smart / Secure" three-card row is the signature cliché of one-shot prompts | Use asymmetric layouts or put a working interactive control directly on the canvas |
| Low-contrast gray-on-gray body copy and tiny uppercase labels | Looks tidy as a thumbnail but strains the eyes during actual reading | Enforce legible contrast, a comfortable 55–75 character measure and four clear type sizes |
How to Subtract Noise: Borders First, Then Type Scale and Air
Open Fieldwork Type, Atelier Volders · Grain & Tenon or TRACE (scent) in the gallery. You will notice how rarely they wrap content in shadowed rounded boxes, yet every section feels distinct. That clarity comes from three fundamentals:
- Use fewer font sizes with bolder contrast between them
- Four distinct sizes (display heading, section heading, body copy and caption/meta) can carry an entire application. Avoid scattering 11px, 12px, 13px, 14px and 15px across the same view.
- Delete half the borders and test whether the layout still holds
- During review, strip container borders and background fills one by one. If left-alignment and vertical rhythm already separate the groups, leave the box off.
- Let working controls replace decorative icons
- Instead of drawing a shield icon next to a paragraph about flexible licensing, render the actual Desktop / Web / App license checkboxes and let the price update on click.
An Anti-Slop Prompt Block You Can Add to Any Brief
Alongside installing Oil UI, you can include these explicit guardrails when prompting your coding agent:
Apply Oil UI standards and enforce these subtraction rules:
1. Do not place eyebrow pill badges above section headings, do not use 4px colored left accent borders, and avoid default purple/blue glowing gradients.
2. Do not invent filler marketing metrics (such as "+128%" or "99.9% uptime") or generic three-column "Fast / Smart / Secure" icon cards.
3. Avoid nesting cards inside cards; build hierarchy with grid alignment, typographic contrast, generous whitespace and subtle 1px dividers.
4. Capture 1440×900 and 390×844 screenshots and remove any border or wrapper whose deletion does not reduce clarity.Works best when Oil UI is installed via npx skills add oil-oil/oil-ui.
Working gallery examples & prompts
Browse collection →Oil UI Pro: Multi-round blind review & safe legacy app renovation
The free skill handles quick single-page subtraction. When you are shipping a flagship release or modernizing an existing codebase without breaking production handlers, Oil UI Pro adds up to 3 rounds of blind review (targeting 9/10), 200% zoom inspection, and 3-tier legacy renovation ($9.99 one-time, lifetime updates).
Explore Oil UI Pro →npx github:oil-oil/oil-cli install oil-ui-proCommon questions
Why does telling an AI "don’t make it look like AI" rarely work on its own?
Because the model does not map the phrase "looks like AI" to specific DOM and CSS choices. Naming the exact culprits—eyebrow pills, nested card padding, invented KPI badges, equal-width icon trios—and supplying concrete structural alternatives is what changes the output.
If I stop wrapping everything in cards, how do I separate sections?
Use four cleaner tools: 1) clear vertical spacing hierarchy (e.g., 96px between sections vs. 20px within a group); 2) subtle full-bleed surface tone shifts; 3) a single 1px top border paired with a left-hand section label; or 4) asymmetric two-column splits.
When is a pill badge actually appropriate?
When it communicates a live, variable state that users need to spot—such as "Payment failed" in a billing table or "3 stools left in April batch." If a pill merely repeats the section topic above an H2, delete it.
What is the fastest way to spot leftover AI template habits on a page?
Zoom out to 50% or blur the text. If the page looks like a uniform stack of rounded rectangles and symmetric three-column blocks, template habits are still running the layout.



