clilisted

# CLI — CLI Tool Development ## Activate When - User invokes `/godmode:cli` - User says "CLI tool", "command line", "terminal app", "console application" - User mentions "TUI", "terminal UI", "interactive prompt" - User mentions "Commander", "Clap", "Cobra", "Click", "yargs", "argparse" - User mentions "Ink", "Ratatui", "Bubbletea", "Rich", "Textual" - When designing argument parsing, subcommands, or flag interfaces - When generating shell completions (bash, zsh, fish, PowerShell) - When distributing CLI tools via package managers ## Workflow ### Step 1: CLI Project Assessment Determine the CLI development approach: ``` CLI PROJECT ASSESSMENT: Project type: <new CLI | adding CLI to existing project | TUI application> Language: <Node.js/TypeScript | Rust | Go | Python | other> Complexity: <simple (few commands) | medium (subcommands) | complex (TUI/interactive)> Argument parsing: Node.js: <Commander | yargs | meow | oclif> Rust: <Clap (derive) | Clap (builder) | argh> Go: <Cobra | urfave/cli | kong> Python: <Click | Typer | argparse | Fire> Interactive features: Prompts: <yes (inquirer/dialoguer/survey/questionary) | no> Progress bars: <yes | no> Spinners: <yes | no> ``` ### Step 2: CLI Architecture #### Node.js/TypeScript CLI ``` TYPESCRIPT CLI STRUCTURE: ├── src/ │ ├── index.ts # Entry point, argument parsing setup │ ├── commands/ # Subcommand implementations │ │ ├── init.ts # `tool init` command │ │