What problem does it solve? Keyboard shortcuts that are configured but never fire are hard to debug because the failure can happen at registration time (binding never entered the registry, or was overwritten by another entry for the same command) or at runtime (a when-clause evaluated false, or a dispatch guard swallowed the key). This Skill provides a systematic diagnostic workflow for the Universe Editor codebase to pinpoint exactly which layer dropped the keypress. ## Core Features & Use Cases - Diagnostic log interpretation: Enable the keyboard troubleshooting channel and read the diag line fields (same-key, monaco bridged, parsed/registered counts) to classify the failure before changing any code. - Decision-tree triage: Distinguish four failure branches — key never reaching the document listener (Monaco or OS swallowing it), binding missing from the registry, when-clause evaluating false, and runtime guards (editable targets, Quick Input, dialogs, editor focus) blocking execution. - Fix discipline with reproduction tests: Write a minimal failing unit test in UserKeybindingsService.test.ts first, then fix, then guard the full chain with a Playwright e2e spec. - Use Case: A user binds ctrl+alt+up to editor.gotoPreviousFold in keybindings.json but nothing happens. The Skill walks through counting log lines, identifying that Monaco's built-in insertCursorAbove consumed the key, and applying the -command unbinding fix. ## Quick Start Ask the assistant to diagnose why a specific keyboard shortcut in keybindings.json does not trigger its command, mentioning the key combination and the target command id.
