Accessible Multi-Select
Let people pick many items and always know exactly what they have picked.
What it adds
A multi-select whose selection state is visible, removable, and announced — chips, counts, select-all, and a keyboard model that works.
What your agent is told to do
5
What your agent is told to do
5-
1
Render each selection as a removable chip with an accessible label naming the item, not a bare X.
-
2
Define one keyboard model and stick to it: arrows move through options, Space or Enter toggles, Backspace on an empty input removes the last chip, Escape closes the list without discarding selections.
-
3
Announce the selection count on every change through a polite live region, and announce removals by name.
-
4
If the app already has a typeahead or suggestion component, extend it rather than building a second one. This feature is about selection state, not about searching.
-
5
Do NOT let bulk removal happen without recourse. Select-all and clear-all must state how many items they affect and be undoable.
Edge cases it handles
7
Edge cases it handles
7- Selected items that fall outside the current search results must stay selected and stay visible.
- The same item must never be selectable twice, including via paste or programmatic set.
- Select-all must mean all matching the current filter, and must say so — not all options in existence.
- A large selection must collapse to a count with a way to expand, so the chip pile does not swallow the page.
- Removing a chip must move focus to a predictable neighbour, never to the body.
- Chips must wrap and remain tappable at 320px, with touch targets large enough to hit.
- A maximum selection limit must be announced before it is hit, not enforced by a silent no-op.
Definition of done
8
Definition of done
8- Every selection is visible as a labelled, removable chip.
- The whole control is operable by keyboard alone, with a documented key map.
- Selection count and individual removals are announced to screen readers.
- Selected items survive searching and filtering the option list.
- Duplicate selections are impossible.
- Select-all and clear-all state their scope and can be undone.
- 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.