better-interface
Coordinates an interface review across six areas.
- Status
- Observed
- Last reviewed
- 2026-10-10
ID: better-interface.
What it does
Defines a specific screen or flow and applies accessibility, layout, writing, typography, color and UI detail checks, in that order. Combines issues into one list ordered by user impact, consolidating defects with the same cause. Includes empty, loading and error states and relevant widths. The review is read-only until you ask to apply its findings.
When to use it
Use it when you explicitly request a comprehensive assessment of an experience. If the problem is already bounded, use the skill for that domain. Reviews of branches, PRs or uncommitted changes instead follow the interface-review procedure, if available.
How to use it
Ask for it by name, or invoke it with /better-interface in Claude Code or $better-interface in Codex. Name the flow, goal, states and review scope. Request one table with evidence, priorities and corrections; the report must distinguish what was observed from what was not checked.
What it delivers
- Scope and coverage of the six areas
- Consolidated issue list, up to 15 findings
- Checks performed and review outcome
Example
Review the entire project creation flow, from entry to success, including errors, the empty state and mobile. Deliver findings only for now.
Prerequisites
- Requires the six better-* skills in the catalog; a missing area is declared unreviewed.
Executable instructions
The skill is installed from the source maintained by jakubkrehel; its license applies.
In the workflow
Use the router to choose this capability based on the required outcome.