Design command-line interface parameters and UX specifications for CLI tools.
npx skills add https://github.com/d3ming/dot-agents --skill create-cli-d3ming
Please help me install this Agent Skill. Skill: create-cli Source: https://github.com/d3ming/dot-agents/tree/main/master/skills/create-cli Command: npx skills add https://github.com/d3ming/dot-agents --skill create-cli-d3ming
Designing command-line interfaces is often inconsistent, unclear, or unfit for both humans and automation; this Skill provides a disciplined rubric to define arguments, flags, subcommands, help, output formats, error handling, and configuration precedence before implementation to avoid costly UX and automation regressions.
Design a CLI spec for a command named mycmd that includes a usage line, subcommands with clear semantics, an args and flags table (types and defaults), --json output mode, config precedence rules, safety flags like --dry-run and --force, and five example invocations.
High-intent search queries and answers about installing and using this skill.
Designing a command-line interface specification involves defining the command tree, usage synopsis, args/flags tables, and subcommand semantics upfront. This approach produces a compact, implementable spec that prevents costly UX and automation regressions before writing any code.
Standard config precedence for CLI tools follows a strict hierarchy: flags override environment variables, which override project, user, and system configurations. Establishing this precedence ensures consistent behavior across interactive terminals and CI automation systems.
Structuring stdout, stderr, and exit codes requires defining clear I/O and error contracts. You should separate stdout for data output from stderr for diagnostics, implement JSON/plain modes, and specify exit codes suitable for both interactive use and scripting.
Safety flags for command-line interfaces should include dry-run and force semantics, alongside specific prompt behaviors. Defining these rules ensures your CLI operates safely across interactive terminals and automated CI systems without unintended side effects.
Yes, you can apply this CLI design rubric to refactor existing command surfaces. It helps standardize inconsistent interfaces by redefining arguments, flags, subcommands, and error contracts into a clear, implementable specification for humans and automation.
You need a formal CLI specification when creating a new tool interface or standardizing UX across an organization. Producing a command tree, usage synopsis, and example invocations ensures your command-line interface remains discoverable, scriptable, and consistent.
michalvavraDesign CLI interfaces with arguments, flags, help text, and output modes.
timbrindedAnalyze UI designs and frontend code for hierarchy, spacing, typography, and color issues.
arbazkhan971Scaffold command-line applications with argument parsing and shell completions.
89jobrienIdentify and resolve CLI command design inefficiencies across projects.
