ux

Walk the quick review checklist grouped by interaction type: Read for data views, Edit for input surfaces, Act for operations and buttons, Feedback for loading states, and Grow for discoverability. Each item links to a reference module with full requirements and examples.

Search, filters, sort, counts, and bulk actions must all query the full dataset server-side, not just loaded pages. Error states must render before empty states, and restored selections should scroll into view once their rows exist.

Use project loaders or skeletons matched to the measured layout instead of antd Spin. Every loading state needs a terminal failure path with retry, and init flags must not be gated on success-only fetches, which cause permanent skeletons.

Unrecoverable or wide-blast actions like clearing all data or deleting an account require a deliberate gesture such as type-to-confirm, not a one-click danger button. The operation must also report partial failures rather than silently half-completing.

DESIGN.md covers the static design system: theme tokens, components, and voice. The ux skill covers dynamic interaction behavior over time, such as state handling, flow momentum, and draft safety. Static look goes to DESIGN.md; behavior goes to this skill.