tui-navigation-guardrails

Enforce safe pane navigation and focus alignment in terminal UI.

Updated Feb 23, 2026
One-click install
npx skills add https://github.com/tacogips/divedra --skill tui-navigation-guardrails
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tui-navigation-guardrails
Source: https://github.com/tacogips/divedra/tree/main/.agents/skills/tui-navigation-guardrails
Command: npx skills add https://github.com/tacogips/divedra --skill tui-navigation-guardrails

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces safe, predictable terminal UI navigation by restricting pane focus changes and key handling to align with the repository's TUI rules and design specs.

Core Features & Use Cases

  • Defines invariants such as only the focused pane rendering an active selected-row state and aligning enter/ctrl-m within the same pane.
  • Provides an implementation checklist (read required docs, update help text, adjust design docs, and update tests) to guide developers when changing TUI navigation.
  • Covers deep-pane navigation semantics (l/h movements, esc to parent) and prevents reusing navigation keys for unrelated global actions.

Quick Start

Review the TUI guidelines and implement focus-safe navigation changes according to the guardrails.

Frequently Asked Questions about tui-navigation-guardrails

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

FAQPage Schema
How do I prevent pane focus and selected-row misalignment in terminal UI navigation?

To prevent pane focus misalignment in terminal UI navigation, enforce invariants restricting focus changes to the active pane and aligning enter/ctrl-m keybindings within that same pane. This ensures safe, predictable TUI behavior across development workflows.

What are the standard navigation keybindings for switching between TUI panes and detail viewers?

Standard TUI pane navigation uses deep-pane semantics where l/h movements switch between panes and esc returns to the parent. Reusing these specific navigation keys for unrelated global actions is prohibited to maintain predictable focus behavior.

When do I need to update tests and design docs for terminal UI navigation changes?

You need to update tests and design docs for terminal UI navigation changes whenever modifying TUI key handling or focus behavior. An implementation checklist requires reading required docs, adjusting design specs, updating help text, and adding test coverage to ensure alignment.

Why does only one pane render an active selected-row state in my terminal UI?

Only one pane renders an active selected-row state in terminal UIs to enforce a strict invariant guaranteeing that focus and selection never diverge. This design spec rule prevents multiple panes from simultaneously displaying conflicting active selection states.

Can I reuse terminal UI navigation keys for global actions like opening settings?

You cannot reuse terminal UI navigation keys for global actions like opening settings. The guardrails explicitly prevent reusing navigation keys for unrelated global actions to avoid focus hijacking and maintain predictable pane switching behavior.