Phone Number Input
Accept phone numbers in the format people know and store them consistently.
What it adds
A phone field with explicit country selection that stores a canonical number while displaying a readable one.
What your agent is told to do
6
What your agent is told to do
6-
1
Store the canonical international form (E.164) and display the national or international format the user recognises. One stored shape means matching, deduplication, and sending all work.
-
2
Make country selection explicit and changeable. Browser locale is not phone country — expatriates, travellers, and anyone with a foreign SIM will be assigned the wrong one.
-
3
Validate per country using real numbering rules, not a single length. Numbers range from about seven to fifteen digits and are not uniform inside one country.
-
4
Capture an extension as a separate field. Appending it to the number breaks dialling and every downstream integration.
-
5
Do not reject a number just because your library does not recognise its prefix. Numbering plans change; warn rather than block, unless the number is being used for delivery.
-
6
Caret movement, separator insertion, and paste normalization are owned by Input Masks; extend that rather than writing a second masking implementation.
Edge cases it handles
6
Edge cases it handles
6- A pasted number that already carries a country code must set the country selector, not be treated as a local number.
- Leading zeros in national format must be dropped correctly when converting to E.164 and restored on display.
- Some countries share a calling code (+1, +7); disambiguate by area code rather than guessing.
- Existing stored numbers may not be canonical — migrate them rather than assuming the format on read.
- The mobile keyboard must be a phone keypad, and must permit +, spaces, and dashes.
- A number valid for display may still be undeliverable for SMS; verification, not validation, decides that.
Definition of done
8
Definition of done
8- Numbers are stored in E.164 and displayed in a readable national or international format.
- Country selection is explicit, visible, and independent of locale.
- Valid numbers from at least a dozen countries of differing lengths are accepted.
- Extensions are stored separately from the number.
- Pasting an international number sets the country correctly.
- Unrecognised prefixes warn rather than block.
- 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.