tab-control

Bridge native macOS keyboard events to web contexts for Tab navigation.

9|3|Updated Jan 13, 2026
One-click install
npx skills add https://github.com/firstloophq/nomendex --skill tab-control
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tab-control
Source: https://github.com/firstloophq/nomendex/tree/main/.claude/skills/tab-control
Command: npx skills add https://github.com/firstloophq/nomendex --skill tab-control

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Focus management across native macOS WKWebView and browser environments to ensure reliable keyboard navigation and visible focus indicators.

Core Features & Use Cases

  • Unified keyboard bridge for Tab/Shift+Tab navigation between Swift and JS contexts.
  • ProseMirror-aware focus handling with editor-aware dispatch of Tab events.
  • Consistent focus ring behavior and Cmd+Enter submission support across platforms.

Quick Start

Launch the app and verify Tab navigation and focus ring consistency across the Mac app and web browser, including Cmd+Enter handling.

Frequently Asked Questions about tab-control

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

FAQPage Schema
How do I fix Tab keyboard navigation not working in WKWebView on macOS?

ProseMirror editor focus handling intercepts Tab events to manage indentation and element insertion. It uses editor context detection to dispatch keyboard events natively, ensuring reliable focus behavior within rich text editors on macOS and web browsers.

How do I manage focus rings and Cmd+Enter submission across macOS and web platforms?

Manage focus rings and Cmd+Enter submission by unifying keyboard bridge logic for Tab and Shift+Tab navigation. This approach delivers consistent focus ring visibility and reliable submission support across both native macOS apps and web browser contexts.

Does keyboard focus management work the same in WKWebView and standard web browsers?

Yes, focus management works consistently across WKWebView and web browsers. The implementation bridges native macOS keyboard events to web contexts, ensuring uniform Tab navigation and focus indicators across both environments without requiring separate logic.

Why does focus indicator visibility break when navigating through dialogs in macOS apps?

Focus indicator visibility breaks due to mismatched native-to-web event dispatching. Bridging macOS keyboard events to the web context ensures consistent focus ring behavior across regular focusable elements, ProseMirror editors, and dialogs in both environments.