nw-ux-tui-patterns

# TUI and CLI Patterns Actionable terminal interface patterns for requirements gathering and design review. Use when target is CLI tool or interactive terminal application. ## CLI Argument Design ### Command Structure Follow `program subcommand [flags] [arguments]` (e.g., `git commit -m "message"`). ### Flags and Options - Both short (`-h`) and long (`--help`) for common flags - Reserve single-letter flags for frequently used options - Standard flags always: `--help`, `--version`, `--verbose`/`--quiet`, `--no-color` - Never accept secrets via flags (use files, stdin, or env vars) - Make flag order independent ### Subcommands - Verbs for actions: `create`, `delete`, `list`, `show`, `update` - Nouns for targets: `user`, `project`, `config` - Pick one pattern (`tool resource action` or `tool action resource`) consistently - Provide shell completion scripts for discoverability ### Argument Design Principles Required arguments are positional; optional use flags. Accept stdin for piping. Support glob patterns for file arguments. Provide `--dry-run` for destructive/complex operations. ## Interactive TUI Patterns ### Framework Architectures | Framework | Language | Architecture | Best For | |-----------|----------|-------------|----------| | **Bubble Tea** | Go | Elm (Model-Update-View) | Full TUI apps with complex state | | **Rich** | Python | Declarative rendering | Beautiful output, progress, tables | | **Ink** | JavaScript | React component model | Teams with React exper...