opentui

What problem does it solve? Building rich terminal applications requires coordinating rendering, layout, keyboard input, audio, and framework bindings across many APIs. This Skill routes you to the correct OpenTUI documentation for each task so you can implement terminal UIs without guessing which component or reference page applies. ## Core Features & Use Cases - Intent-based doc routing: Maps requests like audio playback, keymaps, React/Solid bindings, plugins, QR encoding, SSH, and Three.js WebGPU to the right docs/**/*.mdx reference page. - Component guidance: Covers core components such as Box, Text, Input, Code (Tree-sitter highlighting), and ASCIIFont with properties and usage examples. - Runtime and packaging references: Includes environment variables, standalone executables (Bun compile and Node.js SEA), package entrypoints, and testing with snapshot renderers. - Use Case: You want to add streaming internet radio with ICY metadata to a terminal app. The Skill routes you to the native audio docs covering playStreamUrl, reconnect options, and metadata events. ## Quick Start Ask how to create a terminal UI with OpenTUI, for example how to render a bordered box with text or handle keyboard input, and the Skill will load the relevant documentation. ## Quick Start Tell the agent to build a terminal UI feature with OpenTUI, such as a bordered panel with text and keybindings, and it will consult the matching docs.