Can a prompt replace Zight?

Build a capture tool whose single design target is the time between the keystroke and a working link on the clipboard.

Capture: global shortcuts for region screenshot, window screenshot, full screen, screen recording to MP4, and screen recording to GIF. Region selection with a crosshair, dimension readout, and snapping to window edges. Recording with a visible indicator and a stop shortcut.

The fast path, which is the point of this build:

1. On capture, immediately generate a short unguessable id and write the link to the clipboard. The user can paste before the file exists.
2. Show a small unobtrusive confirmation that the link is copied and the upload is in progress, with progress and a cancel.
3. Upload in the background to object storage. On completion, the link resolves to the file.
4. If the link is opened before the upload finishes, serve a page that says the capture is still uploading and refreshes itself — never a 404, because a 404 trains people to wait before pasting, which defeats the whole design.
5. On upload failure, keep the file locally, mark the link as failed, and retry with backoff. Tell the user clearly rather than leaving a dead link in someone's ticket.

Measure and display the median time from keystroke to clipboard in the tool's own settings. If it is above about 300 milliseconds, the design goal is not met and the number should be visible rather than assumed.

Annotation, kept fast: after a screenshot, a lightweight editor with arrow, rectangle, highlight, text, step numbers, blur and crop. It opens instantly with the link already copied, so annotating is optional and never blocks sharing. Re-uploading after an edit replaces the file behind the same link.

Blur: a one-click blur over a selected region, and a per-capture pass that offers to blur anything matching an email or long-digit pattern found by local OCR. Screenshots leak more than people expect.

Hosting side: a small server issuing ids, accepting uploads, and serving files with correct content types and cache headers. Links are unguessable and optionally expiring; a per-capture setting can require a password. A library page listing your captures with search by date and filename, delete, and a storage total.

Retention: a configurable policy — never delete, or delete after N days — with a warning that deleting removes links already shared. Show storage used and estimated monthly cost.

Out of scope: viewer analytics, team accounts and shared libraries, integrations with other tools, and mobile capture.