Stewie Reflect

The owner's manual your vibe-coded codebase never came with

5.0•2 reviews•

25 followers

The owner's manual your vibe-coded codebase never came with

5.0•2 reviews•

25 followers

Visit website

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.

Stewie Reflect Reviews

Name: Stewie Reflect
Rating: 5.0 (2 reviews)

The community submitted 2 reviews to tell us what they like about Stewie Reflect, what Stewie Reflect can do better, and more.

5.0

Based on 2 reviews

Review Stewie Reflect?

Reviews

Most Informative

Founder Reviews

Other Reviews (2)

•4 reviews

What's great

Stewie Reflect writes the manual your code would write. Every codebase has two descriptions: what was intended and what is actually there. Documentation written by humans describes the first and drifts further from the truth with every commit. Reflect generates the second, and because it is built on PBC Spec, the result is audited against the code rather than someone's memory of it.

Two things surprised me. First, the output is genuinely visually appealing, which matters more for a manual than people admit, because a manual nobody wants to open is a manual nobody reads. Second, Reflect delivers a template rather than a finished artifact. The final product is still yours, but you start from an accurate roadmap of what your codebase really is instead of a blank page.

For a beta release it is remarkably polished and was immediately useful. Here is a real manual it produced for one of my own systems:

https://bulkheadtau.com/bulkhead-tau/reflect/operator-control-plane.html

What needs improvement

The initial manual has a mechanical feel to the language. It's pretty easy to smooth out as you are making your revisions, but this could possibly be streamlined in the future.

vs Alternatives

I didn't choose Reflect over alternatives. I chose it because it provided functionality available nowhere else.

PBC Spec filled a real need for me. It gives my system an upper boundary, a spec that is bound to the code instead of floating beside it. Without that, you are really developing 2 systems, the software and a separate description of the software, and keeping them in sync by hand. That's just too much for me, at least.

Stewie Reflect leverages PBC Spec in a way nobody else is positioned to match, since the open-source repo at the core of the product is the company's own.

EDIT: I forgot to mention the first time around that LangChain entered this space about two weeks ago with an open-source repo called OpenWiki — an exciting move from an open-source powerhouse. It has a similar purpose: build the manual from what the code is, rather than from what's wanted from the code. I'm excited about this one too, since it can fill gaps Reflect doesn't cover: namely, simpler repos with less surface area to analyze.

I've since made several PRs against OpenWiki. Where did the ideas come from? From Stewie Reflect's own manual of OpenWiki. That's the power of this approach: it compounds.

Ratings

Ease of use

Reliability

Value for money

Customization

Report

12 views1mo ago

Thank you for the thoughtful review, Erik — really appreciate you testing Reflect deeply and sharing such specific feedback.

Report

1mo ago