better-interfacelisted

# 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. ## 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 `full` when no mode is supplied. | Mode | Coverage | Finding cap | | --- | --- | --- | | `quick` | Primary user path and highest-traffic states; 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 | If the requested scope is too large to inspect credibly, narrow it to the highest-traffic complete flow and state the boundary. Never imply uninspected surfaces were reviewed. ### 2. Recon Before Judgment Identify the framework, styling system, component library, design tokens, supported viewports, and available preview or test commands. Follow the project's established Tailwind, plain CSS, CSS-in-JS, token, and component conventions.