Hey, we've been building Nimbrook since August and it went live this week, so any feedback would be asome. The problem: documenting an app/system means screenshot, crop, arrow, paste, write, repeat. Then the UI changes and you start again. So the manual never gets written and someone keeps answering the same questions. How it works: 1. Start the recorder and use your app as usual. Every click becomes a step, captured just before you press, with the element highlighted and the crop centred on it. Passwords are never stored. 2. Review the steps and publish. AI writes the text for each step. It's optional: without it, the manual arrives with empty descriptions. 3. Change whatever you want. The editor is A4 sheets, exactly as they'll print. Rewrite text, move the crop (the full screenshot stays underneath), add arrows, rings and numbers, reorder steps. 4. Export to PDF, PowerPoint, Word or Markdown, or publish a web page anyone can read without an account. A few other things: • You can translate a manual, and readers are always free. • For developers, a Claude Code skill can walk the flow and publish the manual through an API. It can also fix one step: "step 17 of 21 is wrong". • It runs on EU hosting, or on your own servers if your screenshots can't leave the building. If you try it on a real flow, tell me where it fell short. What did you have to fix by hand, and what would stop you using it again? https://nimbrook.com   submitted by   /u/Embarrassed-Ebb-740 [link]   [comments]