Quick Setup Guide
1. Add the Element
Drag the "Keyboard Shortcut Handler" element onto your page. The element is invisible and can be placed anywhere - it will automatically handle keyboard events for the entire page.

2. Configure Your Shortcut
In the Property Editor:
- Shortcut Key: Enter a single key (e.g., "s", "Enter", "Escape", "ArrowUp")
- Cmd/Ctrl Modifier: Check this for Ctrl (Windows) or Cmd (Mac) combinations
- Alt/Shift Modifiers: Add additional modifier keys as needed
- Prevent Default: Enable to override browser shortcuts (recommended)
- Description: Add a description for user help systems

3. Create the Workflow
- Click "Start/Edit workflow" on the element
- Select the "When Shortcut is pressed" event
- Add your desired actions (save data, show popup, navigate, etc.)

Common Shortcut Examples:
- Save: Key="s" + Cmd/Ctrl ✓
- Search: Key="k" + Cmd/Ctrl ✓
- New Item: Key="n" + Cmd/Ctrl ✓
- Quick Menu: Key="/" (no modifiers)
- Cancel: Key="Escape" (no modifiers)

4. Advanced Features
Dynamic Control: Use the "Enable Shortcut", "Disable Shortcut", and "Toggle Shortcut" actions in workflows to control shortcuts based on user context or application state.
State Management: Access the "Shortcuts Active", "Last Triggered Shortcut", and "Shortcut Description" states to build user feedback systems and shortcut help overlays.
Multiple Shortcuts: Add multiple Keyboard Shortcut Handler elements for different key combinations. Each element operates independently with optimized performance.

5. Best Practices
- Use standard conventions: Ctrl+S for save, Ctrl+K for search, Escape for cancel
- Test on both Windows and Mac to ensure cross-platform consistency
- Provide visual cues about available shortcuts using the exposed states
- Enable "Prevent Default" for shortcuts that might conflict with browser functions
- Group related shortcuts with consistent modifier patterns for user familiarity

6. Technical Notes
The plugin uses optimized event handling with cached property processing to ensure zero-lag performance. Key matching is performed through early exit patterns, and modifier states are pre-computed to minimize runtime overhead. Event listeners use passive:false configuration to support preventDefault functionality while maintaining optimal performance characteristics.