cli-developer

# CLI Developer ## Core Workflow 1. **Analyze UX** — Identify user workflows, command hierarchy, common tasks. Validate by listing all commands and their expected `--help` output before writing code. 2. **Design commands** — Plan subcommands, flags, arguments, configuration. Confirm flag naming is consistent and no existing signatures are broken. 3. **Implement** — Build with the appropriate CLI framework for the language (see Reference Guide below). After wiring up commands, run `<cli> --help` to verify help text renders correctly and `<cli> --version` to confirm version output. 4. **Polish** — Add completions, help text, error messages, progress indicators. Verify TTY detection for color output and graceful SIGINT handling. 5. **Test** — Run cross-platform smoke tests; benchmark startup time (target: <50ms). ## Reference Guide Load detailed guidance based on context: | Topic | Reference | Load When | |-------|-----------|-----------| | Design Patterns | `references/design-patterns.md` | Subcommands, flags, config, architecture | | Node.js CLIs | `references/node-cli.md` | commander, yargs, inquirer, chalk | | Python CLIs | `references/python-cli.md` | click, typer, argparse, rich | | Go CLIs | `references/go-cli.md` | cobra, viper, bubbletea | | UX Patterns | `references/ux-patterns.md` | Progress bars, colors, help text | ## Quick-Start Example ### Node.js (commander) ```js #!/usr/bin/env node // npm install commander const { program } = require('commander'); prog...