hotkey

Define the shortcut ID in a hotkey enum, register its default key combination in a central registration config, add i18n title and description strings, then create a hook that binds the hotkey to its action and register it in the appropriate scope.

Assign each hotkey a scope such as global or chat in the registration entry, then create a scope-specific hook file that calls a useHotkeyById-style hook for each shortcut and aggregates them in a single registration hook.

Use a platform-agnostic modifier like Key.Mod instead of hardcoding Ctrl or Cmd. This maps to Cmd on macOS and Ctrl on Windows and Linux automatically, preventing platform-specific shortcut bugs.

Common causes include a missing or incorrect scope assignment, the registration hook not being mounted, or the hotkey missing from the central registration config. Verify the scope activation and that the shortcut appears in the settings registration.

Read the user's configured hotkey for the action from the settings store selector, then pass it to the tooltip component's hotkey prop alongside the translated title from the hotkey locale namespace.