better-interface
Review the interface as one system
A strong interface is not six independent audits stapled together. Review the whole experience, let each better-* skill own its domain rules, then consolidate the evidence into one prioritized verdict.
This skill owns orchestration only. 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. Never duplicate or override their rules here. Change-scoped review of uncommitted work, branches, and pull requests belongs to interface-review, which resolves the scope and classifies findings before handing the review back here.
Core Principles
1. Resolve Scope and Mode First
Parse the invocation as [quick|full] [scope]. The first token is a mode only when it is exactly quick or full; anything else is part of the scope. Mode defaults to full.
Infer the screen, flow, feature, or repository scope from the request and current workspace. State the resolved scope in the output.
| Mode | Coverage | Finding cap |
|---|---|---|
quick |
The primary path through the scope and the states it actually reaches; report only HIGH and MEDIUM issues |
5 |
full |
Entire requested scope across all six domain skills, including empty, loading, error, and narrow-width states when present | 15 |