Prompt·Correctness and reliability·R07
Lost place: Back, refresh and shared links
Finds the everyday friction where Back closes the wrong thing, a filter resets, or a pasted link opens the wrong view.
Prompt
Check whether this application keeps the user's place. In a real browser, open lists, filters, tabs, panels and records, then press Back and Forward, refresh, open links in a new tab, and open shared links in a fresh browser both signed out and as another account. Find where users lose a filter, scroll position, draft or open panel, or land somewhere other than what was shared, and trace each case to where that state lives.
- What it returns
- Each case as a recorded journey (start, action, expected, observed) with the file and line that owns the state, and the journey runner's verdict: PASS, FAIL or EXPLORATORY.
- Skip it when
- Static sites with no filters, panels or signed-in pages.
- Changes
- Changes nothing
- Sessions
- One session
- Tools
- The app running locally or on staging with test accounts; Playwright, which the plugin looks for and asks before installing.
- Watch for
- Blocking data-changing requests does not make a browser run read-only, because some apps change data on an ordinary page load. Never point it at production with real accounts.
Related prompts
- Unit tests that give false comfortPromptFinds features whose automated checks all pass and that still break for real people.
- Screens that fight how people workPromptFinds when confusing screens are a symptom of how the product is organised rather than a list of separate bugs.
- Screens showing a change that was refusedPromptFinds screens that show a change right away and keep showing it after the server refused it.
More in Correctness and reliability.