Dependent Select Fields
Load one select's options from another's choice without stale values slipping through.
What it adds
A parent select that constrains a child select's options, loaded on demand, with the request ordering and invalidation handled properly.
What your agent is told to do
5
What your agent is told to do
5-
1
Find the selects whose valid options depend on another field and load the child options from the server when the parent changes.
-
2
Track requests so only the newest response is applied. A user changing the parent three times quickly must not end up with the first response's options.
-
3
Clear the child selection whenever the new option set no longer contains it, and say so rather than silently blanking the field.
-
4
Give the child a real disabled, loading, empty, and error state, and re-validate the pair on the server — never trust that the submitted child belongs to the submitted parent.
-
5
Do NOT preload every combination into the page. It bloats the payload and goes stale; fetch on demand and cache per parent value.
Edge cases it handles
6
Edge cases it handles
6- Out-of-order responses must be discarded, not merged.
- An edit form whose saved child option is now inactive or absent must still display the saved value rather than showing an empty select.
- An empty option set needs its own message and a disabled control, not a select with one blank row.
- A failed load must offer a retry and must not leave the child enabled with nothing in it.
- Clearing the parent must clear and disable the child, not freeze the last options.
- Deep chains — country, region, city — must invalidate every level below the one that changed.
Definition of done
8
Definition of done
8- Changing the parent reloads the child options and discards superseded responses.
- A child value invalidated by the parent change is cleared and the user is told.
- Loading, empty, and error states exist and disable the control appropriately.
- Saved-but-inactive child values still render on edit forms.
- The server rejects a child value that does not belong to the submitted parent.
- Every level below a changed level in a chain is invalidated.
- 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.