Cli Developer

**Assessment:** This skill is a strong fit whenever you need to design or implement command-line tools with a focus on developer experience, especially in Node.js, Python, or Go. It encodes good practices around UX, performance, and cross-platform compatibility, and is notably more specialized than a generic programming skill. **Strengths** - Optimized for CLI-centric tasks: argument parsing, subcommands, interactive prompts, progress indicators, shell completions. - Explicit attention to performance (startup <50ms), non-blocking I/O, and cross-platform testing. - Emphasizes polished UX: clear help text, consistent flags, early input validation, graceful SIGINT handling. - References concrete ecosystems and libraries, improving the likelihood of practical, implementable suggestions. **Risks / Limitations** - Language scope is focused on Node.js, Python, and Go; value may be lower for other ecosystems (Rust, Java, .NET, etc.). - Performance and robustness are guided by best practices but not empirically verified; generated solutions still need benchmarking and real cross-platform tests. - May not fully account for highly specialized environments (very constrained containers, embedded systems, or unusual terminals) without additional expertise. **Recommended Scenarios** - Designing a new developer-facing CLI or refactoring an existing one for better usability and maintainability. - Adding structured subcommands, configuration loading (files/env/flags), and robust error handling to an existing script or tool. - Implementing interactive workflows, progress feedback, and shell completions for installation, deployment, or developer tooling. - Optimizing startup time and responsiveness of existing Node.js/Python/Go CLIs, especially those used heavily in CI/CD or inner dev loops.