UI skills compared: Impeccable, Krehel, Kowalski

A press scale of 0.96 or 0.97, a 65-character measure or 75, a 300ms overlay or 500ms: install three good UI skills side by side and your agent gets three answers to each of these, then picks one at random. For most projects I would install ui from molveau/skills. It merges Jakub Krehel's skills, his make-interfaces-feel-better, Paul Bakaus's Impeccable and a taste guide distilled from Emil Kowalski's work into one playbook that settles those questions in writing. If you want one author's voice and nothing else, install the original, and the sections below say which.

The contenders

Skill	Author	Licence	Best at	Lacks
Impeccable	Paul Bakaus	Apache-2.0	A command per design move, critique and audit, live mode	A short path: it wants an install, an init step and context files
skills	Jakub Krehel	MIT	Exact values for layout, type, color and review	A direction step for a new screen
make-interfaces-feel-better	Jakub Krehel	MIT	The polish details: radii, shadows, optical alignment	Anything beyond polish, by design
skills (emil-design-eng)	Emil Kowalski	MIT	The taste and invisible details behind a polished interface	Layout and color depth; it leans on motion
frontend-design	Anthropic	Apache-2.0	A short brief toward a distinct direction	Values, review or checks
ui-ux-pro-max	nextlevelbuilder	MIT	A searchable database of styles, palettes and font pairings	A small footprint; it needs Python 3
ui	Molveau Studio	MIT	One playbook from direction to review, with the conflicts settled	Impeccable's scripts and live mode; a script of its own

Each one, fairly

Impeccable, by Paul Bakaus

Impeccable is the most complete design vocabulary I know for an agent: polish, bolder, quieter, distill, typeset, critique, audit and more, each loading a playbook for that one move. init writes a PRODUCT.md every later command reads. Its critique scores a screen against usability heuristics, and its live mode lets you pick an element in the browser and cycle through variants. My ui skill carries its reference files but not its scripts, so install Impeccable itself if you want the live mode or its detector.

Jakub Krehel's skills and make-interfaces-feel-better

Jakub writes the skills I trust for exact values. better-layout, better-typography, better-colors and better-ui say what to set and why, interface-review reviews a branch for UI regressions, and make-interfaces-feel-better covers the small details that make a screen feel finished. His repo has more skills than the ones I merge, such as build-design (from a Figma file or an image), variant, state-machine and break. Install his repo if you want those, or his writing without anyone else's.

Emil Kowalski's design engineering skill

Emil's emil-design-eng encodes how he thinks about polish, component design and the details people feel without naming. If you only want Emil's taste, install his skills. My ui skill carries a distillation of his work in my own words, with his numbers credited, and the verbatim copy of his skills lives in my motion skill.

frontend-design, by Anthropic

One file that asks the model to act as a design lead with a distinct point of view, grounded in the subject. It is a cheap first nudge on new UI. It gives no values and checks nothing, so it works best next to a skill that does.

ui-ux-pro-max, by nextlevelbuilder

A different kind of tool: an offline database of styles, palettes, font pairings and UX guidelines with a search script. When you need "a palette for a warm healthcare brand" as a query, it is the right install. It has a large footprint and needs Python, which is why I link to it instead of merging it.

What the merged skill adds

• Routing. One install. The SKILL.md maps each task to a file: typography opens Jakub's better-typography then Impeccable's typeset, a branch review opens interface-review, a too-busy screen opens distill and quieter. The agent reads what the task needs.
• Pinned, unedited copies. Every vendored file sits at a pinned commit under references/vendor/, never edited. A weekly GitHub Action checks upstream and opens an issue when a source moves; a person reviews each bump.
• A playbook that settles disagreements. Each conflict between sources gets a written call. Press scale: Jakub 0.96, Emil 0.97, unslop 0.97 to 0.98, the playbook takes 0.96 and accepts an existing 0.97. Durations: Emil keeps feedback under 300ms, Impeccable allows 300 to 500ms overlays, the playbook takes 150 to 250ms with overlays up to 300ms, because long feedback reads as latency.
• The direction gate. Five lines (product, character, world, moments, signature), an inventory of what only this product has, the second-order defaults to refuse, a swap test, then a pause for your approval.
• Checks through its neighbours. ui has no script of its own. Its done rule runs the anti-slop detector, then your type check, lint and tests, and it hands motion, copy and accessibility to the motion and ux skills.
• A prompt pack and a mockup-first rule for teams that review a mockup before code.

Install

The skill alone, with the skills CLI:

npx skills add molveau/skills -s ui

The design bundle:

npx skills add molveau/skills -s anti-slop -s ui -s ux -s motion -s design-grill -s design-inspiration-index

In Claude Code, all eleven skills as one plugin:

/plugin marketplace add molveau/skills
/plugin install molveau-skills@molveau

Every skill and bundle is on the skills page, and the source is at github.com/molveau/skills. Related comparisons: anti-slop skills, UX and accessibility skills, motion skills.

Checklist

• The project's tokens and DESIGN.md decide before any skill default.
• One design authority runs at a time, and its pass finishes before the next.
• A new screen has its five-line direction approved before code.
• Values that differ between sources follow the playbook's call, not the last file read.
• The anti-slop detector, type check, lint and tests pass before the UI is called done.
• If you need live mode, a database search or one author only, the original is installed instead.