Document CLI surface area specifications with arguments, flags, and exit codes.
npx skills add https://github.com/ivanov-i/dots --skill create-cli-ivanov-i
Please help me install this Agent Skill. Skill: create-cli Source: https://github.com/ivanov-i/dots/tree/main/codex/skills/create-cli Command: npx skills add https://github.com/ivanov-i/dots --skill create-cli-ivanov-i
Designing CLI parameters and UX: arguments, flags, subcommands, help text, output formats, error messages, exit codes, prompts, config/env precedence, and safe/dry-run behavior. Use when you’re designing a CLI spec (before implementation) or refactoring an existing CLI’s surface area for consistency, composability, and discoverability.
--json/--plain; --quiet/--verbose.--dry-run, confirmations, --force, --no-input.Draft a concise CLI spec for a hypothetical tool and validate it against human-first and script-friendly design criteria.
High-intent search queries and answers about installing and using this skill.
A CLI specification defines arguments, flags, subcommands, help text, and exit codes. It ensures consistency, composability, and discoverability by codifying expected user interactions and safe behaviors like dry-run before implementation begins.
The correct precedence for command-line config is flags overriding environment variables, which override project config, then user config, and finally system config. This hierarchy ensures explicit user inputs take priority over global defaults.
Structure stdout for primary data output using formats like --json or --plain, and reserve stderr for errors and verbose logs. Map top failure modes to specific exit codes so calling scripts can programmatically react to different error states.
Include safety rules like --dry-run for previewing state changes, interactive confirmations for destructive actions, --force to bypass prompts, and --no-input for non-interactive environments. These prevent accidental data loss during command execution.
Yes, this CLI design approach works for drafting a specification for a hypothetical new tool and refactoring an existing command-line interface. It scopes arguments, output rules, and config precedence to improve consistency across both scenarios.
matsuni-kkGather user input and generate a structured requirements.md document for mini-applications.
takuto-tanaka-4digitDesign CLI parameters, flags, subcommands, help text, and exit codes.
aptos-labsValidate Aptos documentation for LLM indexing and SEO compliance.
AdamBienImplement zero-dependency enum-based argument parsing for Java CLI applications.