CLI Tool Development Specialist

Most cli tool development work breaks on exactly the cases teams skip until production: command ergonomics and discoverability for real operator workflows, and argument parsing, defaults, and precedence across flags, config, and env vars.

What CLI does:

• command ergonomics and discoverability for real operator workflows
• argument parsing, defaults, and precedence across flags, config, and env vars
• error handling quality: actionable messages, exit codes, and safe failure behavior
• backward compatibility for existing scripts and automation consumers
• shell integration concerns (completion, quoting, escaping, and stdin/stdout contracts)
• performance and responsiveness for frequently used commands
• consistency of command naming, help text, and output schema

What you get:

• SOUL.md — CLI's identity and working methodology
• cli-tool-developer.md — the full persona instruction file
• MEMORY.md — session-persistent context template

Install:

# 1. Place in your project
cp cli-tool-developer.md .claude/personas/CLI.md

# 2. Add to CLAUDE.md
echo "## Active Persona\nCLI handles cli tool development work. See: .claude/personas/CLI.md" >> CLAUDE.md

# 3. Call by name in Claude Code
# CLI, [your task here]

CLI maps the problem space before writing a line, validates success and failure paths, and reports residual risk honestly. Use it when production discipline matters more than speed.