What your result means
Two figures, and the second is the honest one. Accuracy counts every prompt you eventually got right; first try, no hint counts only the ones you produced from memory at the first attempt. The gap between them is the set you think you know. The third figure lists what the trainer has weighted to come back — those are the shortcuts your fingers have not learned yet, regardless of what you can recognise on a printed cheat sheet.
Why this one is different
You physically press the shortcut and the page checks the real keypress, using key codes rather than characters so Ctrl+Shift+= and Ctrl+Shift++ are told apart. Missed shortcuts are weighted to recur three times as often, and combinations a browser cannot capture are listed rather than silently marked wrong.
How it works
The page listens for real key events and builds a signature from the modifiers and the physical key, so Ctrl+Shift+P has to be pressed, not typed as text. Each shortcut carries a weight, starting at 1. A miss — wrong keys, or asking to see the answer — triples that weight, so it is roughly three times as likely to be drawn next time; a clean hit decays the weight back towards 1. Weights persist in this browser, so the drill you take tomorrow is shaped by the ones you fluffed today. Nothing is uploaded.
How to use this trainer
- Pick a set. Each one is the default keymap for that application on Windows.
- Press start, then press the shortcut for the action shown. Keep focus on this page.
- Wrong guesses do not advance you — try again, or show the answer and take the miss.
- Finish the round and read the review list: green is first-try, red is weighted to return.
- Come back. The weighting only pays off across sessions.
Which keys a web page cannot see
Reserved by the browser: Ctrl+W, Ctrl+T, Ctrl+N, Ctrl+Shift+W
Everything else: cancellable, so the drill can mark it
This is a platform limit, not a design choice. Those shortcuts never reach the page's keydown handler, so a browser-based drill cannot know whether you pressed them — which is why they sit in the reference list above with the reason stated, rather than being quietly dropped or, worse, marked wrong.
Example calculation
First try, no hint = 9 ÷ 12 × 100 = 75%
Weight on a missed shortcut: 1 × 3 = 3
Frequently asked questions
Why are Alt+Tab and the Windows-key shortcuts missing from the drill?
Because the browser never sees them. The operating system intercepts Alt+Tab, Alt+F4 and every Win-key combination before a web page gets a keydown event, and a few browser-level keys (Ctrl+W, Ctrl+T, Ctrl+N) cannot be cancelled either. Drilling something the page cannot mark would be dishonest, so those live in the reference list below instead.
How does the weighting work?
Every shortcut starts at weight 1. Miss one and its weight triples, so it comes back roughly three times as often until you get it right, at which point the weight decays back towards 1. The weights are stored in this browser, so a shortcut you keep fluffing keeps returning tomorrow.
Does this work on a phone or tablet?
Not as a drill — there are no modifier keys to press. On a touch device the page shows the full reference list for each set instead, which is the useful thing a phone can do. Come back on a desktop keyboard for the drill.
Related tools
Assumptions & limitations
- Windows keymaps only. On macOS most of these are Cmd rather than Ctrl, so the drill would mark correct macOS muscle memory as wrong. A Mac set is a separate job, not a find-and-replace.
- Default keybindings. If you have remapped VS Code, or use a non-UK keyboard layout, some prompts will not match what your machine does.
- Dated lists. The shortcut tables are hardcoded and versioned in the page source (see the dataset comment). Applications change defaults; check the vendor documentation below before trusting an unfamiliar one.
- Some shortcuts cannot be tested in a browser — listed above, with the reason.
- Weights are local. Clearing site data resets what the trainer knows about your weak spots.