CLI Developer guides Claude through building a command-line tool: map the user workflows, design the command tree, implement with the right framework, polish and test.
It covers commander, yargs and inquirer for Node, click, typer and rich for Python, and cobra, viper and bubbletea for Go, and sets firm rules for output, interactivity and startup time.
What You Get
- A command structure with an entry point and subcommands
- Configuration handling across files, environment variables and flags
- Implementation with clear, actionable error messages
- Shell completion scripts for bash, zsh and fish where the framework supports them
- A short explanation of the user experience decisions
Common Use Cases
- Starting a new Node.js CLI with commander
- Building a Python tool with click or typer
- Writing a Go CLI with cobra and viper
- Adding progress bars, spinners and prompts
- Generating shell completions for an existing tool
What Makes It Unique
The rules cover real terminal behavior: send diagnostics to stderr when output is piped, skip color when output is not a TTY, give non-interactive fallbacks for CI and resolve paths with home directory helpers. Reference files are split by language and by UX patterns.
Under The Hood
The skill is a SKILL.md with five reference files for design patterns, Node, Python, Go and UX patterns. It has no scripts of its own. During a run the agent builds the tool in your project and runs it, calling the new command with —help and —version and running cross-platform smoke tests and startup benchmarks, so it executes shell commands and writes source files there. It does not fetch web pages or call outside APIs.