keyboard-interface

Installation
SKILL.md

Keyboard Interface

Keyboard support is not “make every interactive-looking thing tabbable”.

Use this Skill when an interface contains custom controls, composite widgets, overlays, dense action surfaces, or keyboard commands whose interaction model must remain predictable without a pointer.

Follow Inspect → Extract → Translate → Implement → Verify. Prefer native HTML behavior and established platform / ARIA interaction conventions before inventing new key bindings.

When to use

Use for:

  • custom tabs, menus, radio groups, toolbars, listboxes, trees, grids, comboboxes, or similar composite widgets
  • dialogs, popovers, menus, command surfaces, and other overlays that move or contain focus
  • dense interfaces where naive tabbing would produce excessive or ambiguous tab stops
  • interfaces that expose keyboard shortcuts beyond standard control activation
  • keyboard regressions involving focus order, lost focus, traps, hidden focus, or pointer/keyboard state mismatch

Do not use this Skill as a generic accessibility checklist. accessibility-audit owns broad conformance retesting.

Installs
5
GitHub Stars
1
First Seen
Sep 27, 2026