Keyboard Shortcuts

Audit a web app for missing keyboard shortcuts and implement them end to end: a command registry, context-scoped bindings, a command palette, visible kbd hints, a ? help sheet, invariant tests, and WCAG 2.1.4 compliance. Use whenever the user mentions keyboard shortcuts, hotkeys, keybindings, a command palette, Cmd+K, power-user features, or making an app feel fast, and also when building or reviewing any list, table, modal, form, or editor UI where shortcuts and keyboard access obviously belong even if the user never says the word shortcut.

Testing & QA

Install

skills CLI (Claude Code, Cursor, Codex and more)

npx skills add nparashar150/claude-keyboard-shortcuts --skill keyboard-shortcuts

Manual install

git clone --depth 1 https://github.com/nparashar150/claude-keyboard-shortcuts.git /tmp/claude-keyboard-shortcuts
mkdir -p ~/.claude/skills
cp -r /tmp/claude-keyboard-shortcuts/skills/keyboard-shortcuts ~/.claude/skills/keyboard-shortcuts

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Keyboard shortcuts: audit and implement

Most codebases arrive at shortcuts the same way: a `useEffect` with `addEventListener('keydown')` in one component, another in a modal, a `cmdk` palette somebody wired up for search, and a `Cmd+S` handler that fights the browser. The keys nobody documented stop working when a text field has focus, and no two of them agree on what counts as "focused".

The job here is not to add more listeners. It is to find what is missing, separate the genuine defects from the nice-to-haves, and replace the scattered handlers with one small system where bindings are data and discoverability falls out for free.

Work in phases. Do not skip the audit and go straight to code: the value of this skill is mostly in deciding what deserves a key, and a keymap invented without reading the app will be wrong.

## Phase 0: scope the app before auditing it

Two questions decide the size of everything that follows.

**Is this a keyboard-relevant surface at all?** A marketing site, a CLI, a backend service, or a docs build gets Phase 1 Tier 0 only (keyboard access is still a legal and usability requirement) and nothing else. Say so and stop rather than bolting a command palette onto a landing page.

**What shape is the app?** This picks the interaction model, and getting it wrong is the most common failure:

| App shape | Model | Real examples |
|---|---|---|

Read the full skill on GitHub

Details

Skill name: keyboard-shortcuts
Repository: nparashar150/claude-keyboard-shortcuts
Path: skills/keyboard-shortcuts/SKILL.md
License: MIT
Repo updated: 13 September 2026
Listed in: karanb192/awesome-claude-skills

FAQ

What does the Keyboard Shortcuts skill do?

How do I install the Keyboard Shortcuts skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add nparashar150/claude-keyboard-shortcuts --skill keyboard-shortcuts. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Related skills

Prove It Ran

agentkitco/agentkit-dev-skills

Verify that tests, builds and checks actually ran and exercised the changed code, before claiming a task is done. Use before reporting completion, or when asked to prove tests ran or verify a fix.

Testing & QAIn 1 list

Grill

mtangoz/grill

Grill a decision, plan or forecast. An outside AI judge, a model from a different company than Claude, argues the strongest case for and against it, names the cheapest test that would settle each challenge, and gives a verdict. Use when the user says grill, stress-test, pressure-test, poke holes in, red-team or challenge something they decided or plan to decide, when the weekly review marks a decision for grilling, or when they say look back or paste a decision record to score.

Testing & QAIn 1 list

Test Checklist

Ifeanyiejindu/qarunbook

Build a complete QA test plan for an app — every module, feature and user journey, across each platform it runs on. Use when asked for a test plan, QA checklist, test cases, regression suite, or "what should we test", or when preparing an app for QA, a release or a demo. Writes the plan, puts it into qarunbook (creating the app, or adding to it), then offers to start testing it straight away.

Testing & QAIn 1 list

Never Again

malaysherasia-ai/claude-never-again

Capture a bug or mistake as a permanent guardrail so it cannot happen twice. Use this skill whenever a bug is fixed, a test fails and is repaired, the user says "you did that again", "don't do that", "remember this", "never do X", or any correction is made that a future session would otherwise forget. Also use when the user asks to review, promote, or clean up existing lessons and hooks.

Testing & QAIn 1 list

Watch

igamingsychov/watch-igaming

Смотрит любое видео - по ссылке (видеохостинг, запись экрана или встречи, прямой mp4) или локальный файл (.mov/.mp4) - не только читает транскрипт, но и видит, что на экране. Кадры берёт по сменам сцен (ffmpeg scene detection), а не по таймеру, поэтому не пропускает графику, демо, монтаж и b-roll. Звук: субтитры через yt-dlp, fallback - локальная расшифровка речи. Результат - разбор или таблица в нужном формате: QA-таблица, сравнение конкурентов, UX-аудит, протокол созвона, конспект лекции. Используй, когда пользователь пишет /watch <url> или просит «посмотри это видео», «разбери ролик/созвон/

Testing & QAIn 1 list

River Trash Boom Robot Design

dungnotnull/river-trash-boom-robot-design-agent-skill

Autonomous River Trash-Boom Design & Testing — Production-grade harness for Autonomous River Debris-Boom Robotics & Hydraulics evidence-backed analysis with real-time data aggregation, recognized domain methods, and self-improving knowledge pipeline.

Testing & QA

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.