Command Palette
Add a keyboard-accessible command interface for navigation and actions.
What it adds
A command palette turns your app's navigation and actions into a single searchable
overlay, opened from anywhere with a keyboard shortcut.
- Keyboard shortcut to open the palette from anywhere
- Fuzzy search across navigation destinations and actions
- Full keyboard navigation, with the mouse as an option rather than a requirement
- Recent items, so the thing you did last is one keystroke away
- Responsive behaviour that degrades to something usable on a phone
- Accessible focus management and screen reader support
What your agent is told to do
5
What your agent is told to do
5-
1
Find the app's routes and pages. Every primary destination the user can
-
2
Find the app's existing actions — "create X", "log out", "open settings" —
-
3
Register a global keyboard shortcut to open the palette. Do not hijack a
-
4
Search. Filter commands as the user types, matching label and keywords.
-
5
Group results by kind (Navigation, Actions) when there is more than one
Edge cases it handles
7
Edge cases it handles
7- The user is typing in a form. The shortcut must not fire while focus is in an
- The palette is already open. Pressing the shortcut again closes it.
- Another modal is open. Either block the palette or close the other modal
- An action the user lacks permission for. Hide it. Never show a command that
- The user is signed out. Show only the commands that make sense signed out.
- A very long command list. Cap or virtualize the rendered results; do not
- A recent item pointing at a deleted record. Drop it from the list rather than
Definition of done
11
Definition of done
11- The palette opens from anywhere via the keyboard shortcut.
- It does not open while the user is typing into a field.
- Every primary navigation destination is reachable from it.
- Actions call the app's existing handlers rather than reimplementing them.
- Search filters results as the user types.
- The list is fully keyboard-navigable and Enter activates the selection.
- Escape closes the palette and restores focus.
- Focus is trapped while it is open.
- It works on mobile, with a non-keyboard way to open it.
- It matches the app's existing design system — no new palette or UI library.
- No existing keyboard shortcut or functionality is broken.
Related features
Feedback Widget
Feedback Widget
Let anyone report a bug or send a comment from the page they are looking at.
What it does
An always-available launcher that opens a short feedback form and submits it with page context attached.
How it works
- 1 Put a single persistent launcher in one corner of the app and open a compact form in place. Do not route the user to a separate feedback page and lose the context they were about to describe.
- 2 Attach the current URL, the app version, the viewport size, the signed-in account, and a short trail of recent client errors automatically, so the reporter does not have to describe where they were.
- 3 Show the captured context to the user before they send it, in a collapsible section, and let them remove it. Silent collection of screen state is a trust problem.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/feedback-widget
Booking Page
Booking Page
A shareable page where someone picks an open time and confirms it in a few clicks.
What it does
A public scheduling page listing open slots, taking a booking, and confirming it to both sides.
How it works
- 1 Build the visitor path first: pick a date, see open times in their own zone, fill a short form, confirm, and receive an email with the details and a cancellation link. That is the minimum coherent version.
- 2 Derive open slots from the owner's availability rules and existing bookings on the server at request time. Do not trust a slot list the browser has been holding since page load.
- 3 Reuse the app's existing Time Zone-Aware Scheduling for conversion and storage, store every time as an absolute instant, and display it converted to the visitor's detected zone with the zone named on screen.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/booking-page
Date and Time Display Component
Date and Time Display Component
Render every date and time through one component so none of them are ambiguous.
What it does
A single shared way of displaying dates and times, covering absolute format, time zone, and optional relative phrasing.
How it works
- 1 Find every place the app renders a date or a time — tables, activity feeds, audit logs, exports, emails, tooltips — and route them all through one display path rather than formatting at each call site.
- 2 Never render an all-numeric date whose day and month could be swapped. Spell or abbreviate the month, or use an unambiguous ordering consistently, because a reader has no way to tell 04/07 from 07/04.
- 3 State the time zone whenever the value is a specific moment rather than a calendar day, and be explicit about whose zone it is — the viewer's, the record's, or the account's — rather than leaving it implied.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/date-and-time-display-component
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.