Anti-slop skills compared: unslop, taste, Impeccable

Ask a coding agent for a dashboard with no other brief and the same screen comes back most of the time: a violet gradient, four equal stat cards, emoji in the labels, Inter on white. Several open skills exist to stop that. For most projects I would install anti-slop from molveau/skills. It merges Damir Sokolovsky's unslop method with Leonxlnx's taste-skill, adds a direction gate and a detector for 20 tells, and credits both authors by name. If you only want one author's method, the originals are excellent, and each section below says when to pick one.

The contenders

Skill	Author	Licence	Best at	Lacks
unslop	Damir Sokolovsky	CC BY 4.0	Fixing an existing screen pass by pass; the story video	A script that flags tells in code
taste-skill	Leonxlnx	MIT	Art direction and real pictures for a new page or app screen	A short path for a screen that only needs cleaning; some scripts need Node 22 and a browser
Impeccable	Paul Bakaus	Apache-2.0	One command per design move, a deterministic slop detector, live mode	A light setup: it wants an install, an init step and context files
frontend-design	Anthropic	Apache-2.0	A short brief that pushes the model toward a distinct direction	An audit, a checklist or a script
anti-slop	Molveau Studio	MIT; the parts adapted from unslop stay CC BY 4.0	One workflow from audit to direction to nine passes, with a detector	Impeccable's scripts and live mode; a heavier folder than either original

Each one, fairly

unslop, by Damir Sokolovsky

unslop treats a vibe-coded screen the way a designer treats a redline review. It lists every sign of slop with where it lives, proposes a direction taken from your product (character, world, the one or two moments that carry the color, a signature detail), waits for you, then fixes the screen in nine passes in a fixed order: spacing, color, icons, copy, type, layout, details, visuals, motion. It also works from a live URL, and it can render a short square video of the screen unslopping itself. Damir started the Unslopping series on X, and the method shows that practice.

Install the original if you want his method exactly as he maintains it, with nothing layered on top. Its CC BY 4.0 licence lets you adapt it commercially as long as you credit him and link back.

taste-skill, by Leonxlnx

taste-skill is strongest when there is no page yet. It runs an inventory of what only this product has, deals a direction from its own library, writes the copy deck, builds, then checks the result in a real browser. Its app-screens reference is the most detailed I have read on dashboards and settings pages. Install the original if you mostly build new marketing pages and want its library and the author's updates directly.

Impeccable, by Paul Bakaus

Impeccable gives the agent a vocabulary: polish, bolder, quieter, critique, audit and the rest, each with its own playbook. It ships a slop detector that runs without a model or an API key, and a live mode that swaps variants of an element in your running dev server. My ui and ux skills carry Impeccable's reference files, but none of its scripts. If you want that detector in CI or the live mode, install Impeccable itself.

frontend-design, by Anthropic

Anthropic's own skill is one file. It asks the model to act as the design lead of a studio whose clients have rejected anything templated, and to ground the palette, type and layout in the subject. It is a good first nudge on new UI and costs almost nothing to load. It has no audit and nothing that checks the result, so it pairs well with a detector from one of the others.

What the merged skill adds

• Routing. One install. The SKILL.md has a "when to read what" table, so on a dashboard the agent opens taste's app-screens reference, and for exact values it opens unslop's tokens, instead of loading every file.
• Pinned, unedited copies. unslop and taste-skill sit under references/vendor/ at a pinned commit, never edited by hand. A weekly GitHub Action compares them with upstream and opens an issue when either moves. A person reads each bump before it lands.
• A playbook that settles disagreements. The sources contradict each other in places. unslop falls back to Lucide icons, which I treat as a tell. taste-skill's page run wants a motion layer with section entrances, unslop allows one entrance, and I ban reveal-on-scroll. Each conflict has a written choice and a reason, so the agent does not pick one at random.
• The direction gate. Before any code: five lines (product, character, world, moments, signature), an inventory of 8 to 12 things no competitor shares, a list of second-order defaults to refuse (the cream page with a terracotta accent, Fraunces by reflex), a swap test with a competitor's name, then a pause for your approval.
• The 20 tells and a detector. detect-tells.mjs has no dependencies and runs on Node 20. It flags the mechanical tells (gradient text, emoji in copy, side-stripe borders, hover fades on buttons, em dashes, buzzwords) and comes with a ratchet test recipe so the count can only go down.
• A story video with a live accessibility step. The renderer is adapted from unslop's. A step named Accessibility shows WCAG contrast ratios and target sizes changing as the screen is fixed, red until each one passes. The credit to unslop is drawn on every frame.
• A real example you can check. A vibe-coded dashboard was unslopped in one run by Claude Opus with this skill, with no hand edits. The before, the after, the story file and the video are in the repo under examples/.

Install

The skill alone, with the skills CLI (Claude Code, Codex, Cursor and other agents that read SKILL.md):

npx skills add molveau/skills -s anti-slop

The design bundle (anti-slop, ui, ux, motion, design-grill and the inspiration index):

npx skills add molveau/skills -s anti-slop -s ui -s ux -s motion -s design-grill -s design-inspiration-index

In Claude Code, all eleven skills as one plugin:

/plugin marketplace add molveau/skills
/plugin install molveau-skills@molveau

Every skill and bundle is listed on the skills page, and the source is at github.com/molveau/skills. The neighbours of this skill have their own comparisons: UI skills, UX and accessibility skills and motion skills.

Checklist

• You know whether the screen exists (unslop's pass order) or not yet (taste's run).
• The direction is written in five lines and approved before any code.
• The swap test fails: a competitor's name no longer fits the screen.
• detect-tells.mjs runs on the changed files and its count does not go up.
• Every claim you could not verify is removed or flagged in the report.
• unslop is credited wherever its method is adapted.