A practical look at live Windows menu reading, bundled shortcut packs, and search when you remember the action but not the keys.
You remember the action: rename the symbol, export the document, open the command palette. What you do not remember is the exact key combination, or whether the application uses the same one as the tool you opened yesterday.
The useful question is not “How large is the shortcut database?” It is “Where did this answer come from, and how quickly can I recognize the right one?” FluentOverlay uses two source paths, then applies one search experience across both.
FluentOverlay opens above the active Windows application. That context determines which shortcut set belongs in the overlay. The default trigger is a double-tap of Ctrl, although Pro can configure other standard and pinned trigger profiles.
Keeping the current application as the starting point removes an entire decision from the search. You are not choosing a product, version, or platform from a web index before you can type the action.
Some Windows applications expose their standard menus through Windows UI Automation. FluentOverlay reads those menu names and accelerator keys in real time for supported Win32, WPF, WinForms, and UWP menu structures.
This is the strongest source path when it is available because the application is exposing the menu currently in use. FluentOverlay can group the discovered actions under familiar categories such as File, Edit, View, Tools, and Help rather than flattening them into an unrelated list.
There is an important limit: UI Automation can only return what an application makes available through that interface. A custom-drawn menu or an application without a classic menu needs another source.
For applications without standard menus, FluentOverlay ships bundled JSON shortcut packs. They provide curated shortcut references for a broad range of creative tools, IDEs, browsers, CAD software, file utilities, and other applications.
Packs are not presented as live menu data. They are curated references that let the overlay preserve the same interaction model when UI Automation is not the right source. FluentOverlay can also load custom packs validated against its pack schema. Pro users can create, edit, import, and export those packs with the visual Pack Editor.
That division is healthier than pretending one discovery technique works everywhere: read the application when it exposes usable menu data; use a curated pack when it does not.
Once the relevant shortcuts are in the overlay, source mechanics should fade into the background. Search uses substring and fuzzy matching, so a partial memory such as sv can still find “Save.” A built-in synonym dictionary also maps intent words to related command labels; “delete,” for example, can find actions labelled “remove,” “clear,” or “discard.”
You can hold Ctrl, Alt, Shift, or Win to highlight shortcuts using that modifier. This is useful when the keys are easier to remember than the command name.
The result is a recognition workflow rather than a recall test:
A live menu is bounded by what the application exposes. A bundled pack is bounded by what has been curated. Neither boundary disappears through confident wording.
Custom packs are the practical extension point when an application is missing, and Pro custom personal shortcuts can override or augment an application's standard shortcut set. The Shortcut packs guide explains how packs are loaded, while Creating custom packs covers authoring.
Free is enough for the central job: open the overlay, search, and discover shortcuts without an account requirement. Pro adds click-to-execute, favourites, custom personal shortcuts, and the Pack Editor for people who want to shape the reference around their own work.
The same product also carries reusable prompts, snippets, commands, workflows, and knowledge cards in Pro. That is the subject of From shortcut recall to a local working playbook.
For the product and tier overview, visit the FluentOverlay product page. To report a missing application or question a shortcut reference, use the contact form.
