Prompt · Developer Tools

CLI UX Review

Reviews a command-line tool's interface for usability, then rewrites the help.

Have ready: Paste the help output and describe the main workflows

Fill in · 4 fields

PASTE --help OUTPUTTHE 3 MOST COMMON THINGS USERS DO WITH THIS CLIDEVELOPERS / OPS / END USERS, THEIR SKILL LEVELMY DOMAIN

Your prompt

Review my CLI's user experience.

Help output:
[PASTE --help OUTPUT]
Typical workflows: [THE 3 MOST COMMON THINGS USERS DO WITH THIS CLI]
Who uses it: [DEVELOPERS / OPS / END USERS, THEIR SKILL LEVEL]

Audit:
1. First-run experience: can a new user succeed in 60 seconds from the help text alone? What's missing?
2. Command/flag naming: inconsistent verbs? cryptic shorthands? flags that should be subcommands?
3. Error messages: do failures say what went wrong AND what to do next? Quote the worst offender.
4. Dangerous commands: is there confirmation or --dry-run where there should be? Is output machine-parseable where scripts need it (--json)?
5. Progressive disclosure: is the common path simple while power features stay discoverable?

Deliver a rewritten --help text plus the 3 highest-impact UX changes, each with before/after. Compare against one CLI famous for good UX in [MY DOMAIN] and steal its best idea explicitly.

Paste it into Muse or any assistant. Blank fields stay as [brackets].

More like this

Test Pyramid Planner

Dependency Upgrade Plan

Bug Report Formatter

Rollout Planner

Serialization Chooser

Query Plan Explainer