Anti-patterns for CLI development. Do NOT use commander, inquirer.js, yargs, or other CLI libraries in Constructive projects. Use inquirerer instead. Triggers on "commander", "inquirer.js", "yargs", "CLI library", or when reviewing CLI code.
Quickly install inquirerer-anti-patterns AI skill to your development environment via command line
Source: constructive-io/constructive-skills.
This skill defines what NOT to do when building CLI tools in Constructive projects. All CLI development should use inquirerer instead of other CLI libraries.
| commander | Separate argument parsing, no integrated prompts | | inquirer / inquirer.js | Outdated, not TypeScript-first, different API | | yargs | Complex API, no integrated prompts | | prompts | Limited features, no resolver system | | enquirer | Different API, no Constructive integration | | vorpal | Unmaintained, complex |
| oclif | Heavyweight framework, overkill for most uses | | meow | Minimal, no prompt support | | arg | Argument parsing only | | minimist (directly) | Use inquirerer's parseArgv wrapper instead | | ora | Use inquirerer's createSpinner instead | | cli-progress | Use inquirerer's createProgress instead |
Stable fields and commands for AI/search citations.
npx skills add https://github.com/constructive-io/constructive-skills --skill inquirerer-anti-patternsAnti-patterns for CLI development. Do NOT use commander, inquirer.js, yargs, or other CLI libraries in Constructive projects. Use inquirerer instead. Triggers on "commander", "inquirer.js", "yargs", "CLI library", or when reviewing CLI code. Source: constructive-io/constructive-skills.
Open your terminal or command line tool (Terminal, iTerm, Windows Terminal, etc.) Copy and run this command: npx skills add https://github.com/constructive-io/constructive-skills --skill inquirerer-anti-patterns Once installed, the skill will be automatically configured in your AI coding environment and ready to use in Claude Code, Cursor, or OpenClaw
https://github.com/constructive-io/constructive-skills