3 Best Design Skills for Claude Code and Codex in 2026

Give Claude Code or Codex a vague prompt to make you a "premium" website and there is a decent chance you know what is coming before it renders: a giant centered headline, rounded cards inside more rounded cards, tiny labels above section headings, Inter or Geist, and purple somewhere for no obvious reason. Then comes a row of three features because apparently every business on Earth has exactly three things to say.

The code can be perfectly fine. The problem is that the design smells like AI from across the room.

Design skills are one of the more useful parts of the agent-skills boom in 2026. Of the viral ones I have looked at, three are worth paying attention to: Impeccable by Paul Bakaus, Taste Skill by Leon Lin, and Emil Kowalski's design and animation skills.

They are also being overhyped in slightly different ways. Taste Skill was not "trained on hundreds of award-winning websites." It is not a trained model. Impeccable does not guarantee a beautiful interface because you installed it. Emil's skills do much more than sprinkle expensive-looking animations everywhere, and one of their better ideas is knowing when an interface should not move at all.

All three make sense to use, but they do different jobs.

Quick Answer: What Are the Best Design Skills for Claude Code and Codex?

My three picks in 2026 are Taste Skill, Impeccable and Emil Kowalski's skills. For a new website, my preferred order is Taste -> Impeccable -> Emil: establish the visual direction, clean up the design system and AI habits, then deal with motion. If the product already has a decent visual identity, start with Impeccable instead of asking Taste to reinvent everything.

GitHub numbers below were checked on August 7, 2026. They show that these projects have serious attention; they are not a quality score.

How I evaluated these: I checked the current skill files, installation documentation and changelogs, then compared the promises with recent Claude Code and Codex user reports. GitHub stars tell us whether a project has attention; they do not tell us whether it will magically fix a bad design brief.

Why Claude Code and Codex Keep Making the Same Kind of Website

And I am not the only one being difficult about rounded corners. Users keep describing the same problem.

One Codex user said GPT-5.5 was good at the logic but kept producing React frontends that were "basic and ugly." Another Claude Code discussion turned into people naming the visual giveaways of vibe-coded sites: repeated cards, colored borders, tiny secondary text and the other little habits you start noticing everywhere once somebody points them out.

Impeccable's own documentation names many of the same defaults: purple-to-blue gradients, Inter everywhere, nested cards and rounded-square icon tiles above headings. Its current detector exists because telling the model "make it less AI-looking" is far too vague to be useful.

The better design skills give the agent a vocabulary and constraints. Instead of hoping the model shares your definition of "premium," you can tell it how much layout variance you want, make it critique the hierarchy, force it to respect an existing design system, or give it rules for easing and motion. The model has better design instructions; it has not suddenly become a designer.

1. Taste Skill: Best for Getting Away From the Default AI Layout

Taste Skill is the one for when the problem starts before the code. You have a blank page, the agent keeps choosing the safest possible composition, and every variation somehow ends up looking like the same SaaS landing page wearing a different shirt.

The current default is Taste v2, which reads the brief and then works with three useful controls: DESIGN_VARIANCE, MOTION_INTENSITY and VISUAL_DENSITY. There is also a stricter gpt-taste variant for GPT/Codex, an image-to-code workflow, and separate skills for redesigning existing projects and pushing specific visual directions.

That makes Taste more interesting than a long prompt saying "be creative." If I want something calm and editorial, I can keep the variance controlled. If the first attempt looks like every startup homepage from the last two years, I can push it harder. The agent now has a more concrete idea of what "harder" means.

Taste gets more interesting if you start with an image. Generate a visual reference first, let Codex analyze it, then implement the page from that reference. A user in r/codex who tried this workflow said it needed three attempts, but the third was "truly 1:1" with the reference. Another commenter in the same thread called the workflow "insanely good."

The three attempts matter more to me than the praise. It is a useful reality check. Taste can make Codex considerably more adventurous, but you still have to look at the output and iterate.

The viral claim about Taste is wrong

I have seen Taste described as being "trained on hundreds of award-winning websites and interfaces." I would not publish that as fact.

Taste is a collection of portable instruction files and supporting material. Its repo has a research/ folder and says that background writing shaped the skills, but there is no model-training claim in the current documentation. That distinction matters. You are giving Claude Code or Codex a set of opinions, rules, references and workflows. You are not swapping its brain for a fine-tuned designer model.

The viral clips also tend to skip one awkward detail: the new Taste v2 is explicitly marked experimental. Its own changelog lists dashboards, data tables, multi-step forms, code editors, native mobile and realtime collaborative UIs as out of scope for the main skill. If you are building a dense enterprise dashboard, blindly turning the design-variance dial to 10 is probably how you end up spending tomorrow undoing today's creativity.

For Claude Code, start with the normal design-taste-frontend skill. For Codex, the repo offers gpt-taste when you want stronger layout variance and motion direction. The stricter GPT/Codex version is considerably more opinionated: it enforces an AIDA page structure and heavy GSAP direction, so I would not use it for every restrained product UI just because the filename says GPT.

How to Install Taste Skill

npx skills add https://github.com/Leonxlnx/taste-skill --skill "design-taste-frontend"

2. Impeccable: Best for Fixing and Polishing What the Agent Built

Impeccable is the least interesting to explain in a Reel and probably the easiest one to keep using on a real project.

Paul Bakaus took Anthropic's frontend-design skill as a starting point and built a much larger design system around it. According to the current Impeccable documentation, the project has one main skill, 23 commands, live browser iteration and 59 deterministic rules that can flag common AI-generated frontend problems without needing another model call.

The setup is a big part of why I like it. /impeccable init can write a PRODUCT.md and offer a DESIGN.md, giving later passes context about the product, audience, colors, typography, components and the things you do not want changed. Then commands such as critique, audit, polish, bolder and quieter give you much more precise steering than repeatedly saying "make it look more professional."

I find that especially useful on an existing site. I do not always want an agent arriving with a grand new art direction. Sometimes the site already has one and I need the AI to stop mangling it. Impeccable's current workflow is designed to read an existing system before making changes, which is a far more sensible job for a design skill.

The community experience is not universally magical. One Claude Code user described Impeccable as "very thorough" if you are patient. A Codex user had the opposite experience and complained that even with Impeccable the UI still had too much explainer text, "borders upon borders and cards all over the place." Somebody replying to him immediately asked whether he had done the initial setup.

That little argument tells you more than another 40-second demo. Installing a skill is not the same as briefing it properly, and a rule system can only correct the things it knows how to see.

You may also have seen the old claim that Impeccable picked up 15,000 GitHub stars in its first few days. That number was repeated all over social media and third-party coverage. Historical star timing is much harder to verify cleanly from GitHub today, so it is a silly thing to build the recommendation around. The current number is easy to check: the repo is sitting around 56,000 stars as I write this, which is enough evidence of interest without adding folklore on top.

How to Install Impeccable

Setup is simple:

npx impeccable install

Then run /impeccable init inside the coding agent before expecting the rest of the workflow to understand your project.

3. Emil Kowalski's Skills: Best for Animation and the Last 10 Percent

Emil's skills come in after the page already looks good. His Skills for Designers and Engineers repo says the rules are based on his years of experience working at companies including Vercel and Linear. The main emil-design-eng skill is focused heavily on animation, but the repo also includes animate, review-animations, improve-animations, find-animation-opportunities, animation-vocabulary, pick-ui-library and a prototyping skill.

"Add premium animations" is another wonderful AI prompt if your goal is to make every object on the screen float in from somewhere.

Emil's rules are much more specific. They make the agent think about easing, duration, the properties being animated, how often an interaction happens and whether the animation should exist in the first place. His find-animation-opportunities skill is explicitly supposed to find places where motion helps while also telling you what should stay still. The animate skill even begins by deciding whether something should animate before it reaches easing or duration.

Good motion design works more like this. A button moving for the sake of movement does not make a product expensive; small interaction choices that feel immediate, intentional and consistent are what sell it.

Kowalski explains the idea well in his own piece, Agents with Taste. His argument is that experience eventually lets a designer explain why one motion choice feels better than another, and that knowledge can then be transferred into instructions an agent can use. His repo even gives the example of an enter animation choosing ease-in when ease-out would make more sense.

I would not use Emil's pack as my only design skill for the same reason. It can improve the motion and interaction judgment of a page with bad typography, weak hierarchy and a boring layout, but the underlying design is still bad. Motion can polish a good page; it cannot resuscitate a bad one.

How to Install Emil Kowalski's Skills

Install the pack with:

npx skills@latest add emilkowalski/skills

The Viral Version vs What These Skills Really Do

All three are good enough without the social-media mythology around them.

The last line is the one people do not want to hear because it is terrible content for a viral Reel. There is no npx install taste command for the person making the final call.

Should You Install All Three Design Skills?

Yes, I would install all three. I just would not throw all three at every design task at the same time.

For a new marketing site or landing page, I like Taste -> Impeccable -> Emil. Taste helps establish a less predictable art direction. Impeccable gives you a structured critique and cleanup pass once the direction exists. Emil comes in when you are deciding how the page should move.

For an existing website, start with Impeccable. Let it read the system that is already there, document it, critique the current page and fix the obvious AI habits. Bring in Taste if you want a larger redesign rather than a polish pass. Add Emil when motion is part of the brief.

If you are working on a dense dashboard or serious product UI, read Taste's scope before blindly copying somebody's setup from X. Its main v2 skill openly says several of those interface types are outside its intended job. That is good documentation, not a weakness. The weakness would be ignoring it because somebody's 20-second before-and-after looked cool.

These skills can make Claude Code and Codex much better design partners. They still need somebody on the other side of the screen willing to say, "No, that looks like shit. Try again."