What "design taste" means for an agent skill
Design taste is hard to specify directly, so the skills that actually deliver it don't try to. Instead they encode something narrower and checkable: a named design philosophy, a list of things not to do, a scoring rubric, or a hardened template that closes off the cheap options.
That's the pattern worth looking for. A skill whose description says "makes it look good" with nothing underneath is asking the model to improvise taste from nothing, which produces exactly the generic, interchangeable output these skills exist to avoid.
A few things worth checking before you install one:
- Does it name specific anti-patterns, not just aspirations? "Avoids countdown timers and fake scarcity" is checkable. "Creates compelling designs" is not.
- Does it produce a verifiable artifact? A scored report, a written spec, or a themed export are all easier to judge than free-form markup you have to eyeball.
- Is it scoped to a specific format? Web layout, wireframing and design-tool automation are different disciplines with different rules. A skill built for one won't transfer cleanly to another.
- Does it require script execution? Most of the strongest picks here are pure-instruction skills that run anywhere; a couple need Node.js or shell access, which matters if your platform doesn't allow tool execution.
A note on the star counts below: they belong to the repository a skill ships in, not the skill itself. Anthropic's Frontend Design sits in anthropics/skills alongside dozens of others, so its 167k reflects the whole collection. Single-purpose repos like pbakaus/impeccable and leonxlnx/taste-skill are the more meaningful signal, because there the stars really are for that skill.
The best skills for design taste in 2026
Impeccable Design Skill
Best overall58kTransform your frontend interfaces into exceptional designs.
- Best for
- Anyone who wants better default output without design training
Impeccable is the one to install first if you're only installing one. It lives in its own repository (so its ~58,000 stars are a verdict on this skill specifically, not on a collection it happens to sit in) and it targets the exact failure mode most people hit: an agent that produces functional, competent, completely forgettable interfaces.
It's Apache-2.0 and needs no script execution, so it runs on any agent that reads a SKILL.md, including the ones without tool access.
Stitch Design Taste
Best for design specs75kGenerate high-quality DESIGN.md files for Google Stitch.
- Best for
- Pinning design decisions down in writing before any code exists
Taste takes a different and, in some ways, more durable approach: instead of nudging generation, it produces a DESIGN.md (an explicit written specification of the design decisions) before any code exists.
That matters more than it sounds. An agent asked to "make it look good" improvises fresh every session, so two pages built a week apart don't match. An agent handed a written spec produces consistent work because the decisions were made once and written down. If you're building anything with more than a couple of screens, this is the higher-leverage skill.
Frontend Design
Best official168kCraft unique and intentional UI designs with confidence.
- Best for
- A safe, maintained default from the people who built the format
The official option, from Anthropic's own skills repository. It's the conservative pick, well maintained, unlikely to break, and a sensible baseline if you'd rather not evaluate a third-party skill's design philosophy before trusting it.
It's also less opinionated than Impeccable or Hallmark, which cuts both ways: fewer strong defaults to fight, and fewer strong defaults doing the work for you.
Hallmark
Best anti-slop85kAnti-AI-slop design for greenfield pages, redesigns, audits and direction extraction.
- Best for
- Stopping every project you build converging on the same layout
Hallmark is built around structural variety, the explicit goal that two different projects built with it shouldn't converge on the same templated layout. It handles greenfield pages, redesigns, audits, and extracting design direction from a URL or screenshot.
The author's own caveat is worth repeating: it's a poor fit if you want flexibility or a quick templated result. It's deliberately opinionated. That's the point, and it's also the cost.
Web Design Reviewer
Best for critique38kIdentify and fix design issues in websites efficiently.
- Best for
- Reviewing what an agent already built, rather than building it
Everything above generates. This one critiques. Pointing a reviewer at output an agent already produced catches a different class of problem than trying to prevent it at generation time, and the two compose well, generate with Impeccable, review with this.
Wireframe
Best for early structure77kCreate low-fidelity UI wireframes in SVG format.
- Best for
- Settling layout and hierarchy before anyone argues about colour
Low-fidelity SVG wireframes, which is the right artifact for the stage where layout and hierarchy are still open questions. Deliberately ugly output is a feature here: nobody argues about colour when everything is a grey box, so the structural conversation actually happens.
Web Design
Best lightweight option18kStreamline web UI design and integration.
- Best for
- A light touch when the opinionated skills feel like too much
A lighter-touch option from Daniel Miessler's lifeos repository. Worth knowing about specifically because the strongly opinionated skills can be too much for small jobs, if Hallmark and Impeccable feel like they're fighting you on a two-page site, this is the calmer alternative.
Penpot UI/UX Design
Best for a real design tool38kDrive Penpot, the open-source design tool, directly from your agent.
- Best for
- Teams who need output in a design tool, not just in code
The only skill here that drives an actual design tool. Penpot is open-source, so unlike a Figma workflow there's no licensing barrier to an agent operating it.
Requires Node.js and shell access, which rules it out on platforms without script execution. Check that before planning around it.
Combining them into one workflow
These aren't alternatives so much as stages, and the sequence that works is roughly:
- Wireframe to settle structure while it's cheap to change.
- Stitch Design Taste to write the decisions down as a
DESIGN.md. - Impeccable or Hallmark to generate against that spec.
- Web Design Reviewer to critique what came out.
Installing all four is reasonable. Skills only load when a task matches their description, so an unused one costs nothing but disk.
How to install any of these
Every skill here is a folder containing a SKILL.md. The fastest route is the CLI:
npx skills add pbakaus/impeccable
Or copy the folder into your agent's skills directory by hand, ~/.claude/skills/ for Claude Code globally, .claude/skills/ for a single project. The full install guide covers the exact paths for 16 agents including Codex, Cursor and Antigravity.
Where these fit in the ecosystem
Design skills are one of the clearer demonstrations of why the SKILL.md format took hold: design guidance is exactly the kind of knowledge that's tedious to re-explain every session and easy to write down once. Browse the rest in design, or read on what agent skills are if you're new to the format.
