Address Autocomplete
Help people enter an address fast without trapping them in a bad suggestion.
What it adds
A suggestion-backed address field that fills structured components and always allows full manual entry.
What your agent is told to do
6
What your agent is told to do
6-
1
Always keep manual entry available and obvious. Suggestion providers miss new builds, rural addresses, and much of the world; a form that only accepts a suggestion is a form some users cannot complete.
-
2
Store the structured components — line one, line two, locality, region, postal code, country — alongside the provider's formatted string and its place identifier. Storing only the formatted string makes the data unqueryable later.
-
3
Do not send keystrokes to the provider on the first character. Wait for meaningful input and debounce. Every request costs money and sends a user's partial address to a third party.
-
4
Let the user edit any field after a suggestion is applied, and keep their edits — do not overwrite corrections with provider data.
-
5
Adapt the field layout to the selected country. Fixed 'State' and 'ZIP' labels are wrong for most of the world, and required-postcode rules vary.
-
6
Never block submission on the provider. If it is slow, down, or over quota, the form must still accept a typed address.
Edge cases it handles
6
Edge cases it handles
6- Apartment, unit, and suite numbers are frequently absent from suggestions — always provide a second line and preserve it.
- Selecting a suggestion by keyboard must work identically to clicking one.
- Addresses with no postal code, or postal codes with letters, must be accepted where valid.
- A user may change country after typing — reset provider bias and re-validate the fields rather than keeping stale ones.
- Provider terms often restrict storing or displaying their data; check before caching results.
- Announce the number of suggestions and the highlighted option to screen readers; a silent list is unusable.
Definition of done
9
Definition of done
9- An address can be completed entirely by hand with no suggestion selected.
- Structured components and the original formatted string are both stored.
- No provider request is made before meaningful, debounced input.
- Manual corrections after selecting a suggestion are preserved.
- Field labels and required rules change with the selected country.
- A provider outage does not prevent form submission.
- The suggestion list is fully keyboard operable and announced.
- 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
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
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.