The 5 skills that give your AI taste when it builds an interface
Your AI can code a page. It cannot make it desirable. Here are five skills you install once so your landing pages and product screens stop looking like everyone else's template.
August 7, 2026 · 7 min read
You ask your AI for a landing page. Forty seconds later you have something that works: a hero, three feature cards, a form, a footer. Everything lines up, nothing is broken. And you still know you cannot send it to a client.
The problem is not the code. It is taste. A model trained on millions of pages gives you the average of those pages: Inter everywhere, a purple to blue gradient, cards nested inside cards, a small icon in a rounded square above every heading. It is clean, it is dead, and people clock it in a second.
An interface that smells like a template costs you conversion before anyone reads a word.The good news: taste is installable. Skills are folders of instructions your agent loads when it needs them, and there are now five serious, free design skills, each fixing a different layer of the problem. This guide gives you all five, what each one adds, the exact install command, and the order to stack them in.
The Claude AI Lab is my Skool community where I share my Claude systems and the more advanced modules. Access is $67/month.
Join the Lab →/plugin slash commands built into Claude Code, and the npx skills CLI, which drops the files into your project or your user folder.Frontend Design, the official baseline
This is the skill Anthropic maintains in its public skills repository. It teaches Claude what a real front end looks like and how it should behave: visual hierarchy, density, component states, hover and focus behavior, responsive layouts that hold up on something other than a developer's monitor.
Start here. This is the foundation layer, the one that moves a page from "it compiles" to "it holds together." The other four refine on top of it.
/plugin marketplace add anthropics/skills./plugin install example-skills@anthropic-agent-skills. Frontend Design ships inside that set, so you pick up several example skills at once.UI UX Pro Max, the style library
This one answers a specific question: which style should you pick. It ships a design database your agent can search, with 84 interface styles and 161 reasoning rules for deciding which one fits your case.
In practice, you stop describing your style in three vague adjectives. You describe your product and your audience, the agent pulls a coherent style with its palette and typography, and it sticks to it across every page. This is the skill that solves cross screen consistency, the problem you notice when your pricing page does not look like your home page.
/plugin marketplace add nextlevelbuilder/ui-ux-pro-max-skill/plugin install ui-ux-pro-max@ui-ux-pro-max-skillTaste, the style dial
Taste bills itself as an anti slop framework for agents. Its distinctive move is tuning: instead of one fixed style, you adjust parameters and variants, like an equalizer. Quieter, denser, bolder.
This is the one to grab when you ship for several brands or several clients. You keep one method and move the dials, instead of re explaining your art direction on every new project.
npx skills add https://github.com/Leonxlnx/taste-skillnpx skills add https://github.com/Leonxlnx/taste-skill --skill "design-taste-frontend" if you only want the front end part.--skill keeps context your agent will never use out of the session. Make it a habit, it pays in tokens every time you work.Impeccable, the shared vocabulary
Impeccable is the most tooled of the five: one skill, 23 commands, and 59 deterministic detector rules that run without calling a model. Its core idea is a shared vocabulary with your agent. Instead of writing a paragraph to explain what you want, you type one word: polish, audit, critique, distill, animate, bolder, quieter.
It starts with a context pass. /impeccable init asks whether the surface is brand (marketing site, landing, portfolio) or product (app UI, dashboard, tool), then writes a PRODUCT.md and offers a DESIGN.md. Every later command reads those files, so the agent knows your audience, your voice and your colors without you repeating them.
npx impeccable install/impeccable init and answer the questions. This step is what makes the other 22 commands useful./impeccable audit on an existing page, /impeccable polish on a component that bothers you without you being able to say why.Emil Kowalski's skills, the motion layer
The first four handle what sits still. This one handles what moves: animations, page transitions, micro interactions. It is the layer you add last, and the one you feel immediately.
The author built interfaces at Vercel and Linear, and the skill encodes that kind of call: an enter animation that takes ease-out and not ease-in, a semi transparent shadow instead of a solid border. Taken one at a time, each detail looks negligible. Stacked across a whole interface, they are the difference between "fine" and "this looks expensive."
npx skills@latest add emilkowalski/skillsThe order to stack them in
The five do not compete, they layer. Install in this order, testing on a real page at each step:
If you install only one, take Frontend Design: it moves the line the most for the least effort. If you install two, add Impeccable, because running audit on a page you already shipped is the most instructive exercise on the list.
What this changes in your work
The real gain is not aesthetic, it is economic. A page that inspires trust converts better on the same traffic, and a product interface that explains itself generates less support. You pay for these skills once, at install, and they apply to every page you generate afterward.
The second gain is round trips. Without a shared vocabulary, you spend your iterations describing a feeling: "too busy", "it looks cheap", "I don't know, something is off." With one, you type a word and move on.
Want to go further?
In the Lab, I share my Claude skills, how I build them and how I stack them to automate my day-to-day.
A dedicated session or program, tailored to your tools and use cases.
And day-to-day, I post one reel a day on Instagram: @quentin_iamarketing