Skip to main content
NEW · APP STORE Now on iOS · macOS · iPad Android & Windows soon GET IT
Prompts CLI Project Tooling Standards Guide

developer coding developer risk: low

CLI Project Tooling Standards Guide

Lists specific tools such as pnpm, TypeScript, tsup, vitest, Commander.js, clack, ora, picocolors, and Ink for CLI projects along with practices like command organization, ASCII ar…

PROMPT 

# Cli taste of AA
- Use pnpm as the package manager for CLI projects. Confidence: 1.00
- Use TypeScript for CLI projects. Confidence: 0.95
- Use tsup as the build tool for CLI projects. Confidence: 0.95
- Use vitest for testing CLI projects. Confidence: 0.95
- Use Commander.js for CLI command handling. Confidence: 0.95
- Use clack for interactive user input in CLI projects. Confidence: 0.95
- Check for existing CLI name conflicts before running npm link. Confidence: 0.95
- Organize CLI commands in a dedicated commands folder with each module separated. Confidence: 0.95
- Include a small 150px ASCII art welcome banner displaying the CLI name. Confidence: 0.95
- Use lowercase flags for version and help commands (-v, --version, -h, --help). Confidence: 0.85
- Start projects with version 0.0.1 instead of 1.0.0. Confidence: 0.85
- Version command should output only the version number with no ASCII art, banner, or additional information. Confidence: 0.90
- Read CLI version from package.json instead of hardcoding it in the source code. Confidence: 0.75
- Always use ora for loading spinners in CLI projects. Confidence: 0.95
- Use picocolors for terminal string coloring in CLI projects. Confidence: 0.90
- Use Ink for building interactive CLI UIs in CommandCode projects. Confidence: 0.80
- Use ink-spinner for loading animations in Ink-based CLIs. Confidence: 0.70
- Hide internal flags from help: .addOption(new Option('--local').hideHelp()). Confidence: 0.90
- Use pnpm.onlyBuiltDependencies in package.json to pre-approve native binary builds. Confidence: 0.60
- Use ANSI Shadow font for ASCII art at large terminal widths and ANSI Compact for small widths. Confidence: 0.85
- Use minimal white, gray, and black colors for ASCII art banners. Confidence: 0.85
- Check if package is publishable using `npx can-i-publish` before building or publishing. Confidence: 0.85

ROLES & RULES

  1. Use pnpm as the package manager for CLI projects.
  2. Use TypeScript for CLI projects.
  3. Use tsup as the build tool for CLI projects.
  4. Use vitest for testing CLI projects.
  5. Use Commander.js for CLI command handling.
  6. Use clack for interactive user input in CLI projects.
  7. Check for existing CLI name conflicts before running npm link.
  8. Organize CLI commands in a dedicated commands folder with each module separated.
  9. Include a small 150px ASCII art welcome banner displaying the CLI name.
  10. Use lowercase flags for version and help commands (-v, --version, -h, --help).
  11. Start projects with version 0.0.1 instead of 1.0.0.
  12. Version command should output only the version number with no ASCII art, banner, or additional information.
  13. Read CLI version from package.json instead of hardcoding it in the source code.
  14. Always use ora for loading spinners in CLI projects.
  15. Use picocolors for terminal string coloring in CLI projects.
  16. Use Ink for building interactive CLI UIs in CommandCode projects.
  17. Use ink-spinner for loading animations in Ink-based CLIs.
  18. Hide internal flags from help: .addOption(new Option('--local').hideHelp()).
  19. Use pnpm.onlyBuiltDependencies in package.json to pre-approve native binary builds.
  20. Use ANSI Shadow font for ASCII art at large terminal widths and ANSI Compact for small widths.
  21. Use minimal white, gray, and black colors for ASCII art banners.
  22. Check if package is publishable using `npx can-i-publish` before building or publishing.

EXPECTED OUTPUT

Format
bullet_list

CAVEATS

Missing context
  • Explicit purpose or task (e.g., 'Use these when generating a CLI project').
  • Input/output formats if for code generation.
  • Handling of confidence scores (e.g., only apply high-confidence rules).
Ambiguities
  • Unclear what 'Cli taste of AA' or 'AA' refers to.
  • 'CommandCode projects' is undefined or specific without context.

QUALITY

OVERALL
0.85
CLARITY
0.95
SPECIFICITY
0.95
REUSABILITY
0.85
COMPLETENESS
0.65

IMPROVEMENT SUGGESTIONS

  • Add introductory sentence: 'Strictly follow these preferences when scaffolding or building CLI projects.'
  • Define or remove undefined terms like 'CommandCode' and 'AA'.
  • Group rules into categories (e.g., Tools, UI, Build) for better scannability.
  • Specify how to prioritize or use confidence scores.

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.

MORE FOR DEVELOPER