One Shortcut Away From Every Action in Your App.

Functionally it contains a search bar, but the intent is opposite. A search bar finds content — products, articles, documents — and hands you a result to click. A command palette executes operations: it closes itself after running, and its entries are verbs (create task, toggle theme, invite user) rather than nouns (blue sneakers, pricing page). The modal shell is what makes the execution safe: focus is trapped, the background is inert, and Escape cancels cleanly. If the best action after typing is "click a link", you built site search; if it is "press Enter and something happens", you built a palette.

Add a keydown listener on window that checks for the K key with metaKey on Mac or ctrlKey elsewhere, call preventDefault to stop the browser find shortcut, and toggle the dialog open state. Register the listener inside a useEffect with a cleanup so it unbinds on unmount, and guard it to client-side code if you are on a server-rendered framework. MeDo generates all of this when the prompt says "open with Cmd+K on Mac and Ctrl+K on Windows" — spelling out both platforms is what prevents a palette that only works on laptops.

Start with the ten actions users repeat daily: create, search-inside, navigate to the four or five key places, toggle theme, and copy or share. Then add the operations that are currently buried three menus deep — those are the ones the palette rescues. Leave out anything a first-session user would not recognize by name, since the palette has no room for explanations, and keep destructive commands behind a confirm step. If your app has AI, the highest-leverage entries are natural-language actions, which is why AI tools made the palette their primary surface.

Instead of requiring a substring match, fuzzy matching scores whether the query characters appear in order in the command label or its hidden keywords — typing "usr" matches "Invite user". Good implementations also match against synonyms you register per command, so "theme" finds "Toggle dark mode", and highlight the matched substrings in the result rows. Ask MeDo for "fuzzy filtering with hidden keyword aliases per command" — without the aliases, users have to know your exact labels before the palette is useful.

Keyboard-first, not keyboard-only. Power users should never touch the mouse — arrow keys, Enter, Escape — but clicking a row, tapping on mobile, and an explicit visible trigger button all matter: discoverability depends on a visible "⌘K" affordance in the header, because users cannot want a shortcut they have never seen. On touch devices without a keyboard, surface the palette from the trigger tap with a numeric keyboard instead, and keep row targets at 40px or more for fingers.

Both, because they serve different memories. The sidebar stores the app structure visibly, which is how new users learn what exists; the palette is retrieval for people who already know, and it can never teach the topography of your app. Ship the sidebar as the primary navigation and the palette as the accelerator on top — see the MeDo sidebar page for the persistent-navigation side of this pairing. The failure mode is dropping the sidebar because "⌘K covers it": new-user activation collapses, and the palette only helps people who already stayed.