What problem does it solve? Editing Karabiner-Elements keyboard remaps is error-prone because the live karabiner.json and karabiner.edn files are generated artifacts — hand edits get silently overwritten on the next build. This Skill guides safe modification of a Goku-based keyboard config by routing every change through the correct YAML source files or the add-keymap CLI, then through the proper build and deploy chain. ## Core Features & Use Cases - Add or change key bindings: Use the add-keymap CLI in one-liner mode to bind keys across app-launcher, workspace, shortcut (l1/l2/l3), and hyper layers with collision detection. - Discover existing bindings: Read the YAML configs (app.yaml, shortcuts.yaml, help-text.yaml, hyperkeys.yaml) as the source of truth, find free keys, and decode Goku modifier syntax. - Troubleshoot the build pipeline: Diagnose why a change did not take effect by following the build.sh → chezmoi apply → goku compile chain and verifying the compiled karabiner.json. - Use Case: You want Right Option + Z to launch Spotify. Run add-keymap with the app layer, key z, and action Spotify, then run the targeted chezmoi apply and goku recompile, and grep karabiner.json to confirm the binding is live. ## Quick Start Ask the assistant to add a Karabiner binding that opens Spotify when holding Right Option and pressing Z, then rebuild and verify the compiled config.
