opentui-tui-builder

Design keyboard-native OpenTUI terminal interfaces with renderer cleanup and screen-mode selection.

3|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/joshka0/foxctl --skill opentui-tui-builder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opentui-tui-builder
Source: https://github.com/joshka0/foxctl/tree/main/configs/skills-external/opentui
Command: npx skills add https://github.com/joshka0/foxctl --skill opentui-tui-builder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you design terminal user interfaces that stay readable, responsive, and safe, even when handling focus, resizing, and terminal cleanup.

Core Features & Use Cases

  • Screen-mode and rendering guidance: Choose alternate-screen, main-screen, or split-footer correctly to prevent log clobbering and preserve user context.
  • Keyboard-first interaction patterns: Establish predictable focus, routing, shortcuts, forms, and help overlays that users can reliably operate.
  • Reliability and terminal restoration: Ensure renderer cleanup on success, errors, and interrupts to avoid leaving the terminal in a broken state.
  • Practical UI construction rules: Apply layout regions, borders usage, scroll behavior, code/diff views, tables degradation, and semantic theming for consistent UX.

Quick Start

Describe the OpenTUI TUI you want to build (screens, inputs, key flows, and whether it should run alongside existing CLI output) and ask for a focused implementation plan that includes rendering mode selection and safe cleanup paths.

Frequently Asked Questions about opentui-tui-builder

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

FAQPage Schema
How do I build a keyboard-native TUI that handles focus and resizing safely?

Screen-mode selection for terminal rendering requires choosing between alternate-screen, main-screen, or split-footer modes. This prevents log clobbering and preserves user context when building interactive terminal workflows.

How do I manage keyboard focus and navigation in a terminal user interface?

Keyboard focus and navigation in a TUI require establishing predictable routing, shortcuts, and accessible key conventions. This creates reliable interaction patterns for forms, selectors, and help overlays that users can operate consistently.

How do I restore the terminal state after a TUI application crashes or exits?

Restoring the terminal state after a TUI application exits requires ensuring renderer cleanup on success, errors, and interrupts. Explicit terminal restore via renderer.destroy prevents leaving the terminal in a broken state.

Can I run a terminal dashboard alongside existing CLI output without clobbering logs?

Yes, you can run interactive terminal interfaces alongside existing CLI output by selecting the correct screen-mode for rendering. Using main-screen or split-footer modes prevents log clobbering while preserving user context.

What are the limitations of building terminal user interfaces for varying terminal sizes?

Building terminal interfaces for varying terminal sizes requires applying responsive layout guidance, scroll behavior rules, and table degradation strategies. Layout regions and semantic theming must adapt to prevent broken rendering across dimensions.