Write one journey with a real ending
Start with “A visitor opens a case, understands the offer, signs in, returns to the case, and reads the content they are entitled to.” For a shop, use “find a product, select a variant, understand delivery, and complete the intended order step.” Put each screen beside its loading, empty and failed state. The end should be something the user can verify, not “button clicked.” This keeps an AI coding assistant from polishing screens while leaving the transitions imaginary.
Make Back, refresh and deep links part of the brief
Open an article directly while signed out. Start login and cancel it. You should still be able to read the public section. After successful login, return to that same article, not an unexplained dashboard. Refresh and check that identity remains correct; sign out and check protected access separately. Then filter the case library, open a result, and use Back. The filter and your place in the list should remain understandable. A local demo flag does not verify any real authentication or paid entitlement.
Try the phone conditions a screenshot hides
Use a narrow viewport, longer text and the on-screen keyboard. Labels must remain visible; buttons need space for touch; important actions cannot depend on hovering. Resize an open menu or dialog and confirm it still fits. Test keyboard focus and reduced-motion preferences as well. MDN’s mobile guidance explains why touchscreen controls, responsive layouts and appropriate input types deserve attention beyond the desktop view. A viewport test is useful, but it is not a substitute for every real device or assistive-technology check.
Supporting documentation (opens in a new tab)Use this four-row acceptance record
Row one: valid form input leads to a visible result once. Row two: invalid input names the problem and retains what can safely be retained. Row three: an interrupted request leaves a retry path without duplicating a purchase or submission. Row four: refreshing the result page preserves the correct state. For each row, record the exact page, steps, expected behavior, observed behavior and anything you did not test. These are our suggested checks; an AI saying “all good” is not the observation.
Deliver the experience, not the picture
Keep an inventory of real images, fonts, source links, rights and fallbacks. A video blocked by its host needs an understandable original link; it should not leave an unexplained empty rectangle. Before accepting the build, ask someone to enter through a deep link and find the next step without your narration. The useful handoff is a working route, the checks that were performed and the remaining boundaries. It is not a screenshot, a passing build alone, or a promise that a customer transaction worked when payment was simulated.
Put this method beside a concrete example.
Inspect the related case →Our evaluation framework, not a controlled test or a guarantee of results.
Explore the free Jev collection →