Updated August 17, 2026

A gallery of capture workflows, not stock mockups

The gallery is an evidence surface. Each future item should be a real PNG or MP4 with a stable caption, alt text, and the workflow that produced it.

What belongs here

AI bug reports with a focused region and a readable arrow or callout.
Pull-request or changelog visuals with a clear framing choice.
Terminal and browser captures that show exactly what a model or teammate needs.
Shader-backed stills and recordings with the source format and compatibility boundary stated.

1
Capture a real output
Use a current app build and record the scope, format, and date. Keep raw media separate from its optional sidecar.
2
Describe it accessibly
Add descriptive alt text, a stable title, and a caption that explains the workflow rather than only the colors.
3
Disclose synthetic UI
If a screenshot is illustrative, say so next to the visual. Never present a billing card, customer record, or product integration as live evidence when it is not.

Capture a precise UI state, add only the visual context that helps, and paste into Claude Code, Codex, ChatGPT, Cursor, or a browser assistant.

Turn a visual regression into a reproducible bug report with a focused capture, one annotation, and a privacy check before sharing.

Frame stills and MP4 recordings with compiled GLSL, not another static gradient-only screenshot beautifier.