Documentation finally caught up with vibe coding

Introducing SuperDocs

I’m launching SuperDocs today.

Not because the world needed another docs tool.
But because the way we build has changed, and documentation never caught up.

Most of my recent products were vibe coded. Fast iterations. Messy thinking. Decisions made late at night, written down quickly in markdown files sitting close to the codebase.

The problem was never writing docs.
The problem was using them.

Searching through READMEs, notes, comments, and half-finished explanations broke flow every single time. Context switching slowed everything down.

So I built SuperDocs.

You keep writing docs exactly how you already do.
Markdown, folders, chaos — whatever works.

SuperDocs just sits on top and lets you talk to your documentation.

Ask why something exists.
Ask how a part of the system works.
Ask where you explained a decision weeks ago.

No workflows. No migrations. No setup rituals.

The goal was simple: docs should help you move faster, not slow you down.

I shared an early version casually on Reddit.
That post unexpectedly went viral and brought in the first 50 users.

I don’t want to open this up too fast.

So I’m keeping the next 50 spots only for Substack readers.

Below is a short demo showing how SuperDocs fits into my actual workflow. Nothing polished. Just how I use it while building.

If you’re a builder who ships early, thinks out loud in docs, and hates heavy tooling, this is probably for you.

If you try it and want to talk, I’m very accessible.

You can book time with me anytime.
You can DM me on X.
You can also join me 1:1 on Slack or Discord.

This is early. Feedback matters more than growth right now.

—
Udit