Skip to content

BumpyClock/agent-templates / skills_archive/create-cli

create-cli

Unverified

CLI UX/spec: args, flags, help, output, errors, config, dry-run.

Create CLI

Design CLI surface area (syntax + behavior), human-first, script-friendly. For rich cli/tui apps read skills/create-cli/references/opentui/SKILL.md and related files.

Do This First

Clarify (fast)

Ask, then proceed with best-guess defaults if unsure:

  • Command name + one-sentence purpose
  • Primary user: humans, scripts, or both
  • Input sources: args vs stdin; files vs URLs; secrets (never via flags)
  • Output contract: human text, --json, --plain, exit codes
  • Interactivity: prompts allowed? need --no-input? confirmations for destructive ops?
  • Config model: flags/env/config-file; precedence; XDG vs repo-local
  • Platform/runtime: macOS/Linux/Windows; single binary vs runtime

Deliverables

Produce compact spec:

  • Command tree + USAGE synopsis
  • Args/flags table (types, defaults, required/optional, examples)
  • Subcommand semantics (what each does; idempotence; state changes)
  • Output rules: stdout vs stderr; TTY detection; --json/--plain; --quiet/--verbose
  • Error + exit code map (top failure modes)
  • Safety rules: --dry-run, confirmations, --force, --no-input
  • Config/env rules + precedence (flags > env > project config > user config > system)
  • Shell completion story (if relevant): install/discoverability; generation command or bundled scripts
  • 5–10 example invocations (common flows; include piped/stdin)

Default Conventions (unless user overrides)

  • -h/--help always shows help, ignores other args
  • --version prints version to stdout
  • Primary data → stdout; diagnostics/errors → stderr
  • --json for machine output; consider --plain for stable line-based text
  • Prompts only when stdin is TTY; --no-input disables prompts
  • Destructive ops: interactive confirmation + non-interactive requires --force or --confirm=...
  • Respect NO_COLOR, TERM=dumb; provide --no-color
  • Handle Ctrl-C: exit fast; bounded cleanup; crash-only when possible

Template: CLI Spec Skeleton

Fill sections, drop irrelevant:

  1. Name: mycmd
  2. One-liner: ...
  3. USAGE: mycmd [global flags] <subcommand> [args]
  4. Subcommands: mycmd init ... / mycmd run ...
  5. Global flags: -h, --help / --version / -q, --quiet / -v, --verbose / --json / --plain
  6. I/O contract: stdout: / stderr:
  7. Exit codes: 0 success / 1 generic failure / 2 invalid usage
  8. Env/config: env vars / config file path + precedence
  9. Examples

Notes

  • Recommend parsing library only when asked; otherwise keep language-agnostic
  • "Design parameters" request → don't drift into implementation
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 318kUpdated Claude CodeCodexUnverifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 196kUpdated Claude CodeCodexVerifiedInstall