Command palette: a shortcut for regular users, not a secret entrance to features
Design commands, context and shortcuts so a fast route stays discoverable and makes its effect clear.
Article language: English

In this article
"Create a copy", "Go to orders", "Send to customer". Three similar-looking rows may create an object, change the screen or send a message outside the company. A command palette brings them together, but it should not blur the difference between their effects.
It is a window where someone types the name of an action and selects it from a list. It can help people who regularly work in a complex tool. It is harder to justify as the only route to an operation a new employee has yet to learn. If a feature can be found only by typing its unknown name, the application has created a small quiz about itself.
What are we actually shortening?
A fictional costume workshop uses a panel to manage orders. Every morning Lena opens those waiting for a fitting, and during the day she often adds a note to a particular costume. Her manager would like to give her a command palette. Before producing an impressive window, establish whether the part that needs shortening is moving between views or acting on an open order.
A list of every operation is not yet a design. Beside each name, record when it is available and what it does. "Open orders for fitting" leads to a list. "Add note" opens a field for the current costume. "Send summary" requires a recipient and content to be established. A shared search field can find all three, but each result should say what happens when selected.
Visual Studio Code's accessibility documentation describes filtering a command list by typing a name and an editor for discovering and changing shortcuts. This is a real example of separating an action's name from its key combination. It does not mean an order panel should copy the entire interaction model of a code editor.
For the first version of the palette, select repeated actions whose names the audience understands. Follow Lena through several real tasks rather than assuming every feature deserves a shortcut. An action performed once when setting up an account can remain in settings. A frequently opened view can gain a quick entry without a separate shortcut for each variation.
Do not mix document results and commands without a clear division. "Fitting" might refer to an order with that title, a saved filter or an action to arrange an appointment. In a content search (in Polish), the reader is primarily looking for material. In a palette, they may be about to execute an operation. A category label and a short description of the effect help prevent an accidental choice.
A no-results state should retain the typed word and show a route to ordinary navigation or help. If Lena types "trying on" but the team calls it "fitting", that is a useful candidate synonym to test. If the feature does not exist, the palette should not return a similar but different action merely to avoid an empty result. If the search mechanism is unavailable, the message must describe the failure rather than claim the command does not exist. In that state, buttons on the relevant screen remain an important route for continuing work.
In an Aeneia Design interaction and screen project, such an action inventory becomes the basis for component states. Bring several real workflows and the words the team uses. A screenshot of an attractive palette from another app will not show which object a command should affect or who may execute it.
One name, the same object
Lena is working on order K-24. She types "copy" and sees "Create a copy of order K-24". That is a fuller promise than "Copy" alone, which might mean copying an address, text or an entire object. After the operation, the message should distinguish creation of a separate order copy from putting something on the clipboard.
The name visible in the palette should match the ordinary interface. If a page button says "Add note", the palette does not need to call the same action "Create record annotation". Synonyms can help people find a result, but should not multiply visible names for the same action. Localisation adds word inflection, interface language and terms used within the company.
An icon is supplementary. Principles for choosing symbols and labels (in Polish) help distinguish opening a screen from sending or deleting. Two rows with similar arrows still need text. Someone selecting a command by keyboard should receive a comprehensible name, not a description of the icon's shape.
Context also includes the company or workspace. If Lena serves two workshops, the palette must make clear whether a command concerns the current organisation or searches all of them. Switching companies in an interface (in Polish) needs the same consistency. A result found earlier must not, after an organisation change, act on an arbitrary order with a similar number.
The object and scope can appear beside the result or in the palette heading. The information should be visible at the moment of selection. Do not make the user close the window just to remember which order they were working on. Treat commands available from anywhere in the application particularly carefully: there is not always one obvious current object.
Suppose the window opened on K-24, but the selection in the list changed behind it. The design must say whether the palette holds the context from opening or updates it with the screen. In the first case it continues to show K-24. In the second it should communicate the change clearly and not leave the old description beside a new target. The reader must not discover the rule only after creating a copy. This is a useful prototype case with two similarly named orders.
An unavailable action also needs a meaning. "Send summary" might require saved changes, an address or a different role. The design decides whether the result disappears or remains visible with an explanation. Hiding every unavailable feature makes discovery harder; a list full of inactive commands makes work harder. The right choice depends on the situation, not a general fashion for a cleaner screen.
Do not expose private names and details merely to explain a lack of access. The results list is itself part of the application and needs the right data scope. Actual permissions belong to the system's behaviour; the design should clearly specify what the user sees after a refusal.

A shortcut should not intercept typing
The palette needs a visible entry, such as a labelled button in the toolbar. The current key combination can appear beside it. A new person can discover the feature, while an experienced user gradually learns a faster route. On a phone, convenient touch operation is still needed even when the product was designed for daily desktop work.
Choose a shortcut with the browser, operating system and keyboard layout in mind. The fact that it works on the designer's computer says little about other workstations. Include typing, an open form and assistive technology in the test. Do not intercept a combination the user relies on for another basic action without explanation.
If users can change shortcuts, also define where the setting is stored and how to restore it. A setting for one computer differs from an account setting used across devices. After a combination changes, the button description and help must show the same value. If it conflicts with another command, show both names and let the user decide the assignment. Do not make a new colleague guess why another person's instructions work on one workstation but open a different window on another.
The explanation of WCAG criterion 2.1.4 sets special conditions for character-only shortcuts: they can be turned off, remapped or active only when the relevant component has focus. Focus indicates the element currently operated by keyboard. The rule also concerns character sequences; it is not merely a count of physical key presses.
In our workshop, the letter N should not open a note while Lena is typing a customer's surname in another field. This is a case for our own test, not a claim about a ready-made product. Record where shortcuts work and where they remain disabled. Removing a conflict with one field does not settle the entire application.
After opening the palette, a user types a query and moves through results. The visible selection should be distinct from execution. Reordering during typing must not place a different command under confirmation at the decisive moment. When results are fetched remotely, an older response should not replace a newer list.
PowerToys Command Palette settings distinguish, among other things, Escape behaviour, retaining a query after reopening, and selecting versus running an item. These are decisions by a particular product, not a single mandatory recipe. State them explicitly for your own palette rather than leaving them to a library's accidental behaviour.
Escape may first clear the query or close the window immediately. Both rules can be explained and tested. The problem begins when the same gesture sometimes clears the field and sometimes goes back for no clear reason. After closing, the reader should recover a logical place on the screen from which the palette was opened. A similar completion of the journey appears in the mobile menu design (in Polish).
Aeneia Design
Gather your team's repeated actions and the screens from which they are launched. Let us design command names, execution context and palette behaviour during typing, refusal and return.
Discuss a command palette and shortcuts for your panel
A quick route still ends in a result
When Lena chooses "Send summary", she should see what will be sent and to whom. The palette can open the right form rather than perform the operation immediately. A short route to preparing a message does not have to bypass the sending decision. The result's name should reflect that distinction: "Prepare summary" promises something different from "Send now".
If Lena already has a draft note open, invoking a new form needs a rule for preserving that text. Opening a command should not erase an unsaved paragraph. The new action can be deferred until the current form closes, or an explicit decision about further work can be offered; the choice depends on the save model that actually works in the panel.
For a local operation, such as applying a saved table layout, the result may be immediately visible. The guide to saved table views (in Polish) discusses saved views. It is still worth deciding what happens on error and whether the palette stays open. Do not communicate success solely by making the window disappear. It could also have disappeared after cancellation or a lost connection.
Recent command history should preserve the correct meaning. If Lena copied K-24 yesterday, today's result should explain whether it repeats the operation on the old object or on the one currently open. When pinning a shortcut, distinguish a fixed action from a link to a particular case. A short description saves a longer investigation later.
For acceptance, give a new person a task without revealing the feature's name. Ask them to find the ordinary route to a note and then discover the palette. Ask an experienced panel user to do the same in another workspace and with a text field open. Compare task completion and contextual mistakes, not only the number of key presses.
A palette earns its place when it shortens familiar work without hiding its meaning. Lena should end up on the correct note in K-24, not admiring the speed of command search. That is a sufficiently concrete ambition for a small window.







