CLI Style Guide
Be mindful of dependencies. The plugin architecture allows you to install any npm package to your plugin but this comes with some cost and potential hazards.
CLI Style Guide Table of Contents [expand] Mission statement Naming the command Description Input Output Colors Human-readable output vs machine-readable output Stdout/Stderr Dependency guidelines Last updated January 31, 2025 Heroku CLI plugins should provide a clear user experience, targeted primarily for human readability and usability, which delights the user, while at the same time supporting advanced users and output formats. This article provides a clear direction for designing delightful CLI plugins. Mission statement The Heroku CLI is for humans before machines. The primary goal of an
Explore this link on the map →saved by
related reading
- Command Line Interface Guidelinesclig.dev
- Command-line usability: A terminal user’s thought process | Ubuntuubuntu.com
- Best practices for Claude Code - Claude Code Docsanthropic.com
- Mercurymercuryos.com
- Impeccable: The missing upgrade to Anthropic's impeccable skillimpeccable.style
- Web Interface Guidelinesvercel.com
- Claude Code Cheat Sheetcc.storyfox.cz
- GitHub - nikivdev/go: Go tools, libraries · GitHubgithub.com
- GitHub - jlevy/the-art-of-command-line: Master the command line, in one page · GitHubgithub.com
- GitHub - alebcay/awesome-shell: A curated list of awesome command-line frameworks, toolkits, guides and gizmos. Inspired by awesome-php. · GitHubgithub.com
- My Heroku values · GitHubgist.github.com
- Realtime Colorsrealtimecolors.com