tui-design
Installation
SKILL.md
TUI & CLI Design
Design terminal software that is calm, predictable, fast, and honest about the medium. Treat this file as the workflow and cross-cutting contract. Load detailed guidance from the one reference that owns it instead of reconstructing or repeating it here.
Route before answering
| Need | Authoritative reference |
|---|---|
| Go, Bubble Tea, Lipgloss, Bubbles, tview, gocui | references/ecosystem-go.md |
| Rust, Ratatui, crossterm, Cursive | references/ecosystem-rust.md |
| Python, Textual, Rich, prompt_toolkit, urwid | references/ecosystem-python.md |
| TypeScript/JavaScript, Ink, OpenTUI, Clack, Inquirer | references/ecosystem-typescript.md |
| One-shot commands, arguments, streams, exit codes, automation | references/cli-basics.md |
| Layouts, buffers, borders, hierarchy, color, density, responsive behavior, tables, themes, accessibility (screen readers, plain mode, motion) | references/visual-patterns.md |
| Keys, focus, navigation, modes, forms, mouse, confirmation, undo, OSC features | references/interaction-patterns.md |
| Case studies: lazygit, k9s, fzf, btop, helix, yazi, atuin | references/exemplar-apps.md |
| Screenshots or demo recordings | The vhs-cli-demos skill when installed; otherwise references/cli-basics.md → Demo recordings |
Load only the references the task needs. When the prompt names a framework or ecosystem, always load its ecosystem reference before making API, lifecycle, implementation, or testing claims. Ecosystem references own those specifics. The visual and interaction references own their domains for every ecosystem. Exemplar apps are evidence and inspiration, not substitutes for the pattern references.