This covers the full lifecycle of building command-line tools: argument parsing with libraries like Commander.js and Click, writing help text that actually answers questions, adding interactive prompts that respect non-TTY environments, managing config file hierarchies across system/user/project layers, and distributing via npm/pip/cargo. It's opinionated about POSIX conventions and the principle of least surprise. Use it when you're building a new CLI, adding subcommands, or trying to figure out why your tool feels clunky compared to Git or Kubectl. The config hierarchy section alone (defaults to system to user to project to env to flags) will save you from reinventing that wheel badly.
npx -y skills add absolutelyskilled/absolutelyskilled --skill cli-design --agent claude-codeInstalls into .claude/skills of the current project.
Select a file.
leonxlnx/taste-skill
supercent-io/skills-template
supercent-io/skills-template