Actionable TL;DR
- Promise: "The Anti-Slop Frontend Framework for AI Agents"
- License: MIT, free (open source)
- Install:
npx skills add Leonxlnx/taste-skill - What sets it apart: several style-targeted sub-skills rather than one generalist skill
- Keep in mind: 31.7k★ as of 2026-06-02 (up from 16.6k★ a month earlier), fast growth
The promise, quoted verbatim
"The Anti-Slop Frontend Framework for AI Agents"
Source: tasteskill.dev (ouvre un nouvel onglet), reviewed 2026-06-02. The GitHub page phrases it differently: "gives your AI good taste. stops the AI from generating boring, generic slop".
The bet behind Taste Skill: there is no single "good taste" but distinct visual registers. Rather than one skill that tries to do everything, the project ships a family of sub-skills, each specialized in one intent. You pick the sub-skill that matches the register you want, and Claude applies that register's conventions.
What it changes in practice
Without Taste Skill, asking Claude Code for "a landing page" produces the default LLM landing: centered hero, purple-pink gradient, three aligned feature cards, all interchangeable from one site to the next.
With the targeted minimalist-ui sub-skill, the same prompt yields a sober page, expressive typography, generous whitespace, no gradient or superfluous effect. With industrial-brutalist-ui, the same request produces a raw, high-contrast, assertive register. Choosing the sub-skill becomes the main lever, instead of a long prompt that spells out the style word by word.
Installation
npx skills add Leonxlnx/taste-skill
To target a single sub-skill rather than the whole family:
npx skills add Leonxlnx/taste-skill --skill "design-taste-frontend"
The skill installs at your user profile level and works with several harnesses: as of 2026-06-02 the site lists Codex, Claude Code, Cursor, OpenCode, Gemini CLI, AI Studio, v0 and Lovable.
The family of sub-skills
As of 2026-06-02, the repo groups about a dozen sub-skills. They move fast (some in beta, v1/v2 versions coexist), so treat this list as a snapshot, not a fixed contract:
| Family | Sub-skills (snapshot 2026-06-02) | Use |
|---|---|---|
| Frontend core | design-taste-frontend (v2 experimental), design-taste-frontend-v1 | The generalist anti-slop engine |
| Visual styles | minimalist-ui, industrial-brutalist-ui, high-end-visual-design | Distinct visual registers |
| Image to code | image-to-code | Start from a screenshot or mockup |
| Audit / redesign | redesign-existing-projects | Pick up an existing project |
| Execution | full-output-enforcement | Force complete, untruncated output |
| Export / variants | stitch-design-taste | Google Stitch-oriented generation |
| Image generation | imagegen-frontend-web, imagegen-frontend-mobile, brandkit | Visual references |
Typical workflow with Claude Code
Pick the register
Decide the style before coding: minimalist, brutalist, high-end... The register determines which sub-skill to invoke.
Install the right sub-skill
npx skills add Leonxlnx/taste-skill --skill "minimalist-ui" for example, to load only what you need.
Generate then critique
Claude produces the component in the chosen register. Then ask for a critique to push the render further in the same direction.
Validate visually
Check the render with Playwright MCP: multi-viewport screenshot, contrast, alignment. The sub-skill does not see the browser.
Failure modes to know
Case 1 — Wrong register for the need. Loading industrial-brutalist-ui for a mainstream banking app produces a coherent but off-topic render. The sub-skill family assumes you know which register you want. If you hesitate, start with the design-taste-frontend core rather than a marked style.
Case 2 — Moving versions. The sub-skills evolve fast (v1/v2, betas). A tutorial that cites a precise sub-skill name can be outdated in a few weeks. Check the current list on the repo before relying on an exact name.
Who is it for?
- Recommended if you work across several projects with very different styles and want a clean lever to switch register, without rewriting a long prompt each time.
- Recommended for starting from a mockup or screenshot thanks to the
image-to-codesub-skill. - Avoid if you want a single "do-it-all" tool: Taste Skill's strength (its granularity) is also its learning curve. Impeccable or UI UX Pro Max are more direct for a single use.
Alternatives to know
- Impeccable (
pbakaus/impeccable): a single skill, design vocabulary and anti-patterns. Simpler to start. See the Impeccable page. - UI UX Pro Max (
nextlevelbuilder/ui-ux-pro-max-skill): multi-stack catalog of styles and palettes. See the UI UX Pro Max page. - Huashu Design (
alchaincyf/huashu-design): HTML prototypes and presentations, MIT-licensed since 2026-05-14 (re-check before commercial use). See the Huashu Design page.
To dig deeper: Skills vs MCP vs Plugins comparison, must-have skills 2026, find-skills to discover more.
Going further
- Official site: tasteskill.dev (ouvre un nouvel onglet)
- GitHub repo: github.com/Leonxlnx/taste-skill (ouvre un nouvel onglet) — MIT, 31.7k★ as of 2026-06-02
- Validation workflow: combine with Playwright MCP to check the real render
Taste Skill is the right pick when you juggle distinct visual registers and want to drive them explicitly. Its granularity takes a little ramp-up, but that is exactly what avoids the one-size-fits-all look.