opentui

Guide terminal UI builders in selecting OpenTUI frameworks and implementing TUI components.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/mpsuesser/workspace --skill opentui-mpsuesser
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opentui
Source: https://github.com/mpsuesser/workspace/tree/main/dotconfig/pi/agent/skills/__techs__/opentui
Command: npx skills add https://github.com/mpsuesser/workspace --skill opentui-mpsuesser

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

OpenTUI TUI developers need a single, reliable reference that explains which framework to use and how to implement components correctly without breaking runtime behavior or styling rules.

Core Features & Use Cases

  • Framework selection guidance (core, React, Solid): Quickly choose the right OpenTUI layer for maximum control, React familiarity, or Solid reactivity, and follow the right entry references.
  • Implementation guardrails: Avoid common runtime and developer pitfalls like calling process.exit() directly, using the wrong create-tui argument ordering, and applying React/Solid text styling incorrectly.
  • Task-oriented component and layout decisioning: Find the correct component docs for text, containers, inputs, code/diff, plus layout, keyboard handling, animations, testing, and troubleshooting.

Quick Start

Use the OpenTUI reference docs for the React, Solid, or core framework you chose, then implement your TUI using the component category guides and the critical rules for styling and cleanup.

Frequently Asked Questions about opentui

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

FAQPage Schema
How do I build terminal UIs with React or Solid reconcilers?

Use the OpenTUI reference docs to select the React or Solid reconciler layer, then implement components and styling following the framework-specific guidelines. Reconcilers map component state updates to terminal rendering.

What is the best way to choose between core, React, and Solid for TUI development?

Select core OpenTUI for maximum imperative control, React for component familiarity, or Solid for fine-grained reactivity. The framework selection guidance maps your paradigm choice to the correct entry references.

Why does my terminal UI styling break when applying text styles in React or Solid?

Terminal UI styling breaks when applying React or Solid text styles incorrectly. The OpenTUI implementation guardrails specify the correct styling rules per reconciler to prevent rendering failures and ensure proper output.

How do I handle keyboard input and animations in a terminal UI?

Reference the OpenTUI task-oriented component guides for keyboard handling and animations. These docs cover layout, input events, and animation execution alongside troubleshooting for terminal UI components.

What are common runtime pitfalls in terminal UI development and how do I avoid them?

Common runtime pitfalls include calling process.exit() directly and using wrong create-tui argument ordering. OpenTUI implementation guardrails identify these failures and provide correct usage patterns to ensure stable execution.

Do I need to write tests for my terminal UI components?

Testing terminal UI components is supported through OpenTUI task-oriented guides. The reference docs include testing instructions alongside implementation guidance for text, containers, inputs, and code diff components.