Voice Dictation
Put a microphone in text fields so people can speak their input instead of typing it.
What it adds
A dictation control on the app's longer text inputs that transcribes speech into the field as the user talks.
What your agent is told to do
5
What your agent is told to do
5-
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.
-
4
Make the recording state unmistakable: a change of colour alone is not enough. Show an active indicator and a stop control that is always reachable.
-
5
Do not clear or replace the field when dictation starts. Speaking is usually an addition to something already written, and wiping existing text is unrecoverable if undo is not wired up.
Edge cases it handles
8
Edge cases it handles
8- Insert transcribed text at the current caret position and respect an active selection, rather than appending to the end or overwriting the whole field.
- Where the browser has no speech input support, hide the control entirely and leave a fully working text field. A microphone button that errors on press is worse than no button.
- Stop listening automatically after a stretch of silence, and tell the user why it stopped so they do not keep talking to a field that is no longer listening.
- Handle spoken punctuation and line breaks consistently, and document the phrases that work. Unpredictable punctuation makes every dictated sentence need a manual pass.
- Release the microphone when the field loses focus, the dialog closes, or the user navigates away. A stubbornly active recording indicator is alarming and looks like a bug even when it is one.
- Undo must treat a dictated block as a single step, so one keystroke removes it rather than fifty.
- Dictation into a field that also autosaves must not save every interim result; commit on a pause or on stop.
- Background noise and multiple voices produce garbage. Give the user an obvious way to discard the last dictated block without hunting for where it began.
Definition of done
9
Definition of done
9- Long text inputs across the app offer a dictation control.
- Transcribed text is inserted at the caret and existing content is preserved.
- Interim results are visually distinguished from committed text.
- Unsupported browsers show no control and a fully functional text field.
- Listening stops after sustained silence and on focus loss, navigation, or dialog close, with the microphone released.
- The recording state is indicated by more than colour and can always be stopped.
- A dictated block can be undone in a single step.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
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
Form Field Shell
Form Field Shell
Wrap every input in one structure so labels, help, and errors behave the same everywhere.
What it does
A single wrapper owning the label, description, error, and status region around any control in the app.
How it works
- 1 Inventory the app's existing fields and find the variations that have accumulated — label above versus beside, error under versus in a tooltip — then route all of them through one shell.
- 2 Generate a stable identifier per field and use it to link the control to its label, its description, and its error, so the association survives re-renders and does not collide when the same field appears twice on a page.
- 3 Support required, optional, read-only, and disabled as declared states of the shell, and let the shell pass them to the control rather than each screen setting them by hand.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/form-field-shell
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.