Cli Developer

A solid framework for building production CLIs across Node, Python, and Go. The workflow is sensible: analyze UX first, design your command structure, implement with the right framework (commander, click/typer, cobra), then polish with completions and proper error handling. The constraints section is the real value here, calling out common mistakes like blocking on sync I/O, printing colors to non-TTY outputs, and breaking command signatures. The 50ms startup target is aggressive but correct. References are organized by language and topic, which beats dumping everything in one file. If you're wiring up argument parsing or adding interactive prompts, this gets you to working code faster than reading framework docs from scratch.

skills.sh installs: 5.1K
GitHub stars: 12.3K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add jeffallan/claude-skills --skill cli-developer --agent claude-code

Installs into .claude/skills of the current project.

Files

CLI Developer

Core Workflow

Analyze UX — Identify user workflows, command hierarchy, common tasks. Validate by listing all commands and their expected --help output before writing code.
Design commands — Plan subcommands, flags, arguments, configuration. Confirm flag naming is consistent and no existing signatures are broken.
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.
Polish — Add completions, help text, error messages, progress indicators. Verify TTY detection for color output and graceful SIGINT handling.
Test — Run cross-platform smoke tests; benchmark startup time (target: <50ms).