Scaffold a CLI Tool

CLIs that get used (vs. abandoned) follow the same shape: subcommand structure, sane config precedence, JSON + human output, completion, signed releases, easy install. This scaffold is that shape.

When to use

• Building a CLI you'll ship publicly or share across a team.
• Tool is non-trivial: ≥3 subcommands, takes config from multiple sources.
• You'll publish via Homebrew, Scoop, npm, or GitHub Releases.

When NOT to use

• One-off bash script — overkill.
• Embedded CLI inside a larger app (e.g. next dev) — different scaffolding.
• TUI-heavy interactive tool — see Bubble Tea / Ink scaffolds (separate skills).

Pick a language