Show HN: Shotlist – Make your AI agent prove its work with real screenshots
shotlist Screenshots for your docs — as code. One committed shot list captures your web pages, your real terminal windows, and stateful CLI sessions — and regenerates them all with a single command. The screenshots drift out of date the moment you ship, and nobody notices until they're embarrassingly wrong. shotlist makes them reproducible: describe how to start your app and what to shoot once, in a committed .shotlist.yaml, then regenerate the whole set on demand — locally or in CI.
- ▪shotlist Screenshots for your docs — as code.
- ▪One committed shot list captures your web pages, your real terminal windows, and stateful CLI sessions — and regenerates them all with a single command.
- ▪The screenshots drift out of date the moment you ship, and nobody notices until they're embarrassingly wrong. shotlist makes them reproducible: describe how to start your app and what to shoot once, in a committed .shotlist.yaml, then regen
Opening excerpt (first ~120 words) tap to expand
shotlist Screenshots for your docs — as code. One committed shot list captures your web pages, your real terminal windows, and stateful CLI sessions — and regenerates them all with a single command. Contents The problem Quickstart One shot list, four kinds of shot Use cases Proof reports & pipelines Why shotlist, and not the others How it works Use with Claude Commands Develop The problem Documenting a feature means launching the app, clicking to the right state, screenshotting, naming the file, and embedding it — every time the UI changes. The screenshots drift out of date the moment you ship, and nobody notices until they're embarrassingly wrong.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.