Sensitive Field Reveal
Let users check a password or token without leaving it on screen.
What it adds
A consistent show/hide control for passwords, API keys, and other private values.
What your agent is told to do
5
What your agent is told to do
5-
1
Apply one reveal control to every sensitive field in the app rather than styling each form differently.
-
2
Preserve cursor position and any text selection when toggling — losing the caret mid-typing is the reason people abandon these controls.
-
3
Label the button by its action and update the label with the state, and expose the state to assistive technology rather than relying on an icon swap.
-
4
Auto-hide high-value secrets after a short idle period or on blur, and always start hidden after a page load.
-
5
Do NOT offer reveal on values the server only returns masked. A toggle that reveals asterisks is worse than no toggle.
Edge cases it handles
6
Edge cases it handles
6- The revealed value must not be exposed to browser autofill heuristics or password managers as a plain field.
- Copying a hidden value must copy the real value, not the mask.
- Revealed state must never persist across navigation or reload.
- Screenshot and screen-share risk is why timed auto-hide exists — pick the timeout deliberately and document it.
- The toggle must be reachable by keyboard and must not sit inside the field's tab order in a way that traps the user.
- A field the user cannot read at all — a write-only secret — needs a clear explanation instead of a disabled eye icon.
Definition of done
8
Definition of done
8- All sensitive fields use the same reveal control.
- Toggling preserves cursor position and selection.
- The button's accessible name reflects the current state.
- Fields start hidden on every load and auto-hide after the documented idle period.
- Server-masked values do not offer a reveal toggle.
- The control is fully keyboard operable.
- 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.