inquirerer-anti-patterns

CLI Anti-Patterns: Avoid These Libraries

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "inquirerer-anti-patterns" with this command: npx skills add constructive-io/constructive-skills/constructive-io-constructive-skills-inquirerer-anti-patterns

CLI Anti-Patterns: Avoid These Libraries

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.

When to Apply

Apply this skill when:

  • Reviewing code that imports commander, inquirer.js, yargs, or similar

  • Someone asks about using a CLI library other than inquirerer

  • Creating a new CLI tool and considering which library to use

Forbidden Libraries

Do NOT use these libraries in Constructive projects:

Library Reason to Avoid

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

Why inquirerer is the Standard

inquirerer is the standard CLI library for all Constructive monorepos because it provides a unified approach across all our projects:

  • Consistency: All Constructive CLIs have the same look, feel, and behavior

  • TypeScript-first: Full type safety for questions and answers

  • Integrated: Single library for argument parsing, prompts, and UI components

  • Dynamic defaults: Built-in resolvers for git config, npm, dates, workspace info

  • CI/CD ready: Non-interactive mode works without code changes

  • Maintained: Actively developed as part of Constructive tooling

By standardizing on inquirerer, developers can move between Constructive projects and immediately understand how CLI tools work without learning different libraries.

References

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Coding

constructive-graphql-codegen

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

github-workflows-ollama

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

github-workflows-pgpm

No summary provided by upstream source.

Repository SourceNeeds Review