keyboard-shortcuts

Generates a searchable, up-to-date, and reliable index of the entire codebase and its structural interdependencies and attributesbba.

1.0k|79|Updated Dec 26, 2025
One-click install
npx skills add https://github.com/marcus/sidecar --skill keyboard-shortcuts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: keyboard-shortcuts
Source: https://github.com/marcus/sidecar/tree/main/.claude/skills/keyboard-shortcuts
Command: npx skills add https://github.com/marcus/sidecar --skill keyboard-shortcuts

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Keyboard shortcut governance across Sidecar plugins is inconsistent, making it harder for users to learn and rely on common actions.

Core Features & Use Cases

  • Centralized reference: Provides a complete catalog of keyboard bindings, their contexts, and recommended implementation patterns.
  • Usage guidance: Documents how to add, modify, and align shortcuts with vim-like conventions and UI patterns.
  • Audit and onboarding: Helps teams review bindings for conflicts, mnemonic coherence, and UX consistency across modules.

Quick Start

Start using the canonical Sidecar shortcuts across plugins to speed up navigation and actions.

Frequently Asked Questions about keyboard-shortcuts

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I align keyboard shortcuts across Sidecar plugins to prevent conflicts?

Align keyboard shortcuts across Sidecar plugins by applying a centralized reference catalog that documents bindings, contexts, and implementation patterns to reduce user friction. This ensures consistent command execution and UI navigation across all modules.

What is the best way to audit keyboard bindings for UX consistency?

Audit keyboard bindings by reviewing them for conflicts, mnemonic coherence, and UX consistency across modules. This process checks vim-like conventions and UI patterns to maintain standardized accessibility across plugins.

How do I add new keyboard shortcuts that match existing vim-like conventions?

Add new keyboard shortcuts by following documented implementation patterns that align with vim-like conventions and UI standards. This maintains mnemonic coherence and prevents binding conflicts across the Sidecar ecosystem.

When do I need centralized keyboard shortcut documentation for onboarding?

Centralized keyboard shortcut documentation is needed during onboarding to help new users learn common actions quickly. It provides a complete catalog of bindings and contexts, reducing the learning curve for plugin navigation.

Does the keyboard shortcuts reference support conflict resolution for UI navigation?

The keyboard shortcuts reference supports conflict resolution by auditing bindings across plugins for overlapping commands. It documents integration points and centralized patterns to resolve UI navigation conflicts effectively.

Why does keyboard shortcut governance matter for Sidecar plugin development?

Keyboard shortcut governance matters because inconsistent bindings across Sidecar plugins make it harder for users to learn and rely on common actions. Centralized documentation ensures standardized implementation for future enhancements.