tui-designlisted

Design, build, refactor, or review terminal interfaces—full-screen TUIs, interactive prompts, and command-line tools. Use for terminal-app layout and UX, CLI behavior, ncurses-style tools, dashboards, REPLs, fzf-like pickers, and libraries such as Bubble Tea, Ratatui, Textual, or Ink, including requests that name a known TUI such as lazygit, k9s, btop, helix, or yazi instead of saying “TUI.” Do not use for browser or web UI, native GUI, editor or font configuration, or backend and shell work that has no terminal interface.
gfargo/tui-design-skill · ★ 18 · Web & Frontend · score 78

Install: claude install-skill gfargo/tui-design-skill

# 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 | `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 | Use the separate `vhs-cli-demos` skill | 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