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
Unit Converter
Unit Converter
Let people convert a value between units without leaving the page they are on.
What it does
An inline converter that takes a typed value in one unit and shows the equivalent in another, in place.
How it works
- 1 Start from the units the app actually deals in. A shipping tool needs weight and length; a recipe tool needs volume and temperature. Ship those and leave the rest out.
- 2 Convert as the user types, with the result visible beside the input rather than behind a submit button. Let either side be edited so the conversion runs in both directions.
- 3 Reuse the app's existing number parsing and display formatting rather than writing new ones. If Locale-Aware Numbers and Dates or Number Formatting Component is already present, the converter must render through it so grouping and decimal marks match the rest of the app.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/unit-converter
Field State Matrix
Field State Matrix
Decide once how every field looks and behaves in every state, before screens improvise.
What it does
A defined and documented set of visual and behavioural states covering every input type in the app.
How it works
- 1 Enumerate the app's input types and cross them against every state they can enter: empty, filled, focused, hovered, invalid, valid, disabled, read-only, loading, and browser-autofilled.
- 2 Define disabled and read-only as genuinely different states — a read-only field shows a real value the user may select and copy, a disabled field is inert and excluded from submission.
- 3 Define the loading state so the field is visibly busy and not editable, and say what happens to a keystroke that arrives mid-load rather than letting it be silently swallowed.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/field-state-matrix
Required Field Indicator
Required Field Indicator
Make it obvious which fields must be filled in and which may be left alone.
What it does
A consistent marking of required and optional fields across every form in the app.
How it works
- 1 Count the required and optional fields across the app's forms and pick the convention that marks the minority — if most fields are required, mark the optional ones instead.
- 2 Apply the chosen convention to every form without exception, and state the convention once at the top of each form so the marker means something to a first-time reader.
- 3 Expose the requirement to assistive technology as well as visually, so the control itself reports that it is required rather than relying on a symbol beside the label.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/required-field-indicator
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.