Can I vibe code Scribe?
Turns any click-through into step-by-step documentation.
The trick behind Scribe is a browser extension listening for clicks: on each one, grab a screenshot, note the element's label, and append 'Step 3: Click Save'. That capture-to-doc loop is genuinely buildable in a sitting, and for documenting your own processes it works. The 'kinda' is everything that makes docs shareable at work — automatic redaction of sensitive fields, hosted guides with permissions, team libraries, desktop capture. You get a Markdown generator; they sell a documentation platform.
Build a Chrome extension (Manifest V3) that turns a browser click-through into step-by-step documentation. On 'record', listen for clicks and inputs; for each step capture a screenshot via chrome.tabs.captureVisibleTab, the element's accessible name, and the page URL; draw a highlight circle where I clicked. On 'stop', open an editor page where I can retitle steps, delete noise, and add notes, then export Markdown (screenshots embedded) and a single-file HTML guide. Store sessions in IndexedDB — no server needed. Include a mask tool to black out regions before export.
A Chrome extension that records a click-through — screenshot plus element label per step — and exports a numbered, editable guide as Markdown or HTML.
- Automatic blurring of emails, names, and other sensitive pixels
- Hosted guides with share links, permissions, and view analytics
- A team library where docs stay organized and updatable
- Desktop-app capture beyond the browser
Companies pay because a guide's value is mostly in the sharing — hosted links, redaction they can trust, and one library the whole team updates.
A prompt is the first move, not the whole game. Course 01 teaches you to take a prompt like this one to a shipped, working app — reviewing, correcting, and steering the agent the whole way.
Start Course 01 →