01Draw on the live page
Drop the bookmarklet on any URL — staging, production, localhost. Click an element to pin it, or scribble freehand around whatever looks wrong. The overlay runs in its own transparent layer, so your app keeps its pixels, its styles, and its listeners.
tool · pick · draw · note02Anchors, not CSS strings
Insofar remembers where an element lives — tag, attributes, text, landmarks — and re-finds it after the redesign. When it can't, it nudges: re-anchor? A pin is never silently lost. (The pins on this page track their elements while you scroll — that's this, live.)
anchor · structural · re-match scored03Talk where the bug lives
The thread hangs on the element itself — not in a tracker three tools away. Say what's wrong, propose the fix, reply in place. The whole conversation lands in the packet verbatim.
thread · on the pin · in the packet04The prompt packet is the product
Everything lands in one self-contained paste: instruction verbatim, URL + viewport, DOM + computed styles, screenshot, thread, trail. Markdown for humans, rich HTML for docs, JSON for agents. Change only what is asked — no clarifying question required.
packet · markdown · html · json05Propose the fix, don't describe it
Recolor the button, rewrite the label, hide the banner — the overlay paints a watermarked draft on the real page. Before/after goes into the packet with generated CSS, and one click reverts.
draft · watermarked · revertible06The trail keeps receipts
Status, PR and commit links, every message, every decision — append-only. What shipped, who asked for it, why it looks like that now. Months later, the answer is still on the element.
trail · status · links · history