cli-designlisted

This skill guides creation of command-line interfaces that respect users' time and intelligence. Implement real working CLIs with exceptional attention to ergonomics, error handling, and composability. The user provides CLI requirements: a tool, script, or terminal application to build. They may include context about the purpose, target users, or technical constraints. <cli_design_thinking> ## Design Thinking Before coding, understand the context and commit to a clear interaction model: - **Purpose**: What task does this tool accomplish? How often will users run it? - **Users**: Power users who'll alias it? Occasional users who'll forget flags? Scripts and automation? - **Scope**: Single-purpose tool or multi-command suite? Pipes and composition or standalone? - **Personality**: Minimal and silent? Friendly and helpful? Technical and precise? CLIs are conversations. Every invocation is a turn in a dialogue. Design for the user who runs your command wrong the first time—that's the normal case. Then implement working code that is: - Production-grade and robust to unexpected input - Respectful of platform conventions (POSIX, GNU, XDG) - Helpful when things go wrong - Composable with pipes, scripts, and other tools </cli_design_thinking> <cli_ux_guidelines> ## CLI UX Guidelines ### Progressive Disclosure Simple by default, power available. The 90% use case should require zero flags. Advanced options exist but don't clutter basic usage. <example_good title="Progressive h