원클릭으로 Manus에서 모든 스킬 실행

시작하기

cli

스타7

포크0

업데이트2026년 3월 21일 04:24

When creating Node.js/TypeScript CLI tools

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

nazozokc

nazozokc/dotfiles

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

CLI Tool Development Guidelines

When to Use

When building command-line tools in TypeScript/Node.js
When setting up CLI scaffolding with commander/yargs
When adding CLI-specific features (completion, prompts, error handling)

Basic Rules

Use commander or yargs: Prefer commander for simple CLIs, yargs for complex ones
TypeScript first: Always use TypeScript with strict mode
Exit codes: Use proper exit codes (0 for success, 1 for errors, 2 for invalid args)
No interactive by default: CLI tools should be non-interactive unless explicitly requested

Project-Specific Patterns

Storage: prefer JSON files under ~/.local/share/<tool-name>/ for persistent data
External tools: integrate with fzf for selection UIs, nvim for editing flows
Packaging: every CLI tool must have a Nix flake — see ../nix/SKILL.md
Output: default to clean stdout; use stderr for errors and progress

User Experience

Clear error messages: Show helpful error messages with actionable solutions
Progress indicators: Use ora for long-running operations
Interactive prompts: Use inquirer when user input is required
Color output: Use chalk or kleur for meaningful color coding
Verbose mode: Support --verbose flag for detailed logging

Build & Deployment

Bin field: Set bin field in package.json for CLI entry point
** shebang**: Use #!/usr/bin/env node in entry file
ESM support: Include "type": "module" for ESM support
Cross-platform: Avoid platform-specific commands unless necessary
Version bumping: Use version command or automated versioning
After build, verify the binary works via nix run .#<tool> if a flake is present

File Structure

cli/
├── src/
│   ├── index.ts      # Entry point
│   ├── commands/     # Command definitions
│   ├── utils/        # Helper functions
│   └── types.ts      # Shared types
├── package.json
└── README.md

Commands to Verify

Run tsc --noEmit to check types
Run npm run build before publishing
Test with npm link locally

Related Skills

For general code generation, see ../code-gen/SKILL.md
For TypeScript rules, see ../typescript/SKILL.md
For Nix packaging, see ../nix/SKILL.md

이 저장소의 다른 Skills

같은 저장소

merge-main

nazozokc/dotfiles

Use this skill whenever the user wants to merge the main branch into their current branch. Triggers include phrases like "merge main", "mainをマージ", "mainを取り込む", "mainに追従", "sync with main", "mainの変更を取り込みたい", or any request to bring changes from main into a feature/working branch. Always use this skill — do not improvise git commands without it.

2026-03-307

skills-creator

nazozokc/dotfiles

Template and notes when creating or updating SKILL.md files under skills/

2026-03-307

code-review

nazozokc/dotfiles

Perspectives and rules when conducting a code review

2026-03-217

create-pr

nazozokc/dotfiles

Template, notes, and procedure when creating a Pull Request

2026-03-217

git-commit

nazozokc/dotfiles

Rules for Git commits, pushes, and PR creation

2026-03-217

github-actions

nazozokc/dotfiles

When creating, editing, or debugging GitHub Actions workflow YAML files

2026-03-217

CLI Tool Development Guidelines

When to Use

When building command-line tools in TypeScript/Node.js

When setting up CLI scaffolding with commander/yargs

When adding CLI-specific features (completion, prompts, error handling)

Basic Rules

Use commander or yargs: Prefer commander for simple CLIs, yargs for complex ones

TypeScript first: Always use TypeScript with strict mode

Exit codes: Use proper exit codes (0 for success, 1 for errors, 2 for invalid args)

No interactive by default: CLI tools should be non-interactive unless explicitly requested

Project-Specific Patterns

Storage: prefer JSON files under ~/.local/share/<tool-name>/ for persistent data

External tools: integrate with fzf for selection UIs, nvim for editing flows

Packaging: every CLI tool must have a Nix flake — see ../nix/SKILL.md

Output: default to clean stdout; use stderr for errors and progress

User Experience

Clear error messages: Show helpful error messages with actionable solutions

Progress indicators: Use ora for long-running operations

Interactive prompts: Use inquirer when user input is required

Color output: Use chalk or kleur for meaningful color coding

Verbose mode: Support --verbose flag for detailed logging

Build & Deployment

Bin field: Set bin field in package.json for CLI entry point

** shebang**: Use #!/usr/bin/env node in entry file

ESM support: Include "type": "module" for ESM support

Cross-platform: Avoid platform-specific commands unless necessary

Version bumping: Use version command or automated versioning

After build, verify the binary works via nix run .#<tool> if a flake is present

File Structure

cli/ ├── src/ │ ├── index.ts # Entry point │ ├── commands/ # Command definitions │ ├── utils/ # Helper functions │ └── types.ts # Shared types ├── package.json └── README.md

Commands to Verify

Run tsc --noEmit to check types

Run npm run build before publishing

Test with npm link locally

Related Skills

For general code generation, see ../code-gen/SKILL.md

For TypeScript rules, see ../typescript/SKILL.md

For Nix packaging, see ../nix/SKILL.md

name	cli
description	When creating Node.js/TypeScript CLI tools