Glorious 60 Keyboard Shortcuts: Master Your 60% Setup
A comprehensive guide to glorious 60 keyboard shortcuts for 60% keyboards. Learn Windows/macOS mappings, layering, and practical examples to boost productivity and reduce finger travel.
Glorious 60 keyboard shortcuts are a curated set of key bindings designed for 60% keyboards, focusing on efficiency and layer-based access. They help you perform common tasks quickly by combining a modifier with the reduced keyset. In practice, you map frequently used commands across Windows and macOS, then adopt a consistent naming scheme.
Why the glorious 60 keyboard shortcuts matter
60% keyboards trade a full row of dedicated keys for a compact form, but that doesn't mean you sacrifice efficiency. The glorious 60 keyboard shortcuts concept prioritizes rapid access to high-frequency actions by using layers and thoughtfully assigned modifiers. In practice, you can design a mapping that aligns with your workflow and reduces finger travel on a daily basis.
{
"shortcuts": [
{"name":"Copy","keys":"Ctrl+C"},
{"name":"Paste","keys":"Ctrl+V"},
{"name":"Open command palette","keys":"Ctrl+Shift+P"}
]
}- Explanation: The JSON above defines a basic mapping you can extend. Start with the fastest actions and keep key names consistent across operating systems.
- Variations: On macOS, use Cmd instead of Ctrl; you can also swap in your preferred modifiers for layers.
Windows baseline shortcuts for day-to-day work
A practical approach is to establish a Windows baseline that covers copying, pasting, undoing, and searching. On a Glorious 60 keyboard this often means mapping common actions to your base layer and keeping navigation shortcuts on a secondary layer. The goal is to reach muscle memory quickly.
# Baseline Windows shortcuts
$windowsShortcuts = @(
@{ Name="Copy"; Keys="Ctrl+C" },
@{ Name="Paste"; Keys="Ctrl+V" },
@{ Name="Undo"; Keys="Ctrl+Z" },
@{ Name="Find"; Keys="Ctrl+F" }
)
$windowsShortcuts | ConvertTo-Json -Depth 3- Notes: PowerShell script demonstrates building a structured shortcut list. Adjust names and keys to fit your own workflow.
Mac shortcuts and cross-platform parity
Apple users rely on Cmd instead of Ctrl for many shortcuts. When mapping a Glorious 60, aim for parity across platforms by keeping action names identical and replacing the modifier. The goal is to minimize brain switches while keeping your most-used actions accessible.
# macOS shortcut equivalents (guiding template)
declare -A macShortcuts
macShortcuts=( [Copy]="Cmd+C" [Paste]="Cmd+V" [Find]="Cmd+F" )
printf "%s\n" "${macShortcuts[@]}"- Guidance: Use a small, documented set of actions and adapt via layers; ensure you update any editor-specific shortcuts accordingly.
Layered shortcuts: accessing extra keys with Fn
60% keyboards often rely on a base layer for the most-used actions and a function layer (Fn) to reveal additional keys. Conceptually, you map a second set of actions that are unreachable from the base layer without Fn. This approach preserves the tactile simplicity of the 60% layout while expanding capability.
{
"layers": {
"base": { "A": "paste", "S": "save" },
"fn": { "A": "select-all", "S": "save-as" }
}
}- Implementation tips: Start with a small base layer before adding a separate Fn layer to avoid conflicts. Use clear naming when switching between layers to maintain consistency.
Practical workflow mapping: daily tasks
To illustrate, map a typical daily workflow to a compact set of shortcuts. Build a short list first for high-frequency actions, then extend via a Fn layer for less-used tasks. A small, documented map tends to outperform a long, confusing one.
# Simple daily-workflow shortcut map
workflow = [
{"task": "Copy line", "keys": "Ctrl+C"},
{"task": "Open search", "keys": "Ctrl+F"},
{"task": "Open command palette", "keys": "Ctrl+Shift+P"}
]
for item in workflow:
print(f"{item['task']}: {item['keys']}")- Practical takeaway: Keep a changelog of updates; review monthly to retire unused mappings and add new ones.
Testing and refining your shortcut map
Testing is essential to ensure mappings behave as expected. Use a small test script or a mock environment to verify each action triggers the intended command, especially on user-specific software (editors, terminals, browsers). Iterate quickly by adjusting as you notice friction points.
#!/usr/bin/env bash
echo "Starting shortcut tests..."
python3 test_shortcuts.py
if [ $? -ne 0 ]; then
echo "Tests failed; review mappings."
exit 1
fi
echo "All shortcut tests passed."- Best practice: Run tests with a non-critical dataset first to avoid accidental data loss.
Exporting and sharing your shortcut map
Once you settle on a stable map, export it in a portable format and share it with teammates. A simple JSON export can be loaded by configurator tools, while a human-readable README improves onboarding for new users.
{
"exportFormat": "json",
"includeHeaders": true,
"shortcuts": [
{"name": "Copy","keys": "Ctrl+C"},
{"name": "Paste","keys": "Ctrl+V"}
]
}- Variation: Consider generating per-application profiles to tailor shortcuts to specific software.
Summary: adopting glorious 60 shortcuts in practice
In practice, start small by selecting 5–10 high-frequency actions and building a reliable base layer. Add a Fn layer gradually, documenting every change. Regularly revisit mappings to ensure they still align with your workflows and editor/tool changes. The goal is consistency across devices and ease of recall.
Steps
Estimated time: 45-60 minutes
- 1
Define your goals
Identify 5–10 core tasks you perform most often and map them to quick-access shortcuts. Keep naming consistent across platforms to minimize cognitive load.
Tip: Start with the tasks you reach for daily—copy, paste, search, and navigation. - 2
Audit existing shortcuts
Review existing mappings in your editor and OS utilities. Note conflicts and identify actions that would benefit from layer-based access.
Tip: Record conflicts to resolve before expanding layers. - 3
Create a base layer
Assign high-frequency actions to the base layer. Favor one-to-one mappings and avoid multi-step chains.
Tip: Limit the base layer to 8–12 primary actions. - 4
Add a Fn layer
Introduce a function (Fn) layer to expose additional actions without cluttering the base layer.
Tip: Label keys clearly to prevent misfires. - 5
Test and iterate
Test mappings across your favorite apps. Iterate quickly based on friction and feedback.
Tip: Keep a changelog of iterations and rationale.
Prerequisites
Required
- Windows 10/11 or macOS 10.15+Required
- Glorious 60 keyboard or any 60% keyboardRequired
- USB-C or wired USB connectionRequired
- Keyboard configurator software or firmware toolRequired
- Basic command line knowledgeRequired
Optional
- Understanding of keyboard layers (Fn keys)Optional
Keyboard Shortcuts
| Action | Shortcut |
|---|---|
| CopyGeneral use | Ctrl+C |
| PasteGeneral use | Ctrl+V |
| CutGeneral use | Ctrl+X |
| FindDocument/search | Ctrl+F |
| UndoGeneral edits | Ctrl+Z |
| RedoEdits | Ctrl+Y |
| New TabBrowsers/editors | Ctrl+T |
| Open Command PaletteCode editors | Ctrl+⇧+P |
Questions & Answers
What is a glorious 60 keyboard shortcuts?
Glorious 60 keyboard shortcuts are a curated set of hotkeys designed for 60% keyboards. They rely on layers and modifier keys to access a wide range of actions without a full-size keyset. This approach accelerates common tasks while preserving the compact form.
Glorious 60 keyboard shortcuts are a compact set of hotkeys for 60% keyboards that use layers to access more actions. They help you work faster with fewer keys.
Do I need to install extra software?
Some keyboards come with configurator software or firmware tools to map keys. You can start with a hardware-agnostic approach and then adopt a configurator if you want deeper customization. Always ensure compatibility with your OS and editor.
You may use a configurator for deeper customization if your keyboard supports it, but you can start with basic mappings right away.
Are these shortcuts OS-specific?
Baseline shortcuts align across Windows and macOS, but modifiers differ (Ctrl vs Cmd). Aim for parity by naming actions consistently and switching modifiers per OS when needed.
Most shortcuts share the same actions, but Windows and macOS use different modifiers like Ctrl and Cmd.
How do I reset to default mappings?
Most keyboards provide a reset option in firmware or configurator software. Use the reset to restore a clean slate before testing new mappings.
You can usually reset mappings via firmware or software, then reapply your preferred layout.
Can I share and reuse mappings across devices?
Yes. Export your mapping as JSON or a profile file and import on other devices. Keep version control for consistency and easy rollback.
You can export your mapping and load it on other devices to reuse setups.
Main Points
- Map core actions to your base layer
- Leverage a Fn layer for additional keys
- Document mappings and review regularly
- Test across apps to ensure consistency