Point your Pen. Comment. Improve.
Turn your vibe code into a wiki you can understand, review and improve.

I built it with AI. It worked.
But did I really understand it?

Your documentation connects your code, your AI, and your team.

When others
should weigh in.
Every request passes the auth middleware, then the cache in front of the database, then the handler.
Is the cache still needed? If not, remove it here and in the code.
Open any Markdown file, or let Claude create one from your code. Point to something you don't understand. Ask Claude to explain it — or change it.
Give others a link to your wiki. They explore and review your project without installing VS Code or Claude Code.
Comments from the web appear in your editor. Reply yourself, or let Claude Code investigate, fix the issue, and update the documentation.
Review the changes. Keep improving.Claude Code can document your whole project. Three Markdown files, three ways to use them.
architecture.mdLet Claude explain your project's architecture, components and dependencies.
security-standards.mdDescribe how your project should work. Your standards, written in plain Markdown.
security-review.mdLet Claude find gaps between your code and your standards. Fix the issues and verify the results.