opentui

OpenTUI is a framework for building terminal user interfaces, and this skill is the navigation layer over its canonical documentation, spanning the core API, native audio, keymaps, React and Solid bindings, components, layout, keyboard input, plugins, and testing. Rather than duplicating prose, it routes to sibling docs/**/*.mdx files authored once as the single source of truth. A path invariant keeps references stable: a /docs/<slug> URL maps to docs/<slug>.mdx relative to the skill root, and inside the OpenTUI repository the same slug resolves under packages/web/src/content/docs/. The skill lays out a reading order by area so callers know where to begin for each topic: getting started, the renderer for core concepts, audio, keymap overview, React and Solid bindings, the text and input components, layout, keyboard handling, plugin slots, testing, and the environment-variable reference. A quick routing table translates intents into entry documents: audio-related keywords such as native-audio, sound, playback, pcm, and fft point to docs/core-concepts/audio.mdx; layout, flexbox, and yoga point to docs/core-concepts/layout.mdx; keymap, keybindings, and leader point to docs/keymap/overview.mdx; and so on across renderer, keyboard, testing, plugins, text, input, and environment configuration. For a specific component the guidance is to jump straight to docs/components/<name>.mdx after the relevant entry page, and for plugin internals to narrow from docs/plugins/slots.mdx into the core, React, or Solid plugin docs. Working rules tell the reader to prefer the current entry pages first, then read narrower docs in the same section, to open the sibling .mdx files directly instead of copying their content, and to use the stable /docs/... URLs when cross-referencing. It suits anyone installing OpenTUI, wiring up a React or Solid terminal app, adding audio or keymaps, writing plugins, or testing terminal UI code, by pointing to the precise document for the task.