Command Palette

Keyboard-first navigation and action launcher with contextual commands, recent actions, and shortcuts. The screen connects Commands and Recent so product teams can find the “Customize” action while checking commands and recent.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Create new project and Go to billing settings, rather than an empty visual shell.

Use this template in Figr

Template facts

Screen

Primary action

Customize

Pattern

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps users do

Product teams need a clear “Customize” action without losing sight of commands, recent and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

Primary action: Customize is clearly available where the task happens.
Main view: Commands keeps the starting point obvious.
Connected view: Recent supplies nearby context.
Metric: Commands is visible with a meaningful value.
Another signal: Recent helps people judge what to do next.
Representative record: Create new project makes the example specific.
Second record: Go to billing settings shows the pattern works beyond one item.

States worth designing

No matching records; show what people can do instead of leaving a blank panel.
Loading commands without changing the layout unexpectedly.
Search or filter request failed; explain the problem and preserve work.
Permission denied for recent; clarify who can continue.
Success after choosing Customize; confirm the result and the next step.
Network or data refresh failure; offer a retry without losing context.

Where this screen sits in the flow

Commands → Recent → Customize → Review outcome

Patterns used

Search, Commands, Recent, Navigation, accessible states, contextual actions

Why these choices work

Preserve the query and chosen filters as people inspect results. Make no-results recovery useful instead of a dead end.

In this design, people should be able to compare Create new project with Go to billing settings. Make commands clear, then use recent to explain whether the next step needs attention.

Before handing this to a designer or engineer, check keyboard focus, error copy, permissions and what happens after they choose the “Customize” action. The happy path alone is not enough.

Related UI examples: Saved Searches, Browse Categories, Advanced Search Filters.

Start from this in Figr

Design a command palette screen for our existing software product. Use our real design-system tokens, components and product language. Show Commands and Recent, include believable records such as Create new project, and make customize easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr