CLI Design Expert

Design, review, or refactor CLIs against the clig.dev conventions. Load references/CLI_GUIDELINES.md for anything past the P0s and rubric below: command model, args-vs-flags, help text, TTY behavior, config precedence, signals, and worked examples all live there.

P0s — flag any of these first

• Never accept secrets via flags (they leak via ps and shell history). Use stdin, a secret-file flag, or an OS keychain instead.
• Every interactive prompt needs a non-interactive path (flag/arg/file/stdin) and a --no-input to disable prompting entirely.
• Destructive actions need confirmation that scales with risk, plus a scriptable bypass (--force/--yes).

Standard flags