Search everywhere
The double-shift launcher is a signature JetBrains shortcut.
With MacKeys
Without MacKeys
Programming shortcut guide
JetBrains IDEs are especially keyboard-rich, with menus, keymaps, and navigation built for serious coding sessions. MacKeys is useful here because even one or two recurring shortcuts can save a lot of translation overhead in long programming sessions.
With MacKeys
The goal is not to make Figma different. It is to remove the modifier translation layer so common actions still feel like the Mac workflow your hands already know.
Without MacKeys
Native Windows shortcuts usually ask for `Ctrl` and `Alt` translations. In dense design sessions, that adds up as hesitation, extra reach, and slower recovery when you are moving quickly.
Shortcut rows
9
Workflow actions covered on this page.
Translated shortcuts
9
Rows where MacKeys removes the Windows modifier translation.
High-gain actions
6
7 of these are high-frequency shortcuts.
Workflow sections
Jump to the part of Figma where shortcut translation matters most.
Editing
High-value editor actions.
A quick structural edit used constantly in practice.
With MacKeys
Without MacKeys
Used in debugging, experiments, and review.
With MacKeys
Without MacKeys
Refactor
Code transformation shortcuts.
One of the most valuable refactor actions in the IDE.
With MacKeys
Without MacKeys
A signature IDE action where shortcut familiarity pays off.
With MacKeys
Without MacKeys
Tools
Terminal, run, and tool-window shortcuts.
Useful for keeping coding and shell work close together.
With MacKeys
Without MacKeys
A strong example of a local action where modifier feel matters.
With MacKeys
Without MacKeys
Reading the gain labels
A shortcut gets a higher estimated gain when it combines three things: frequent use, more awkward native Windows modifiers, and a higher likelihood of breaking Mac muscle memory in the middle of focused work.
Why this matters in JetBrains IDEs
JetBrains IDEs rewards fast repetition. Duplicate, group, frame, zoom, and property-copy actions are not isolated commands. They are part of the rhythm. The closer that rhythm stays to Mac muscle memory, the less time gets lost to tiny modifier decisions.
FAQ
Because the keymap patterns are shared across the family, so a single directory entry is practical for v1.