Search Suggestions
Finish the user's thought as they type.
What it adds
Typeahead suggestions that appear as the user types, with keyboard navigation.
What your agent is told to do
4
What your agent is told to do
4-
1
Suggest real records and real queries — not a generic autocomplete of dictionary words.
-
2
Debounce requests and cancel superseded ones.
-
3
Make the list fully keyboard navigable: arrows to move, Enter to select, Escape to dismiss.
-
4
Highlight the matched substring so the user can see why something matched.
Edge cases it handles
5
Edge cases it handles
5- Suggestions must respect permissions — never suggest a record the user can't open.
- A slow response must not overwrite a newer one.
- Selecting with the keyboard and clicking must do exactly the same thing.
- The dropdown must not be clipped by an overflow:hidden ancestor.
- No suggestions is a valid state — don't show an empty box.
Definition of done
7
Definition of done
7- Suggestions appear quickly and are debounced.
- Arrow keys, Enter, and Escape all work.
- Stale responses never overwrite newer ones.
- Suggestions never leak records the user cannot access.
- The combobox is marked up with correct ARIA roles.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Global Search
Global Search
One search box that finds anything in your app.
What it does
Search across every meaningful entity in the application from a single input.
How it works
- 1 Identify every entity worth searching, and report them before building.
- 2 Use the database's own search capability first (for example Postgres full-text search). Do not add Elasticsearch or a search SaaS unless the project already has one.
- 3 Return results grouped by entity type, strongest match first.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/global-search
Voice Search
Voice Search
Let people speak a search query instead of typing it, and still edit what was heard.
What it does
A microphone control on the app's existing search field that turns speech into a query the user can correct before it runs.
How it works
- 1 Add the microphone to the search input the app already has. Do not build a separate voice search screen or a second results page; the spoken query must go through the same search, the same filters, and the same ranking as a typed one.
- 2 Show words as they are recognised, in the search field itself, so the user can see the microphone is working before the final result arrives.
- 3 Leave the recognised text in the field as ordinary editable text once recognition finishes. The single most common repair is the user fixing one wrong word and pressing enter.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/voice-search
Saved Filters
Saved Filters
Let people keep the views they build.
What it does
Save a filter combination as a named view the user can return to.
How it works
- 1 Let a user name and save the current filter state, and list their saved views.
- 2 Store the filter definition, not the matching row IDs — a saved view must stay live as data changes.
- 3 Allow editing, renaming, and deleting saved views.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/saved-filters
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.