Anti-Slop Skills for Claude Code: frontend-design, Impeccable and Taste Skill Compared (2026)
Three free skills promise to keep Claude Code off the generic AI look. What each one installs, what it tells the model, what it checks, and when a plain rules file does the job instead.
On this page
A skill is a rules file with a plan: instructions the agent loads when the task calls for them, sometimes with scripts that check the result.
If you build interfaces with Claude Code, you have probably met the generic look: the same accent, the same font, the same three cards. Prompts help for one session. Rules files help for every session. Skills go one step further: they package design guidance, and in some cases a checker, that the agent pulls in when it works on UI.
Three free skills come up most often in November 2026: Anthropic's own frontend-design, Paul Bakaus's Impeccable, and Taste Skill. This article describes each from its own repository, compares them, and says when you do not need any of them.
frontend-design (Anthropic)
The skill lives in Anthropic's public skills repository. Its description reads: "Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one."
Install. In Claude Code, add the marketplace with /plugin marketplace add anthropics/skills, then install from /plugin. The repository's README installs its skills as two plugins, document-skills and example-skills; check in the /plugin menu which one carries frontend-design before you install. Licence terms are in the skill's LICENSE.txt.
What it tells the model. It is guidance, not a list of banned classes. On type, it asks for "one family or two, and if two, make them clearly distinct", and to "Choose your typefaces deliberately, not the default families you would reach for on any other project". On colour, it asks the model to plan a palette of four to six named hex values. On motion, it prefers "A single orchestrated moment" to scattered effects.
What makes it interesting is its list of looks it considers overused, which goes beyond the usual blue and purple: a warm cream background with a high-contrast serif and a terracotta accent (it notes that accent is often near #D97757, Anthropic's own Claude colour), a near-black background with a single acid-green or vermilion accent, monospace for small labels, and an arrow appended to links and buttons. Fair warning: the site you are reading uses three of those. A list of overused looks is a prompt to decide on purpose, not a law.
Checks. None: it guides the generation and leaves the verification to you.
Impeccable
Impeccable is by Paul Bakaus, under the Apache 2.0 licence, and started from Anthropic's frontend-design skill. It describes itself as "The design vocabulary for your coding agent".
Install. From the project root, npx impeccable install detects your coding tools and offers a per-project or global install; then run /impeccable init. For Claude Code there is also a plugin: /plugin marketplace add pbakaus/impeccable. It supports Cursor, Codex CLI, Gemini CLI and others through their own folders.
What it adds. Twenty-four commands grouped as steer (bolder, quieter, typeset, layout...), review (critique, a scored UX review; audit, a technical report ranked P0 to P3), finish (polish, harden...), and plan (init writes a PRODUCT.md, document writes a DESIGN.md).
Checks. This is its strongest point. Impeccable ships a detector with 62 deterministic rules, no model and no API key. It runs as an agent hook on each UI file the agent edits, from the command line (npx impeccable detect src/ or on a URL), in CI, and as a Chrome extension.
Worth knowing before you install. Per its README, installed hooks run even when you deny the model's own commands; telemetry is on by default (npx impeccable telemetry off or DO_NOT_TRACK=1 turns it off); and its live mode may start claude with --permission-mode bypassPermissions when no chat session is active, unless you set IMPECCABLE_LIVE_COPY_AGENT. None of this is hidden, but read the README before adding it to a shared repository.
Taste Skill
Taste Skill is by Leonxlnx, under the MIT licence. It aims to steer agents toward polished company websites, with "art direction, reference images and a browser check instead of generic AI pages."
Install. With the skills CLI: npx skills add https://github.com/Leonxlnx/taste-skill --skill "design-taste-frontend". As a Claude Code plugin: /plugin marketplace add Leonxlnx/taste-skill then /plugin install taste-skill@taste-skill. There is a Codex plugin too. It needs Node 22 or later and a Chrome, Edge or Chromium browser.
What it tells the model. It is the most opinionated of the three. The agent first classifies the business (software, gaming, tech, product, service or place), then scripts assign a palette, a font pairing and one of eleven hero layouts. It asks for real photographs and real product UI, limits WebGL effects to software, tech and gaming pages, and keeps motion to a hero entrance plus one or two moments.
Checks. It renders the page in headless Chrome at widths from 1440 down to 390 pixels and looks for broken effects, contrast drops and placeholder text, and a gate script blocks completion until the fixable failures are gone, three rounds at most.
Side by side
| frontend-design | Impeccable | Taste Skill | |
|---|---|---|---|
| Author, licence | Anthropic, see LICENSE.txt | Paul Bakaus, Apache 2.0 | Leonxlnx, MIT |
| What it is | Design guidance | Guidance, commands, detector | Art direction, scripts, browser check |
| Checks the output | No | Yes, 62 rules, hook, CLI, CI | Yes, browser renders and a gate |
| Best for | A better first draft | Teams that want review and enforcement | Marketing sites built from scratch |
| Weight | Light | Heavy: hooks, telemetry to switch off | Heavy: Node 22 and a browser |
When a rules file is enough
A skill shines when the agent builds new interfaces often, or when you want it to review its own work. If what you need is that the next page stops using the default blue, the default font and the three-card row, a short section in AGENTS.md does it with nothing to install. The AGENTS.md design rules template is that section, with the literal tokens to ban.
The two approaches also combine well: rules for the decisions that never change (your palette, your fonts), a skill for the craft of each new page.
Checking the result, whatever you install
Whichever route you take, look at what shipped. The free AI slop checker scans a live page for eight of the defaults these skills target and shows the evidence, so you can tell whether the guidance held after a long session. From inside Claude Code, the Sailop MCP server runs the same check as a tool (scan_url), read-only and without an account: ask the agent to scan the preview after each change.
Impeccable's detector covers more rules than Sailop's eight and runs on source files; Sailop reads the page a visitor receives. Use the one that fits where you check: in the repository, or on the live site.
Related
Scan your site free
Eight AI-builder defaults, the evidence for each on your page, and the fix kit. Free, no account. If your site has more pages to fix, the site report covers up to 25 of them.
Read the whole site, with a fix prompt per default
Get told when the CLI ships