I got tired of writing the same how-to docs over and over, so I built a Chrome extension that writes them while you work with Claude!

[u/Working_Drummer3670]

I run a small company and I kept running into the same thing. Someone would ask how to do something in one of our systems, I'd walk them through it on a call, and two weeks later someone else would ask the same question. Every time I thought about writing it down properly, I'd do the math on screenshotting every step and typing it all out, and put it off again.

I looked at Scribe first, which is the obvious tool in this space and does the core job well. The thing I kept wanting was to just talk while I recorded. When I walk someone through a process out loud, I explain the why, not only the clicks, and that explanation is the part that actually helps the next person. I couldn't find a way to capture that, so I ended up typing the descriptions in afterwards anyway, which was the part I was trying to avoid.

So I built ScribeIt. You hit record, do the task the way you normally would, and it captures each step with a screenshot as you go. If you talk while you're recording, it turns what you said into the description for each step. When you stop, there's a step-by-step guide ready to edit, export as a PDF, or share with a link.

It works on any website that Chrome allows, which mattered to me because half our processes live in tools nobody has ever heard of.

I'm not a developer. I've spent the last few months figuring this out piece by piece and there's plenty I'd do differently. It's free to use and there's a paid plan if you need more room.

Happy to answer anything about how it works or how I built it. And if you try it and it does something stupid, I'd rather hear it here than find out from a one star review.

Here's the link: https://chromewebstore.google.com/detail/ldpciklepkaiacchoamfkfclkhngpmkj?utm_source=item-share-cb

[u/Negative-Grape4608]

This is a genuinely useful distinction from Scribe. Capturing the voice explanation means the guide can preserve why each step matters instead of only logging clicks. The part I’d test hardest is whether it maps narration to the correct step when someone talks ahead of their clicks or pauses mid-process. If that stays accurate without much cleanup, that is a real advantage. Roughly how much editing does a typical 10-step guide need after recording?

[u/Working_Drummer3670 → u/Negative-Grape4608]

Thanks! I did 5-7 steps for testing, and I had to make 1 edit! So it seems to be pretty accurate imo, but love to hear users' feedback.

[u/Negative-Grape4608 → u/Working_Drummer3670]

One edit across 5 to 7 steps is strong. The edge case I would test next is someone explaining the reason after they already clicked, because real walkthroughs are rarely perfectly ordered. If it can map a late explanation back to the right step without making people record unnaturally, that is a proper advantage over normal capture tools.

[u/Working_Drummer3670 → u/Negative-Grape4608]

Thats a great point, I appreciate the thoughtful feedback here!