opentui
msmps/opentui-skill
Build terminal UIs with Core, React, or Solid APIs—components, layout, keyboard, animations, and testing.
What is opentui?
OpenTUI is a framework for building terminal user interfaces with your choice of imperative (Core), React, or Solid APIs. Use it when you need to create interactive CLI applications with components, layouts, keyboard handling, animations, and comprehensive testing support.
- Choose from three frameworks: Core (imperative, maximum control), React (familiar component patterns), or Solid (fine-grained reactivity)
- Build with pre-made components: text display, containers, inputs, code/diff viewers, tables, images, QR codes, and more
- Handle keyboard input with low-level events, focus management, clipboard access, and declarative layered keybindings
- Create responsive layouts using Flexbox-style positioning, absolute positioning, and terminal-size-aware patterns
- Animate properties with timeline-based animations, easing functions, and transitions
- Test TUI applications with snapshot testing, interaction testing, and a dedicated test renderer
How to install opentui
npx skills add https://github.com/msmps/opentui-skill --skill opentui- Bun runtime (OpenTUI runs on Bun)
- Node.js or Bun for package management
- Zig compiler for native builds (see core/gotchas.md for details)
How to use opentui
- 1.Run `npx skills add https://github.com/msmps/opentui-skill --skill opentui` to install the skill
- 2.Choose your framework: read `./references/<framework>/REFERENCE.md` (core, react, or solid)
- 3.For new projects, use `bunx create-tui -t <framework> <project-name>` with options before arguments
- 4.Consult decision trees in the skill for your task: display content, user input, layout, animations, keyboard handling, or testing
- 5.Read the relevant reference files: `api.md` for components, `configuration.md` for setup, `patterns.md` for best practices, `gotchas.md` for troubleshooting
Use cases
- Build an interactive CLI dashboard with real-time data display and keyboard navigation
- Create a code editor or diff viewer with syntax highlighting and custom keybindings
- Develop a form-based terminal application with input validation and multi-step workflows
- Build a terminal UI library or framework on top of OpenTUI's Core API
- Implement a terminal-based game or interactive visualization with animations
- CLI tool developers building interactive terminal applications
- Frontend developers familiar with React or Solid wanting to build TUIs
- Library authors creating terminal UI frameworks or components
- DevOps engineers building terminal dashboards and monitoring tools
opentui FAQ
Use Core for maximum control and performance with an imperative API; React if you're familiar with React patterns; Solid for fine-grained reactivity and optimal re-renders. Core is also required if you're building a library on top of OpenTUI.
Run `bunx create-tui -t <framework> <project-name>` where framework is `core`, `react`, or `solid`. Important: options must come before arguments.
Never call `process.exit()` directly—use `renderer.destroy()` instead. Text styling in React/Solid requires nested modifier elements, not props. Always use `create-tui` for new projects. Options in `create-tui` must come before arguments.
Use `keyboard/REFERENCE.md` for low-level keyboard events, focus management, and clipboard access. Use `keymap/REFERENCE.md` for declarative, layered keybindings with support for leader keys and commands.
OpenTUI includes text display (styled text, images, QR codes, ASCII art), containers (boxes, scrollbars), inputs (text field, textarea, select, slider), code/diff viewers, tables, and more. See `components/REFERENCE.md` for the full index.
Full instructions (SKILL.md)
Source of truth, from msmps/opentui-skill.
name: opentui description: OpenTUI skill for building terminal user interfaces with the Core, React, or Solid APIs. Use for any TUI task including components, layout, keyboard and keymap handling, animations, and testing. metadata: references: core, react, solid, components, layout, keyboard, keymap, animation, testing
OpenTUI Platform Skill
Consolidated skill for building terminal user interfaces with OpenTUI. Use decision trees below to find the right framework and components, then load detailed references.
Critical Rules
Follow these rules in all OpenTUI code:
- Use
create-tuifor new projects. See frameworkREFERENCE.mdquick starts. create-tuioptions must come before arguments.bunx create-tui -t react my-appworks,bunx create-tui my-app -t reactdoes NOT.- Never call
process.exit()directly. Userenderer.destroy()(seecore/gotchas.md). - Text styling requires nested tags in React/Solid. Use modifier elements, not props (see
components/text-display.md).
How to Use This Skill
Reference File Structure
Framework references follow a 5-file pattern. Cross-cutting concepts are single-file guides.
Each framework in ./references/<framework>/ contains:
| File | Purpose | When to Read |
|---|---|---|
REFERENCE.md | Overview, when to use, quick start | Always read first |
api.md | Runtime API, components, hooks | Writing code |
configuration.md | Setup, tsconfig, bundling | Configuring a project |
patterns.md | Common patterns, best practices | Implementation guidance |
gotchas.md | Pitfalls, limitations, debugging | Troubleshooting |
Cross-cutting concepts in ./references/<concept>/ have REFERENCE.md as the entry point.
Reading Order
- Start with
REFERENCE.mdfor your chosen framework - Then read additional files relevant to your task:
- Building components ->
api.md+components/<category>.md - Setting up project ->
configuration.md - Layout/positioning ->
layout/REFERENCE.md - Keyboard/input handling ->
keyboard/REFERENCE.md - Layered keybindings/commands ->
keymap/REFERENCE.md - Animations ->
animation/REFERENCE.md - Troubleshooting ->
gotchas.md+testing/REFERENCE.md
- Building components ->
Example Paths
./references/react/REFERENCE.md # Start here for React
./references/react/api.md # React components and hooks
./references/solid/configuration.md # Solid project setup
./references/components/inputs.md # Input, Textarea, Select docs
./references/core/gotchas.md # Core debugging tips
Runtime Notes
OpenTUI runs on Bun and uses Zig for native builds. Read ./references/core/gotchas.md for runtime requirements and build guidance.
Quick Decision Trees
"Which framework should I use?"
Which framework?
├─ I want full control, maximum performance, no framework overhead
│ └─ core/ (imperative API)
├─ I know React, want familiar component patterns
│ └─ react/ (React reconciler)
├─ I want fine-grained reactivity, optimal re-renders
│ └─ solid/ (Solid reconciler)
└─ I'm building a library/framework on top of OpenTUI
└─ core/ (imperative API)
"I need to display content"
Display content?
├─ Plain or styled text -> components/text-display.md
├─ Container with borders/background -> components/containers.md
├─ Scrollable content area -> components/containers.md (scrollbox)
├─ Standalone scrollbar -> components/containers.md (scrollbar)
├─ ASCII art banner/title -> components/text-display.md (ascii-font)
├─ PNG/JPEG/WebP/GIF image -> components/text-display.md (image)
├─ First-draw diagnostic -> components/text-display.md (time-to-first-draw)
├─ QR code -> components/text-display.md (qr-code, @opentui/qrcode)
├─ Embedded child terminal/VT output -> components/containers.md (Core only)
├─ Data table with borders/wrapping -> components/code-diff.md (TextTable)
├─ Code with syntax highlighting -> components/code-diff.md
├─ Diff viewer (unified/split, hunk nav) -> components/code-diff.md
├─ Line numbers with diagnostics -> components/code-diff.md
└─ Markdown content (streaming) -> components/code-diff.md (markdown)
"I need user input"
User input?
├─ Single-line text field -> components/inputs.md (input)
├─ Multi-line text editor -> components/inputs.md (textarea)
├─ Select from a list (vertical) -> components/inputs.md (select)
├─ Tab-based selection (horizontal) -> components/inputs.md (tab-select)
├─ Value slider -> components/inputs.md (slider)
├─ Declarative/layered keybindings -> keymap/REFERENCE.md (@opentui/keymap)
└─ Custom keyboard shortcuts -> keyboard/REFERENCE.md
"I need layout/positioning"
Layout?
├─ Flexbox-style layouts (row, column, wrap) -> layout/REFERENCE.md
├─ Absolute positioning -> layout/patterns.md
├─ Responsive to terminal size -> layout/patterns.md
├─ Centering content -> layout/patterns.md
└─ Complex nested layouts -> layout/patterns.md
"I need animations"
Animations?
├─ Timeline-based animations -> animation/REFERENCE.md
├─ Easing functions -> animation/REFERENCE.md
├─ Property transitions -> animation/REFERENCE.md
└─ Looping animations -> animation/REFERENCE.md
"I need to handle input"
Input handling?
├─ Keyboard events (keypress, release) -> keyboard/REFERENCE.md
├─ Layered bindings, commands, leader keys -> keymap/REFERENCE.md
├─ Focus management -> keyboard/REFERENCE.md
├─ Paste events -> keyboard/REFERENCE.md
├─ Mouse events -> components/containers.md
├─ Text selection & copy-on-select -> keyboard/REFERENCE.md (selection)
└─ Host/terminal clipboard service or OSC 52 -> keyboard/REFERENCE.md (clipboard)
"I need to test my TUI"
Testing?
├─ Snapshot testing -> testing/REFERENCE.md
├─ Interaction testing -> testing/REFERENCE.md
├─ Test renderer setup -> testing/REFERENCE.md
└─ Debugging tests -> testing/REFERENCE.md
"I need platform capabilities (audio, images, clipboard, notifications, SSH)"
Platform capability?
├─ Play loaded sound or MP3/FLAC stream -> core/api.md (Audio)
├─ Capture microphone PCM / record WAV -> core/api.md (Audio)
├─ Decode, transform, or display images -> components/text-display.md (image)
├─ Read/write host or terminal clipboard -> keyboard/REFERENCE.md (clipboard)
├─ Desktop notifications (OSC 9/777/99) -> core/api.md (triggerNotification)
├─ Custom stdin/stdout (PTY, xterm.js) -> core/api.md (createCliRenderer)
└─ Serve a TUI over SSH -> core/REFERENCE.md (@opentui/ssh)
"I need to debug/troubleshoot"
Troubleshooting?
├─ Runtime errors, crashes -> <framework>/gotchas.md
├─ Layout issues -> layout/REFERENCE.md + layout/patterns.md
├─ Input/focus issues -> keyboard/REFERENCE.md
└─ Repro + regression tests -> testing/REFERENCE.md
Troubleshooting Index
- Terminal cleanup, crashes ->
core/gotchas.md - Text styling not applying ->
components/text-display.md - Input focus/shortcuts ->
keyboard/REFERENCE.md - Layout misalignment ->
layout/REFERENCE.md - Flaky snapshots ->
testing/REFERENCE.md
For component naming differences and text modifiers, see components/REFERENCE.md.
Product Index
Frameworks
| Framework | Entry File | Description |
|---|---|---|
| Core | ./references/core/REFERENCE.md | Imperative API, all primitives |
| React | ./references/react/REFERENCE.md | React reconciler for declarative TUI |
| Solid | ./references/solid/REFERENCE.md | SolidJS reconciler for declarative TUI |
Cross-Cutting Concepts
| Concept | Entry File | Description |
|---|---|---|
| Layout | ./references/layout/REFERENCE.md | Yoga/Flexbox layout system |
| Components | ./references/components/REFERENCE.md | Component reference by category |
| Keyboard | ./references/keyboard/REFERENCE.md | Low-level keyboard input handling |
| Keymap | ./references/keymap/REFERENCE.md | Declarative layered keybindings (@opentui/keymap) |
| Animation | ./references/animation/REFERENCE.md | Timeline-based animations |
| Testing | ./references/testing/REFERENCE.md | Test renderer and snapshots |
Component Categories
| Category | Entry File | Components |
|---|---|---|
| Text & Display | ./references/components/text-display.md | text, ascii-font, image, time-to-first-draw, styled text, qr-code |
| Containers | ./references/components/containers.md | box, scrollbox, scrollbar, embedded-terminal, borders |
| Inputs | ./references/components/inputs.md | input, textarea, select, tab-select, slider |
| Code & Diff | ./references/components/code-diff.md | code, line-number, diff, markdown, text-table |
Additional Packages
| Package | Description | Docs |
|---|---|---|
@opentui/keymap | Layered keybinding/command engine (Bun or Node, no FFI) | ./references/keymap/REFERENCE.md |
@opentui/qrcode | QR code component | ./references/components/text-display.md |
@opentui/ssh | Serve a TUI over SSH | ./references/core/REFERENCE.md |
@opentui/three | Three.js WebGPU renderer (formerly core/src/3d) | upstream packages/three |
@opentui/examples | Runnable examples (formerly core/src/examples) | upstream packages/examples |
Core also ships loaded/streaming/captured Audio, native images, host and terminal clipboard services, and OSC desktop notifications.
Resources
Repository: https://github.com/anomalyco/opentui Core Docs: https://github.com/anomalyco/opentui/tree/main/packages/core/docs Examples: https://github.com/anomalyco/opentui/tree/main/packages/examples/src Awesome List: https://github.com/msmps/awesome-opentui
Related skills
More from msmps/opentui-skill and the wider catalog.

msw-avatar
Manage avatar costumes (17 equip slots) and animation state mapping for any entity.

msw-behaviourtree
End-to-end authoring for MSW `.behaviourtree` files with automatic spec generation and validation.

msw-combat-system
Complete MSW 2D combat system integration covering attack resolution, damage, hit reactions, game feel, and AI FSM.

msw-defaultplayer
Manage DefaultPlayer character model, components, movement, physics, HP, and camera settings.

msw-general
Foundation skill for MapleStory Worlds game creation—templates, builders, and visual polish principles.

msw-packages
Official prebuilt feature packages for MSW game systems—check before building from scratch.