better-interface

Topics in the source

• Interface
• Evidence, not taste
• 1. Resolve the scope first
• 2. Send a change to interface-review
• 3. Recon before judgment
• 4. Use domain skills as the sources of truth
• 5. Verify what can be verified
• Require evidence

This skill runs a cross-discipline review. It routes the interface to each better- skill, collects their evidence and consolidates one ranked verdict. Orchestration is all it owns. 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. Change-scoped review of uncommitted work, branches and pull requests belongs to interface-review. Press hard on the escalation triggers and leave deliberate project choices alone. A trigger is a failure whatever the style guide says. A density, radius or voice you merely disagree with is not a finding. The bar for reporting is evidence. The bar for Approve is that you inspected what you claim to have inspected. Infer the screen, flow, feature or repository scope from the request and current workspace. State the resolved scope in the output. Cover all of it in every domain, including the empty, loading, error and narrow-width states where they exist. When the scope is too large to inspect credibly, narrow it to one complete flow. Take the one the request centers on, or failing that the entry path every user must pa

This is an excerpt. Refer to the complete source and its current requirements.