Keep macropad shortcuts consistent across project workspaces

KM16 Macropad can become confusing when a key opens search in one project and launches a task in another. Some differences come from editor workspace settings; others come from your own saved profile. Keep a small stable vocabulary for shared navigation, then make project-dependent actions visibly separate. Consistency is most valuable where a mistaken press would otherwise surprise you.

Which actions can remain the same everywhere?

Start with destinations that exist across your projects, such as the file picker, editor search, terminal view and source-control panel. Bind the editor's named commands where practical. Check them in representative workspaces rather than assuming an extension or command is installed everywhere you work.

Use labels that describe the destination instead of the current project. A key named Build may hide different scripts with different consequences. A key named Focus terminal is more consistent, although the terminal it reveals still deserves checking before you type. Hardware labels should not imply more context awareness than your setup provides.

What belongs in a project-specific layer?

A repository task, a saved query or a particular folder path belongs in a clearly named project profile. Record what must exist for it to work. Avoid embedding credentials, private tokens or environment-specific command arguments in a profile you might later share with someone else.

Prefer opening a task chooser over immediately executing a stored command while you are still learning the workspace. That gives you a visible check of the selected project. If the application supports a direct command binding, inspect its behaviour rather than replacing it with a timed sequence of text entry.

How can you find workspace overrides?

Review the application's shortcut and configuration interface for rules that differ between profiles or contexts. In VS Code, consult the documented keyboard rule evaluation when the same input invokes different commands. The emitted key can be identical while the selected command changes with focus or conditions.

Test the physical key after switching projects, then compare the command shown by the app's diagnostic tools. This separates a changed hardware layer from a changed editor rule. Fix the responsible layer rather than creating another translation that masks the difference.

What should a portable shortcut record include?

Keep a shared section for navigation and a separate section listing project-specific actions with their prerequisites. Include a simple way to return to the shared profile. Before moving to another machine, export supported settings and note any background utility required. The KM16's configurable controls are useful when their meaning stays visible across the workspaces where you rely on them.