Better Interface is the orchestrator of a set of design-engineering skills. It resolves the scope of a review, loads each domain skill in a fixed order, collects their evidence and consolidates everything into one findings table ranked by user impact, ending in a Block or Approve verdict.
It owns no domain rules itself. Accessibility, layout, writing, typography, color, UI polish and motion each stay with their own skill, and a domain whose skill is unavailable is marked Not reviewed.
What You Get
- A scope and coverage section that names what was inspected in each of the seven domains
- One findings table with severity, domain, file and line, current code, replacement and the reason it matters
- Systemic findings merged into one row against the shared token or component, listing every location
- A verification section separating checks that passed from checks marked Not verified
- A Block or Approve verdict, where any remaining HIGH finding blocks
Common Use Cases
- Reviewing a new settings screen before release across all interface disciplines at once
- Auditing a checkout flow, including its empty, loading, error and narrow-width states
- Getting one ranked list of interface problems to hand to a team in place of seven separate reports
- Checking a repository’s shared components for systemic issues that repeat across pages
What Makes It Unique
It adds a shared severity scale and a list of escalation triggers, such as a control with no accessible name or text that fails contrast, that rank HIGH on sight. It also prefers the cheapest fix, trying deletion first, then the platform, then existing project tokens, then a corrected value, and adding something new last.
Under The Hood
The skill is a SKILL.md and one review-format file, and it contains no scripts. It reads the project’s own docs such as AGENTS.md, CLAUDE.md, CONTRIBUTING.md and design-system notes, loads the seven sibling better-* skills, may run the project’s safe check commands and may inspect the rendered interface in a browser. A review is read-only; it edits source only when you ask for the findings to be implemented. A change, branch or pull request review is sent to the interface-review skill.