HN Hall of Fame Weekly email

CLI Guidelines – A guide to help you write better command-line programs

Screenshot of clig.dev captured 2026-07-20
Page preview · captured 2026-07-20

Resurfaced independently across 5 calendar years, with breakout response in 2 of them.

submissions
12
submitters
12
observed span
2020–2025
peak thread · 212 comments
564 pts
latest 20+ return · 2024-02-06
341 pts

Submission timeline

2007–2026

One slot for every year since HN launched. Height is that year's peak points; orange marks a 100+ point or 50+ comment breakout. Select a bar to open its strongest thread.

First comments on top threads

HN comment order

Hello HN! We’re Ben, Aanand, Carl, Eva, and Mark, and we made the Command Line Interface Guidelines. Earlier this year, I was working on the Replicate CLI [0]. I had previously worked on Docker so I had a bunch of accumulated knowledge about what makes a good CLI, but I wanted to make Replicate really good, so I looked for some design guides or best practices. Turns out, nothing substantial had been published since the 1980s. On this search I…

bfirsh·564-point thread·

> Most people today don’t know what the command line is, much less why they would want to bother with it. This is true today, and it was true as well "in the 1980s", to use the same time frame as TFA. The difference is that today there are more people than ever who know what the command line is, and who can use it. At least an order of magnitude more people; maybe two. We can certainly say that…

This is actually nice and useful resource for command line UX.

> Don’t bother with man pages. We believe that if you’re following these guidelines for help and documentation, you won’t need man pages. I disagree strongly in all but exceptional cases. These exceptions would still benefit from a bare-bones man page with the most common options and a handful of examples of common usage.

teddyh·19-point thread·

The first top-level comment from each of the four biggest threads, in HN’s own order. Excerpts are shortened; open a comment for full context.

Breakout years
2

100+ points or 50+ comments

Total points
1007

reference only — not used in Hall rules or ranking

Total comments
422

reference only — not used in Hall rules or ranking

Every submission

DateTitle as submittedByPointsComments
2020-12-04CLI Guidelinestodsacerdoti40
2020-12-04CLI Guidelines – A guide to help you write better command-line programsFirst breakout · Best threadbfirsh564212
2020-12-21Command Line Interface Guidelinesgmays195
2022-04-30Command Line Interface GuidelineskyleShropshire50
2022-06-07Command Line Interface Guidelinesmmazzarolo611
2022-11-25Command Line Interface Guidelinesjustanotherdot20
2023-10-28Command Line Interface Guidelinespizza21
2023-11-07Command Line Interface Guidelinesaphrax20
2024-02-06Command line interface guidelines (2021)Hall induction · Latest 20+ point returnpetercooper341201
2025-09-19Command Line Interface GuidelinesNullCascade31
2025-11-05Command Line Interface Guidelinesmooreds30
2025-12-25Command Line Interface Guidelinesvinhnx11