elianiva/opentui
agents/skills/opentui/SKILL.md
Build terminal UIs with OpenTUI. Covers the core API, keymaps, React and Solid bindings, components, layout, keyboard input, plugins, and testing.
$ install --global
skillsauthnpx skillsauth add elianiva/dotfiles opentuiInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 28, 2026, 3:29 AM60.4s1 file scanned
SKILL.md
- name:
- opentui
- description:
- Build terminal UIs with OpenTUI. Covers the core API, keymaps, React and Solid bindings, components, layout, keyboard input, plugins, and testing.
OpenTUI Skill
Canonical reference docs are authored once in sibling docs/**/*.mdx files.
Inside the OpenTUI repo, this skill root lives at packages/web/src/content/, so the same files are also visible at packages/web/src/content/docs/**/*.mdx.
Path invariant
/docs/<slug>maps todocs/<slug>.mdxrelative to this skill root- in the repo, that same slug maps to
packages/web/src/content/docs/<slug>.mdx
Reading order by area
- Getting started:
/docs/getting-started - Core:
/docs/core-concepts/renderer - Keymap:
/docs/keymap/overview - React:
/docs/bindings/react - Solid:
/docs/bindings/solid - Components:
/docs/components/text,/docs/components/input - Layout:
/docs/core-concepts/layout - Keyboard:
/docs/core-concepts/keyboard - Plugins:
/docs/plugins/slots - Reference:
/docs/reference/env-vars
Quick routing by intent
| Intent(s) | Start here |
| ---------------------------------------------------------- | --------------------------------- |
| getting-started, installation, quickstart, intro | docs/getting-started.mdx |
| core, renderer, terminal, scrollback, lifecycle | docs/core-concepts/renderer.mdx |
| keymap, keybindings, shortcuts, commands, leader | docs/keymap/overview.mdx |
| layout, flexbox, yoga, positioning | docs/core-concepts/layout.mdx |
| keyboard, input, keybindings, paste, focus | docs/core-concepts/keyboard.mdx |
| react, jsx, hooks, animation, testing | docs/bindings/react.mdx |
| solid, signals, jsx, hooks, animation, testing | docs/bindings/solid.mdx |
| plugins, plugin, slots, registry, extensions | docs/plugins/slots.mdx |
| text, styling, content, selection | docs/components/text.mdx |
| input, form, editing, focus | docs/components/input.mdx |
| env, environment, configuration, flags | docs/reference/env-vars.mdx |
For concrete component requests, jump straight to docs/components/<name>.mdx after the relevant entry page. For plugin implementation details, narrow from docs/plugins/slots.mdx into docs/plugins/core.mdx, docs/plugins/react.mdx, or docs/plugins/solid.mdx.
Current skill entry pages
docs/getting-started.mdxdocs/core-concepts/renderer.mdxdocs/keymap/overview.mdxdocs/core-concepts/layout.mdxdocs/core-concepts/keyboard.mdxdocs/bindings/react.mdxdocs/bindings/solid.mdxdocs/plugins/slots.mdxdocs/components/text.mdxdocs/components/input.mdxdocs/reference/env-vars.mdx
Working rules
- Prefer the current entry pages first, then read narrower docs in the same section.
- Read the sibling
docs/**/*.mdxfiles directly instead of copying prose into this file. - Use stable
/docs/...URLs when cross-referencing docs.
Related Skills
elianiva/web-design-guidelines
development
VerifiedTrustedCommunity
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
202SKILL.mdUpdated May 28, 2026
elianiva/thermo-nuclear-code-quality-review
development
VerifiedTrustedCommunity
Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially harsh maintainability review.
202SKILL.mdUpdated May 28, 2026
elianiva/session-retrospective
tools
VerifiedTrustedCommunity
At end of difficult sessions, analyze friction points and propose concrete improvements.
202SKILL.mdUpdated May 28, 2026
elianiva/root-cause-tracing
testing
VerifiedTrustedCommunity
Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior
202SKILL.mdUpdated May 28, 2026