A "De-AI" Design Skill for Frontend Built by AI: Impeccable

One skill, 23 commands, an anti-pattern cheat sheet, and a slop detector that runs in CI. The main site explains the how; /slop catalogs every UI cliché that screams "generated."

By Impeccable07-15 · 10 min read⚑ Tutorial / how-to
Impeccable · Tool Guide
July 15, 2026 · ~10 min read · impeccable.style + /slop

Build frontends with Cursor, Claude Code, Codex, or similar and the results blur together: purple gradients, Inter, icon-tile headings, the same three-column card grid every time. Impeccable doesn't try to make the model "more creative." It clears out those default reflexes and hands you a vocabulary of design commands you can call directly.

1 + 231 core skill, 23 commands organized by discipline
46deterministic detection rules that run in CI without asking the model
Freeworks with Cursor / Claude Code / Copilot / Gemini / Codex
01What it solves

First, unlearn the generator's default muscle memory

Using AI for UI, blind

Purple-and-teal gradients, dark glow, the full Inter / Geist house style.

Feature cards are always "small rounded icon + title + three lines."

Copy is all streamline / empower / supercharge.

After Impeccable

Slop reflexes are cleaned first, then you target type, color, layout, and motion by name.

Respects your project's tokens and components instead of imposing a new default system.

npx impeccable detect catches regressions in PRs.

The main site calls it Desloppification: stripping the "generated" defaults out of typography, color, layout, responsive behavior, interaction states, motion, and copy. Its own boundaries are stated plainly too: a skill won't make the model a better designer, but it can kill the reflexes that make the output look generated.

Another approach showed up: pols's Slop.md

Same family of "AI-looking UI" problems, different route—an ~80,000-word rulebook you can curl into Claude / Cursor / Codex as config. No 23 commands, no CI detect. Stick with Impeccable for command flows and PR checks; read the other piece if you just want an overall rulebook, or want to layer one on top.

Related follow-up · Read this too
An 80,000-word anti-AI-wonk design guide: drop Slop.md into your agent as the default rulebook
Shape comparison + five-agent install/switch + before/after demo. Stacks with this article.
02How to use

23 commands: a shared design vocabulary between you and the AI

Each command maps to a design task, so you don't re-explain yourself from scratch. Roughly five groups:

Create/craft · /shape

Think before doing: surface the need, write a brief, then design and ship it whole.

Evaluate/critique · /audit

Design reviews with scoring and automated checks; five technical dimensions with P0–P3 severities.

Refine/typeset · /layout · /colorize

Type, layout, color. Also /animate, /delight, /bolder, /quieter, /overdrive.

Simplify/distill · /clarify · /adapt

Cut hard, rewrite copy, adapt across breakpoints.

Harden/polish · /optimize · /harden

Final pass on craft, performance, production edge cases, i18n.

Detectnpx impeccable detect

Deterministic checks that don't need a model—scan files, dirs, stdin, or a rendered URL.

A common flow /shape /craft /critique /polish detect Review output feeds into refine commands like typeset / layout / distill; detect can run solo in CI.
Commands combine: typeset often pairs with bolder or polish; critique typically routes into polish, distill, bolder, and similar follow-ups.
03Capabilities

Eight product features, ordered as they'd land in your repo

The main site lists eight areas; here they are in the order they'd actually come in:

  • Learns your design system: scans tokens, components, and conventions—new work follows your system, not a fresh default.
  • Product context, written once: drop it in PRODUCT.md; subsequent commands read it before designing (who the users are, tone, anti-references).
  • Exports DESIGN.md: optionally in Google Stitch format, readable by other DESIGN.md tools.
  • Built per-agent: the same skill recompiles for different harnesses/models, with bans for known bad habits (one model loves hover-zoom on images).
  • Landing page vs product UI, two rule sets: marketing pages and dashboards are not the same aesthetic.
  • Block slop before ship: 46 deterministic rules with exit codes for CI.
  • Live Mode (Beta): click elements on a running dev server, leave notes, generate hot-swappable variants.
  • Writes back to source: variants land in real files as normal diffs—commit or revert.
04Slop field guide

/slop page: what "AI-look" actually is

impeccable.style/slop lays out the common anti-patterns, sorted into AI slop / Quality, each flagged for CLI or browser detection. A few you'll run into almost daily:

AI slop
The AI palette

Purple-teal gradients with a dark glow—the ID card of generated UI.

AI slop
Gradient text

Color gradients on headings and metrics, basically a generator signature.

AI slop
The same card grid

Equal-size cards + icon + title + body, repeated to infinity. The default homepage.

AI slop
Icon tile above title

Small rounded icon always sitting above the heading. The universal feature-card template.

AI slop
Ubiquitous typefaces

Inter, Geist, Space Grotesk, and now Instrument Serif—once they're everywhere, it stops looking like a choice.

AI slop
Cream beige backgrounds

Warm off-white as the "tasteful" default, rather than something grown from a palette.

AI slop
Em dash spam

String after string of em dashes in body copy is a tell-tale model tic.

Quality
Low contrast

Fails WCAG AA, hard to read, and has nothing to do with looking premium.

Two ways to detect

Run /impeccable critique inside the harness and the browser evaluation layers in deterministic findings. For CI or a local terminal, use npx impeccable detect. Or grab the Chrome extension to scan any page at a glance.

05Install

One command installs the build matched to your harness

Needs Node 22.12+. GitHub Copilot already ships it in the app—just turn on Experimental in settings and skip the install.

Copy-paste · Install / update / init
# Install the build matched to your current harness & model
npx impeccable install

# First time
/impeccable init

# Update
npx impeccable update

# Deterministic detection (CI-ready)
npx impeccable detect src/
Quick start
  1. Run npx impeccable install in Cursor / Claude Code / Codex
  2. Run /impeccable init to set up project conventions and PRODUCT context
  3. New page: start with /impeccable shape or /craft; existing page: /critique, then polish / typeset
  4. Wire npx impeccable detect into the PR to stop purple gradients and cookie-cutter cards before merge
  5. Full docs: docs · Getting started: getting started
What to take away
What this piece gives you: what it is, how the commands are organized, what slop looks like, and the three install/detect commands.

Primary sources

Main site: Impeccable: Design skills for AI harnesses

Anti-pattern field guide: AI Slop / Quality patterns

Docs & detection: docs · detect

Source
ImpeccableImpeccable·Read the source
↑ End of article
✓ This article is free to read in full

Members can copy or download the full Markdown, and let their AI subscribe and ask.

Read the original ↗
📮 New explainers, straight to your inbox

Found this useful? Leave your email — every new explainer, the moment it's out. Unsubscribe anytime.