Jakub Krehel's skills: 15 skills that review and polish a UI
Someone had /teardown build a page explaining how an engine works, and posted the result on X
- Who
- Jakub Krehel, who writes the design engineering magazine Interfaces, for people building UI with an agent.
- When
- The repository opened on 10 July 2026 and was pushed to as late as 10 November 2026, with no release tags; the plugin is at 1.19.2.
- Where
- A plugin in Claude Code, or npx skills for other agents. It runs inside your own project.
What was hard
Ask an agent for a screen and you get one that works. But the icon-only close button has no name, the body text is too faint to read, and at a narrow width a button gets clipped. Saying "make it nicer" again leaves what to change, and how, just as vague.
What it does about it
This repository writes down what makes an interface good as one skill per area. better-interface calls the accessibility, layout, writing, typography, color and UI polish skills in turn on one screen, then returns a single table ranked by severity, each finding with its file and line and a before and after. It judges on evidence, not taste, so a button with no accessible name or a missing focus ring is HIGH even on a minor screen.

What people made with it

Had the /teardown skill build an HTML page that explains how an engine works, and posted the screen, calling it fun.
/teardown スキルを使って、エンジンの仕組みを解説するHTMLページを作ってもらった。
How it runs inside
- 1
You → Claude Code
One sentence asking for a reviewThe request decides whether a screen, a flow or a feature is looked at. - 2
Claude Code → better-interface
Resolve the scope and state itToo large a scope is narrowed to one flow, and nothing uninspected is implied to be reviewed.skills/better-interface/SKILL.md - 3
better-interface → Your project's code and docs
Read the stack, tokens and convention docsIt reads CONTRIBUTING.md, AGENTS.md and the like first, and writes fixes in the project's own idiom.skills/better-interface/SKILL.md - 4
better-interface → The six better-* skills
From accessibility through to UI polishThe domain skills load in order: accessibility, layout, writing, typography, colors, UI.skills/better-accessibility/SKILL.md - 5
The six better-* skills → better-interface
Findings, each with file:lineEvery finding cites a file and line and shows the current code. What could not be checked is Not verified.skills/better-interface/SKILL.md - 6
better-interface → Ranked report and verdict
One HIGH/MEDIUM/LOW table and Block or ApproveOne root cause is one row, 15 findings at most. Any remaining HIGH means Block.skills/better-interface/review-format.md
What goes in, what comes out
Is it for you
Good for
- Getting a list of what is missing before a screen an agent built goes out
- Developers and one-person teams building product UI without a designer
- Checking before merge whether a pull request regressed the interface (interface-review)
- Needing an exploded view or other technical illustration for a post or a talk (teardown)
Not for
- A review is read-only by default. Ask separately if you also want the findings fixed.
- A report holds at most 15 findings. Past that it lists the HIGH ones first and says how many were left out.
- Skills such as interface-review, break and variant only start when you invoke them yourself.
- A teardown drawing explains and presents. Nothing is toleranced, so it is not a drawing to make a part from.
Reviewed by Devalley’s editor before publishing. How the column is made