Explain My BuildHow to document an app you built with Claude Code
Last updated: July 26, 2026
To document an app built with Claude Code, point Explain My Build at your repo or local folder. Claude Code works in your terminal, so you already have a real git repo. It reads the code and writes an end-user guide, a founder runbook and a code-verified fix-list, each claim cited to a real file.
What is Claude Code, and what do you already have?
Claude Code is Anthropic's agentic coding tool that runs in your terminal. You run it in a project directory, describe what you want, and it reads your codebase and does the work — across files, running tests, and committing results. Claude Code-specific facts:
- You already have a real git repo. Claude Code works on files on your own machine, typically under version control — there's no proprietary project to export.
- It's agentic and multi-file. It plans an approach, then writes and modifies code across many files at once, so a single request can create features spread throughout your project.
- It's stack-agnostic. Claude Code isn't tied to one framework — your app could be a web app, an API, a CLI or something else — so documentation has to read whatever is actually there.
Because you have a normal repo, documenting a Claude Code app is straightforward: point Explain My Build at the folder and it reads what Claude Code built.
Why document an agentically-built app from code?
When an app is built agentically, features get created in one flow across files you may never open, so reading the code is the only complete way to know what your app actually does. Explain My Build maps every route, command, data model and integration from the real source Claude Code wrote.
This matters most for two audiences. Your users need a plain-English end-user guide to the features they touch. And you need a founder runbook to operate and extend an app whose internals you didn't write by hand. A screen recording can't give you either, because it only sees the screens you click — not the backend Claude Code built. See end-user guide vs developer docs.
What three artifacts do you get for a Claude Code app?
From one read of your Claude Code repo you get:
- End-user guide — plain-English help for your users, with share link and access code, in-app Help widget and portable export. $19/month ($12/month founding for the first 100).
- Founder runbook — how the app is structured and how to run and extend it. Free.
- Code-verified fix-list — ranked, cited issues you can hand straight back to Claude Code in your terminal to fix, closing the loop in the same tool. Free.
An honest note
Your Claude Code repo is already local, so you can run Explain My Build on it entirely in your browser or via the CLI — the code never leaves your machine, which suits private projects. It reads code; it is not a live penetration test, and you review the end-user guide before publishing.
Frequently asked questions
How do I document an app I built with Claude Code?
Point Explain My Build at your git repo or local folder — Claude Code already gave you real code on your machine. It reads the source (including the multi-file features Claude Code built agentically) and writes an end-user guide, a founder runbook and a code-verified fix-list. You review the guide before publishing.
Claude Code built features across my whole repo — can I document them all?
Yes. Reading the code covers every feature Claude Code generated, wherever it lives, including files you never opened. You don't need to understand the code first — the tool explains it in plain English and cites where each claim comes from.
Can I keep my Claude Code project private while documenting it?
Yes. Because your repo is local, you can run Explain My Build entirely in your browser or via the CLI, so the code never leaves your machine. Public repos read on our server are deleted after reading, not stored.
Turn your app into a guide your users can follow.
Paste a public GitHub link and get your founder runbook + fix-list free in about a minute — no sign-up. Private code runs entirely in your browser.