Date Range Picker
Let users pick a valid date window without guessing which end comes first.
What it adds
A range picker with typed entry, clear boundary semantics, and no timezone drift between what was picked and what was stored.
What your agent is told to do
5
What your agent is told to do
5-
1
Support both calendar clicking and typed entry. Keyboard users should never be forced through a grid to enter two dates they already know.
-
2
Decide and document whether the range is inclusive or exclusive at each end, and make the summary text say it in words.
-
3
Handle reversed selection gracefully: picking the later date first should swap the endpoints, not reject the input.
-
4
Treat a calendar date as a calendar date. Store and compare it without a time component, or you will ship the off-by-one-day bug where a user in UTC-8 picks the 1st and the server records the 31st.
-
5
Do NOT reimplement locale formatting by hand. Use the platform's locale data for month names, date order, and first day of the week.
Edge cases it handles
6
Edge cases it handles
6- First day of week and date order differ by locale — read them from the locale, do not hardcode Sunday or MM/DD.
- Disabled dates inside a range must be enforced, not just greyed out.
- Minimum and maximum span limits must be explained when they block a selection.
- Open-ended ranges need explicit support and a clear label, not a blank endpoint.
- On mobile the calendar must fit without horizontal scroll and should not fight the native keyboard during typed entry.
- Presets like 'last 30 days' must state their boundary rule — whether today counts.
Definition of done
8
Definition of done
8- A range can be entered fully by keyboard and fully by pointer.
- Inclusive or exclusive boundaries are documented and reflected in the displayed summary.
- Selecting the end before the start produces a valid range.
- The stored range matches the dates the user saw, in every time zone.
- Locale determines date format and first day of week.
- Disabled dates and span limits are enforced with an explanation.
- 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.