
better-interface
Reviews a screen, flow or whole interface across accessibility, layout, writing, typography, color and UI polish, and returns one ranked report.
- Installs
- 37.1K
- Last 24h
- +539
- Trending rank
- #637
- Security
- Pass
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/jakubkrehel/skills --skill better-interface- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads better-interface automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
Security audits
Independent scans of the skill's instructions and bundled files, each dated to when it ran.
SKILL.md
The instructions your agent reads when the skill is triggered.
Interface
This skill runs a cross-discipline review. It routes the interface to each better-* skill, collects their evidence and consolidates one ranked verdict.
Orchestration is all it owns. Accessibility rules belong to better-accessibility, structure to better-layout, copy to better-writing, type to better-typography, color to better-colors, visual polish and motion to better-ui.
Change-scoped review of uncommitted work, branches and pull requests belongs to interface-review.
Evidence, not taste
Press hard on the escalation triggers and leave deliberate project choices alone. A trigger is a failure whatever the style guide says. A density, radius or voice you merely disagree with is not a finding.
The bar for reporting is evidence. The bar for Approve is that you inspected what you claim to have inspected.
1. Resolve the scope first
Infer the screen, flow, feature or repository scope from the request and current workspace. State the resolved scope in the output.
Cover all of it in every domain, including the empty, loading, error and narrow-width states where they exist.
When the scope is too large to inspect credibly, narrow it to one complete flow. Take the one the request centers on, or failing that the entry path every user must pass through. State the boundary and what it excluded. Never imply uninspected surfaces were reviewed.
2. Send a change to interface-review
A request naming a branch, pull request, commit range or uncommitted changes is a change review. Say so and ask the user to run interface-review, which is user-invoked and cannot be started from here. Never resolve a change scope yourself, because a guessed diff gives the report a scope nobody can check.
When interface-review hands a review back, apply everything below to it. The cap and the verdict cover Introduced and Regression findings only, so a change whose only findings are Pre-existing is an Approve.
3. Recon before judgment
Identify the framework, styling system, component library, design tokens, supported viewports and any preview or test command. Write every fix in the project's own idiom, never as a request to adopt a different stack.
Then read what the project has written about its own interface: CONTRIBUTING.md, CODING_STANDARDS.md, AGENTS.md, CLAUDE.md, a design-system doc, Storybook docs and interface ADRs. Name which you found, or that there are none.
A documented convention settles matters of taste but never excuses a trigger or a domain rule violation. What it changes is where you report. When a guideline or shared token is the cause, report it once against that source, with the components as its locations.
4. Use domain skills as the sources of truth
Load every owning skill below and complete each domain review before consolidation. Review in this order so foundational failures are not hidden by polish:
better-accessibilitybetter-layoutbetter-writingbetter-typographybetter-colorsbetter-ui
From each, take its principles, its references and its verification checks. Its severity ladder and its format are for standalone use; the ones in this file replace them.
If an owning skill is unavailable, mark that domain Not reviewed, name it and continue with the rest. Do not recreate its rules from memory, substitute a neighbour or claim holistic coverage.
When two skills appear to cover one issue, assign it to the owner of the underlying rule and note secondary effects in the Why cell.
5. Verify what can be verified
Run the safe, relevant checks the project offers. Inspect the rendered interface when runtime behavior or visual judgment matters, and report the exact command or interaction and its result. A check you cannot run is Not verified, never a finding.
Require evidence
Every finding cites path/to/file:line and shows the current implementation. When runtime behavior determines the result, source alone cannot support a visual finding and a screenshot alone cannot support a code finding.
Rank by user impact
Use one shared severity scale:
HIGH: blocks a task, misleads the user, hides content or controls, causes data-loss risk or creates a repeated systemic failure.MEDIUM: meaningfully harms comprehension, efficiency, adaptability or consistency.LOW: isolated polish with limited task impact.
Within a severity, rank by how many places the finding reaches and how much one fix buys. A token or shared-component fix outranks the same symptom in one leaf.
Escalation triggers. Once the owning skill confirms one of these, it is HIGH on sight, never averaged down because the surface is minor:
- An interactive control with no accessible name.
- A keyboard-reachable control with no visible focus indicator.
- A control or path reachable by pointer but not by keyboard.
- Motion or auto-playing content that ignores
prefers-reduced-motion. - Content or a control clipped, overlapped or unreachable at 320px width or 200% zoom.
- Body or control text whose rendered contrast pair fails its required ratio.
- State or meaning carried by color alone.
- A destructive action with no confirmation, undo or distinct treatment.
- Truncated content with no way to reach the full value.
- Content or a control reachable only past a scroll edge or behind a disclosure that has no visible cue.
- An error that names no way to recover from it.
- A semantic color used against its meaning, such as the danger hue on a non-destructive action.
- A state change carried by motion alone, with no color, icon or label left behind when the animation does not run.
Triggers rank above every other finding. When more fire than the cap allows, list them first and say how many the cap excluded. A cap may shorten a report; it may never be why a blocker went unreported.
These set severity, not new rules. The owning skill decides whether the symptom is present; this list decides what it costs.
Prefer the cheaper fix
Severity says how bad a finding is; this says which fix to propose. When more than one would work, take the earliest that does:
- Delete. A separator that space would carry, an animation on a high-frequency interaction, an ARIA attribute a native element makes redundant, a ramp nothing imports.
- Use the platform. The native element, the native control or the browser's own focus ring, in place of a custom rebuild.
- Reuse what the project has. An existing token, spacing step or motion curve, before any new value.
- Correct the value. The wrong easing, radius, gap or contrast pair, using the exact value the owning skill gives.
- Add. A new token, a wrapper, a media query, an ARIA attribute the platform cannot supply.
When the code under review adds what Delete would fix, that is a finding, and its After is the deletion.
Consolidate systemic findings
One root cause is one finding, with every confirmed location in the same row. Report at most 15 findings. Never pad toward the cap; a short review or no findings is a valid result.
Review without mutating by default
Treat a review request as read-only. Do not edit source unless the user also asks you to implement the findings. When they do, keep the consolidated report as the change scope and re-run the relevant verification afterward.
Before you finish
| Mistake | Fix |
|---|---|
| A separate findings section per domain | Merge them into one table ranked by severity, then reach |
| A rendering claim whose only evidence is source | Inspect the rendered state, or mark it Not verified |
A missing accessible name or focus ring rated MEDIUM because the surface is minor | Triggers are HIGH on sight |
| A coverage row whose evidence cell names no file, component or check | Inspect that domain, or mark it Not reviewed with the reason |
A domain marked Clear although its skill never loaded | Mark it Not reviewed and name the skill |
| The same symptom in several rows, one per component | One row against the shared token or component, listing every location |
| An After that adds a wrapper, token or ARIA attribute | Check whether a deletion or the native element fixes it first |
| A fix written in a library or styling system the project does not use | Rewrite it in the project's own idiom |
Review output format
The format lives in review-format.md: scope and coverage, the findings table, verification and the verdict. A review is not finished until its findings are reported there.
FAQ
What does the better-interface skill do?
Reviews a screen, flow or whole interface across accessibility, layout, writing, typography, color and UI polish, and returns one ranked report.
How do I install better-interface?
Run npx skills add https://github.com/jakubkrehel/skills --skill better-interface in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/better-interface/ (personal) or .claude/skills/better-interface/ (project).
Which AI agents can use better-interface?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is better-interface safe to install?
Security partners have reviewed it: Gen Agent Trust Hub passed; Socket passed; Snyk passed. As with any skill, read the SKILL.md and bundled scripts before installing.
Who maintains better-interface?
It is published by jakubkrehel in jakubkrehel/skills. It has 37,053 recorded installs.
More from jakubkrehel/skills
better-ui
jakubkrehel/skills
Polishes surfaces, icons and motion with exact values for border radius, optical alignment, shadows, icon states and animation.
better-typography
jakubkrehel/skills
Sets and reviews how text renders, from the type scale and spacing to font features, wrapping, truncation and punctuation.
better-colors
jakubkrehel/skills
Builds and checks color systems by generating palettes, naming semantic tokens, converting between formats and measuring contrast.
better-layout
jakubkrehel/skills
Sets grouping, alignment, reading order, responsive structure and room for translated text, so a layout holds up when it is resized, translated or mirrored.
better-accessibility
jakubkrehel/skills
Reviews and fixes keyboard and focus behavior, ARIA, accessible names, forms, screen-reader announcements, motion and zoom against WCAG 2.2.
better-writing
jakubkrehel/skills
Writes and reviews interface copy, from labels and errors to empty states and confirmations, so it matches the product's voice and tells people what to do next.
Popular frontend & design skills
setup-matt-pocock-skills
mattpocock/skills
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
frontend-design
anthropics/skills
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
ui-taste
uizze.sh
Give your coding agent better UI taste. Build and polish web and iOS interfaces with Uizze's anti-ui-slop playbooks and optional real-product references. Use for UI design, implementation, redesign, critique, or a final visual review in Claude Code, Codex, Cursor, or Copilot.
prototype
mattpocock/skills
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
hyperframes-animation
heygen-com/hyperframes
All animation knowledge for HyperFrames — atomic motion rules, multi-phase scene blueprints, scene transitions, broader motion-design techniques, AND the seven runtime adapters (GSAP default, plus Lottie, Three.js, Anime.js, CSS keyframes, Web Animations API, TypeGPU). Use for any motion or animation task: pick 2-4 rules and compose, or load a blueprint, or look up runtime-specific API (e.g. GSAP eases / Lottie player / Three.js mixer). Also covers auditing an existing composition's choreography (animation map) and 24 named text-animation effects. HyperFrames-native: single paused timeline, seek-safe, deterministic.
hyperframes-core
heygen-com/hyperframes
The HyperFrames composition contract — build one renderable project. Use for composition structure, the data- timing attributes, class="clip", tracks, sub-compositions, variables, framework-owned media playback, deterministic-render rules, and validation. Read before writing composition HTML.