Hey HN,

I'm William, founder of Doculearn. I built this after spending years wrestling with the same problem: anyone can document a single file, but understanding how a complex system actually works requires analyzing the entire codebase—dependencies, architecture, design decisions, and all.

The Problem:

We're generating code faster than ever with AI assistants (Copilot, Claude Code, etc.), but documentation can't keep up. Traditional tools work file-by-file. When you're onboarding someone or doing a handover, they need to understand "how does this entire system work?" not just "what does this function do?"

What Doculearn Does:

We ingest your entire repository and provide comprehensive insights that go beyond basic file-level documentation. Ask questions like "What are the critical dependencies in this system?" or "How does authentication flow through the architecture?" and get answers that consider your complete codebase context.

Key Features:

Repository-scale analysis (not just individual files) Dependency mapping and architectural insights Automated PDF exports and static web deployments Answers complex questions about system design and component relationships

Why I Built This:

After working on multinational projects across Africa and winning a hackathon with an automation tool, I saw the same pattern: teams struggle to understand large codebases, especially as AI generates more code. Documentation needs to work at the system level, not just the file level. We're launching October 31, 2025.

Sign up for the waiting list at https://doculearnapp.com and be among the first to experience documentation that actually understands your entire system.

Would love to hear your thoughts—especially if you've dealt with documentation challenges in large codebases or AI-generated code.

I applaud your effort, agree on the need, and don't want to rain on a fellow founder's parade, but I have a thought.

I'm sure you know all of this is already possible by prompting in a tool like Cursor. Agents can already write comprehensive and integrated doc, as you are no doubt doing behind the scenes.

If you're creating the prompt, how can the doc include any of the "secret sauce" that makes their app special? This is the most important stuff to document, the why as well as the how.

Won't your generic doc always be missing that aspect?