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. The same ownership runs forward: in build mode you consult the owners while implementing, then review your own diff against them.
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.
Core Principles
1. Resolve Scope and Mode First
Infer the screen, flow, feature, or repository scope from the request and current workspace. State the resolved scope in the output. Use core when no mode is supplied and the request is a review; use build when the request is to implement something. full is opt-in — it dispatches a judge lane per domain with candidates and costs accordingly.
| Mode | Coverage | Finding cap |
|---|---|---|
quick |
Primary user path and highest-traffic states. Detect across all six domains; judge inline, no lanes. Report only HIGH and MEDIUM |
5 |
core |
Detect across all six domains, then judge at most two, selected by the rule below. Unjudged domains are reported Detected only |
8 |
full |
Entire requested scope, including empty, loading, error, and narrow-width states when present. Detect across all six domains and judge every domain that produced candidates — no cap | 15 |
build |
Implement the requested change, then self-review the diff against the domains it touches. Selected-domain, not a six-domain sweep | 15, scoped to the diff |