Unsaved Changes Guard
Stop people navigating away from work they have not saved.
What it adds
A warning on any attempt to leave a form with genuine unsaved changes, covering routing and browser navigation.
What your agent is told to do
5
What your agent is told to do
5-
1
Compare the current form values against the values it loaded with. Track real changes, not merely whether a field was focused.
-
2
Cover all four exits: internal navigation, the back button, a page reload, and closing the tab.
-
3
Name what is at risk in the warning and offer to save rather than only to discard.
-
4
Clear the guard immediately on a successful save, an autosave, or an explicit reset.
-
5
Do not warn on a form the user never meaningfully touched. A guard that fires on an accidental keystroke gets dismissed on reflex, including the time it mattered.
Edge cases it handles
6
Edge cases it handles
6- A field typed into and then changed back is not a change. Compare values, not events.
- A failed save must leave the guard in place and the data intact, not trap the user with no way out.
- A save still in flight should block navigation with a pending state, not a scary dialog.
- The browser's own beforeunload prompt cannot be styled or given custom text. Do not try; use it only for reload and tab close.
- Deliberate sign-out and session expiry must not fight the guard.
- Multi-step forms must guard the whole flow, not each step in isolation.
Definition of done
7
Definition of done
7- Leaving a dirty form warns on internal navigation, back, reload, and tab close.
- An untouched form, or one edited back to its original values, never warns.
- A successful save or reset clears the guard immediately.
- The warning offers to save, not only to discard.
- A failed save leaves the user on the form with their data.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Voice Dictation
Voice Dictation
Put a microphone in text fields so people can speak their input instead of typing it.
What it does
A dictation control on the app's longer text inputs that transcribes speech into the field as the user talks.
How it works
- 1 Add the control to the fields where typing is genuinely tedious: long descriptions, notes, comments, and message bodies. A microphone on a postcode field is clutter.
- 2 Show interim results in the field as they arrive, visually distinct from committed text, so the speaker can see it is working and correct course before they finish.
- 3 Reuse the app's existing Voice Transcription for the server-side path so one recognition configuration and one set of language settings serve both dictation and recorded audio.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/voice-dictation
Help Text Pattern
Help Text Pattern
Put field guidance in one predictable place, phrased the same way every time.
What it does
A consistent treatment for the short explanatory text that sits with a field and its control.
How it works
- 1 Collect the guidance the app currently scatters across placeholders, tooltips, asterisked footnotes, and modal help, and move it into one slot beneath the field.
- 2 Keep guidance that is required to complete the field permanently visible. A format rule hidden behind a hover target is not available to a touch user or a keyboard user.
- 3 Write help as the rule the user needs before typing — the accepted format, the consequence of the choice — not as a restatement of the label.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/help-text-pattern
Form Section Pattern
Form Section Pattern
Break long forms into labelled sections people can scan instead of read.
What it does
A section pattern grouping related fields under a heading, a description, and its own actions.
How it works
- 1 Find the forms that have grown past a screenful — settings, profiles, checkout, configuration — and group their fields by the question each group answers, not by the table the columns come from.
- 2 Give each section a heading in the document's heading order and an optional one-line description, so screen reader and keyboard users can jump between sections.
- 3 Allow at most one level of nesting. A section inside a section inside a tab gives the user no orientation and pushes the fields into a narrow gutter.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/form-section-pattern
How it works
-
1
Copy the link
Grab the Markdown instruction URL for this feature.
-
2
Give it to your AI
Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.
-
3
It inspects, then implements
Your agent reads your existing app first, then adds the feature to fit it.
Works with your stack
These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.
Need it tighter than that? Customize the feature and tell it exactly what you're running.