Coding & developmentFrontend QAcode
Find the forgotten UI states
Reviews a component beyond the happy path.

Ready to use
Prompt
Inspect [COMPONENT SOURCE] and [USER JOURNEY]. Enumerate loading, empty, error, unauthorised, stale, success and mobile states, plus keyboard and screen-reader behaviour. For each state, note whether it is present, missing or unverified, with a source line or reproducible test. Propose the smallest patch sequence and acceptance criteria; do not write implementation until asked. Return a state matrix and two high-value manual test scripts. Do not mistake hidden controls for inaccessible controls without testing. If live rendering is unavailable, label visual findings as code-inferred rather than observed.