| name | cli-tui-design-language |
| description | Design or critique terminal software. Use for CLI command trees, help text, flags, stdout/stderr, prompts, errors, progress, TUI layout, keybindings, search, no-color behavior, and terminal accessibility. |
Use this skill when the work is terminal UX, not generic app UX.
- Read cli-design.md for command trees, naming, help, flags, streams, machine modes, prompts, errors, and progress.
- Read tui-design.md for panes, tables, detail views, navigation, keybindings, focus, search, status bars, and empty states.
- Read accessibility.md for keyboard use, focus visibility, contrast, no-color behavior, and terminal-specific accessibility constraints.
- Read anti-patterns.md before polishing output. It captures common terminal UX failures.
- Read examples.md when the design needs concrete help text, output, status, or layout examples.
- Read commands.md when you need a fast design pass.
- Read references.md when you need to check what is standard-backed, convention-backed, or house style.
Core doctrine:
- Keep CLI and TUI guidance separate when their tradeoffs differ.
- Treat machine-readable output as an explicit contract.
- Put human messaging on
stderr, primary output on stdout.
- Do not depend on color alone for state, focus, or severity.
- Keep focus, selection, and mode visibly distinct.
- Label standards as standards, conventions as conventions, and house style as house style.
