critique

Topics in the source

• Review before you show
• Capture
• Score each capture, 0 to 10
• Report

The person should never be the first one to find an overflow, a clipped menu or a spinner that never ends. You find them first, from screenshots of the real screen. For each screen you changed: light and dark theme, desktop and phone width. For each surface that loads data, all five states: 1. Loading: a skeleton in the shape of what is coming; after 15 seconds, a line saying it is taking longer than usual. 2. Empty: a real empty state that says what to do first. 3. Error: the cause in plain words and a way to retry, with what the person typed kept. 4. Populated: realistic data. 5. Edge: long names, many rows, missing optional fields. | Axis | Ask | |---|---| | Coherence | Does it follow the design system exactly: spacing, type, components, icons? | | Hierarchy | Is the one thing that matters most the first thing the eye lands on? | | Detail | Alignment, overflow, truncation, padding, nothing touching an edge? | | Function | Do controls work, answer a 44 px touch target, show focus, and give field errors under the field? | | Distinction | Is there one deliberate choice that makes it feel made, not generated? | Fix everything under 7 and capture again. Three short lists: Kept (what

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