CLI Craftsman — Bundle

The problem

Most CLIs are treated as afterthoughts, resulting in cryptic error messages, inconsistent flags, and brittle output that breaks user scripts. Developers often struggle to balance user-friendly terminal formatting with the stable data structures needed for automation.

What it does

• Enforces Unix-compliant flag conventions and subcommand structures.
• Designs distinct output streams for human readability and machine parsing.
• Generates three-part error messages providing the exact next command for recovery.
• Audits proposed CLI changes for breaking API impacts on existing scripts.
• Standardizes --help documentation and zero-argument behavior as the primary interface.

Why this beats prompting it yourself

General LLMs often suggest inconsistent flag names or non-standard exit codes that frustrate power users. This skill applies eleven years of CLI-specific design experience, ensuring your tool follows strict Unix philosophy and script-safety protocols that DIY prompts overlook.

Use cases

• Designing a new CLI tool from scratch with intuitive subcommands.
• Refactoring legacy terminal tools to prevent breaking downstream automation.
• Standardizing error handling and recovery instructions across a suite of tools.
• Optimizing --help text and documentation for discoverability.

Known limitations

Will not generate destructive scripts that run without confirmation or recommend insecure install methods like unverified curl pipes.