Taste Skill vs Impeccable: Which Design Skill to Pick?

Taste Skill vs Impeccable — which one should you install? Pick Taste Skill if you want a fast, opinionated first draft of a landing page or portfolio. Pick Impeccable if you are building or refining a real product interface — an app, a dashboard, or a page where the facts on screen must stay exactly true to your product. Both skills attack the same problem, the generic look of AI-generated interfaces, but they do it in opposite ways: Taste Skill sets a direction and gets out of the way, while Impeccable builds a design system around your product and then checks the work against it.

What Taste Skill actually does

Taste Skill is a single, long set of frontend design rules that your coding agent reads before it writes any interface code. It starts by forming a "design read" of the page you asked for — what the page is for, who it is for, and what feeling it should leave — and then sets three dials that control how bold, how experimental, and how restrained the result should be. From there it follows a list of banned patterns: the purple gradients, the identical rounded cards, the grey all-caps labels, and the other tells that make generated pages look interchangeable.

The practical effect is speed. There are no commands to learn and no extra files to maintain. You describe the page, the agent applies the rules, and you get a landing page that looks deliberately designed rather than assembled from defaults. That simplicity is also the limit. Taste Skill has no memory of your product across screens and no built-in check that the finished page obeyed its own rules. It is strongest on the first page of something new — a landing page, a portfolio, a redesign of a marketing page — and weakest where consistency across many screens matters more than one striking first impression.

What Impeccable actually does

Impeccable is a design language, not just a rule list. It ships with 24 commands, a set of playbooks, and an anti-pattern detector, and it works in two distinct modes: one for brand and marketing surfaces, one for product interfaces. When you start a job, it writes a PRODUCT.md that records what your product actually is — its features, its pricing, its limits — and then, as it builds, a DESIGN.md that records the system it shipped: type, colour, spacing, and component rules.

That paperwork is the point. Because the agent has a written record of what is true about your product, it is far less likely to invent testimonials, feature lists, or pricing details that were never in your brief. Because it has a written design system, later screens can follow the first one instead of drifting. And because it ships a detector, you can run a check over a finished page and get a list of anti-pattern findings to fix. The trade-off is effort and cost: more commands to learn, more files to keep, and noticeably longer, more expensive runs than a single-rule skill, because the agent does more thinking, more auditing, and more passes over its own work.

Taste Skill vs Impeccable: how they differ

The difference is not quality — it is what each skill is built to control:

• Scope. Taste Skill is built for landing pages, portfolios, and redesigns. Impeccable is built for any interface, including apps and dashboards where many screens must stay consistent.
• How you steer it. Taste Skill steers through its three dials and its banned-pattern rules, applied to the whole task at once. Impeccable steers through named commands such as shape, audit, critique, polish, bolder, quieter, and animate, so you can ask for a specific kind of change at a specific moment.
• Memory. Taste Skill leaves nothing behind except the page itself. Impeccable leaves PRODUCT.md and DESIGN.md, so the next session starts from the same facts and the same system.
• Checking. Taste Skill has no shipped checker; you judge the result by eye. Impeccable ships a detector you can run over finished pages, including in a review step before merge.
• Effort. Taste Skill is close to zero setup: install it and describe the page. Impeccable asks you to learn its commands and to keep its product and design documents current, and it pays that effort back on longer projects.

If you only remember one line, remember this: Taste Skill improves the next page you generate, while Impeccable improves every page after the first one.

Which one should you pick?

Work through these four questions in order, and the answer usually picks itself:

• What are you building? A landing page, a portfolio, or a one-off marketing page points to Taste Skill. An app, a dashboard, a settings screen, or any interface with real user data points to Impeccable.
• How much must stay true? If invented copy would be embarrassing or harmful — wrong pricing, features you do not ship, testimonials from people who do not exist — Impeccable's product record is the safer choice. For a concept page where every fact is yours to invent anyway, Taste Skill is fine.
• How many screens? One screen favours Taste Skill. Five screens that must look like one product favour Impeccable, because its design document is what keeps screen five consistent with screen one.
• How much process do you want? If you want to describe a page and get a result, choose Taste Skill. If you enjoy iterating — shape it, critique it, make it bolder, audit it — Impeccable's commands give you handles for each of those moves.

A useful rule of thumb: choose the skill that matches the job's second page, not its first. The first page is where both skills shine. The second page is where a skill without memory starts to drift, and where a skill with a design system starts to pay off.

Can you use both together?

Yes, and for some teams this is the best answer. Use Taste Skill to set the initial direction — its dials are a fast way to escape the default look and land on something with a point of view. Then hand the result to Impeccable's audit and critique commands, or use its detector, to check the page against anti-patterns and to record the surviving decisions in a design document. The order matters: direction first, system second. Reversing it — building a full design system before you know what direction you want — spends the most effort where it helps least.

One caution: do not install both and let them run unguided on the same prompt. Two opinionated systems pulling in different directions produce a page that looks negotiated rather than designed. Give one of them the lead for each job, and use the other for a defined step, such as a final audit.

How to get started with each

Getting started with Taste Skill is deliberately simple. Install it from its repository — Leonxlnx/taste-skill on GitHub — and then describe the page you want, including what it is for and who it is for. If the result feels too safe, ask for a bolder direction; if it feels too wild, ask for a quieter one. The skill's dials respond to plain language, so you do not need to learn a command vocabulary first. For a fuller walkthrough of what it enforces and how to install it, see our Taste Skill guide for Claude Code.

Getting started with Impeccable takes one extra step that pays off immediately: write down the product facts before you ask for a page. Install it from pbakaus/impeccable on GitHub, then give the agent your real features, pricing, and constraints, and let it build the product record first. After the first page, try audit on the result before you ask for changes — the findings list is often a better brief for the next pass than your own first impression. If you are choosing between the two anti-slop leaders and a third option, Hallmark is worth a look too: it is another anti-slop skill with its own build, study, audit, and redesign modes.

FAQ

Is Taste Skill free? Yes. It is an open-source skill you install from its repository, and it works with Claude Code, Cursor, and Codex.

Is Impeccable free? Yes, it is open source as well, and it works across Claude Code, Cursor, Codex, Copilot, and Gemini CLI, among others.

Do I need both skills? No. Most people need one, chosen by the job: Taste Skill for a fast landing page, Impeccable for a product interface. Add the second only when you have a defined step for it, such as a final audit.

Which one is better for a dashboard? Impeccable. Dashboards are many screens with real data, and that is exactly where a recorded product model and design system earn their keep.

Which one is better for a first landing page? Taste Skill. It reaches a designed-looking result with the least setup, and you can always audit the result afterwards.

The bottom line

Taste Skill vs Impeccable is not a contest with one winner. Taste Skill is the faster, simpler way to make a single page look designed. Impeccable is the heavier, more systematic way to make a whole product look designed — and to keep its facts honest along the way. Match the skill to the job's second page, not just its first, and you will rarely pick wrong. If the job is a single page that needs to look good this week, install Taste Skill and describe the page well; the dials and the banned-pattern rules will do most of the work. If the job is a product that will grow screen by screen, invest the extra setup in Impeccable, write the product facts down first, and let its design document carry the consistency for you. Start with Taste Skill for your next landing page, and reach for Impeccable the moment the interface becomes a product.