Launching today
Stewie Reflect
The owner's manual your vibe-coded codebase never came with
14 followers
The owner's manual your vibe-coded codebase never came with
14 followers
Stewie Reflect reads a read-only snapshot of your GitHub repo and generates an Owner's Manual for the product inside it: what the code does, where the evidence ends, and which decisions only you can make. Every claim is tied back to the file or function that supports it, with plain-language diagrams so the manual is readable, not just technical. Pick a repo and branch to get a free preview — a full chapter plus a map — then unlock the full manual and Markdown export for a $19 beta price.
Grass
oh this is a good one. half the designers using Maker end up with working code they couldn't really explain out loud, so this anxiety is dead on. does it document what's already there or does it want to ride along from the start?
@sunnyjoshi Thanks! That was exactly the problem I built it for.
Right now it documents what’s already there. You point it at a repo snapshot, it reconstructs what the product actually does from the code and generates an evidence-backed owner’s manual.
Having it ride along during development is something I’m actively thinking about, but I wanted to solve the “I already shipped this—now help me understand it” problem first.
Curious how it handles monorepos with multiple services, does it try to summarize everything together or let me pick which subfolder gets its own manual?
how does it handle monorepos with multiple services sharing one repo, does the manual get split per package or stay as one big doc
the traceability thing is really well done, every claim links straight back to the file it came from so you can actually trust what the manual is telling you instead of taking it on faith.
If you'd like to see what the output actually looks like before trying it, here's a public sample manual generated from a real AI bookkeeping app:
https://reflect.stewie.sh/#/manual
No signup required.