Codebase-to-docs generator for AI coding agents
Build a documentation-generation and maintenance tool for AI coding agents that converts a codebase into structured, agent-readable context files (architecture maps, conventions, decision logs) and keeps them in sync with the repo via git hooks or CI. Target solo developers and small teams running Claude Code, Cursor, or similar agents who need persistent project context without per-session memory.
What to build
A CLI + CI/git-hook tool that scans a codebase on every commit and auto-generates (then keeps in sync) a set of agent-readable context files — architecture map, coding conventions, and a decision log — formatted for Claude Code, Cursor, and similar AI coding agents. Targeted at solo developers and small teams who currently hand-maintain a CLAUDE.md or AGENTS.md file and watch it go stale.
AI coding agents re-derive project context every session because they have no persistent memory; the opportunity is a lightweight layer that turns the repo itself into always-current, agent-formatted documentation instead of relying on memory features or manually-updated markdown files.
Demand
Solo developers and small teams running Claude Code or Cursor daily are the buyers — they're the ones hitting repeated context-loss errors and currently patching it with manual CLAUDE.md/AGENTS.md files, which is exactly the pain the HN discussion surfaced.
- Hacker NewsEngagement
"Agents don't need memory, they need documentation" — 67 points, 51 comments on HN; high engagement at the source.
- Signal cluster: Agents don't need memory, they need documentationNews
Argues durable documentation is a more tractable fix for agent context loss than session memory; scored 0.56 with no historical match found.
Stack
- Git hooks (pre-commit/post-commit)
- GitHub Actions / GitLab CI
- Tree-sitter (code parsing for architecture maps)
- Claude API (summarization/decision-log generation)
- Markdown/MDX output targeting CLAUDE.md and AGENTS.md conventions
- SQLite or flat-file store for decision-log history
Solo + AI difficulty
The MVP — a CLI that parses a repo with Tree-sitter, calls an LLM to summarize architecture and conventions into a CLAUDE.md-style file, and wires a git hook to re-run on commit — is buildable solo in 2-4 weeks. The hard part is avoiding staleness/false-confidence on large or fast-changing repos and making the diffing (what actually needs re-summarizing) cheap enough to run on every commit without burning API budget.
- Entry threshold
- Buildable by one developer in 1-3 weeks using existing LLM APIs to parse and summarize repos into structured docs, plus a sync mechanism tied to commits; no licences or capital needed, but requires good prompt engineering to make summaries genuinely useful across many codebases.
- Window
- 6-12 months
Where to find first users
- Hacker News launch (Show HN)
- r/ClaudeAI and r/cursor
- Product Hunt launch
- Claude Code / Cursor community Discords
Competitors
Counter-signals & risks
Major agent vendors (Anthropic, Cursor/Anysphere, OpenAI) could ship native persistent memory or project-context features directly into their tools, commoditizing or obsoleting a third-party documentation layer.
Keeping generated documentation in sync with a fast-changing codebase via git hooks/CI is a known hard problem (staleness, merge conflicts, false confidence from outdated docs) that could undermine trust in the tool's output.
Solo developers and small teams may be price-sensitive and reluctant to adopt another CI-integrated tool, preferring lightweight conventions (README, CLAUDE.md/AGENTS.md files) they maintain manually over a dedicated product.
Original title: Agents don't need memory, they need documentation
Related signals
- Developer tools#1
Health checks for AI-generated codebases
Build a codebase health scanner aimed specifically at AI-assisted and vibe coders, combining static analysis with LLM-based pattern detection to flag fragility signatures common in AI-generated code: duplicated abstractions, missing tests on AI-written functions, inconsistent error handling, dead code, and risky untested diffs. Ship it as a CLI, GitHub Action, or VS Code extension with a weekly codebase health report, targeting solo builders and small teams shipping fast with Claude, Cursor, or Copilot.
Demand10/10measuredBuildability7/10est.Competition5/10est.via Hacker News44 competitors - Developer tools#3
Universal app starter kits for AI coding agents
Build niche vertical starter kits and templates on top of Expo Exact's universal write-once-run-everywhere stack (web, macOS, iOS, Linux) targeting indie devs who want to ship a cross-platform app fast without separate native codebases. Also sell AI-agent-friendly scaffolding, test harnesses, and CI recipes that let coding agents reliably build, run, and visually verify apps across all five targets using this kit.
Demand9/10measuredBuildability6/10est.Competition6/10est.via GitHub33 competitors - Developer tools#8
Tooling and templates for MuJoCo 4 studio
Build tooling around MuJoCo 4's new studio for robotics engineers and RL researchers: ready-made scene templates for common robot types, a URDF/MJCF converter and scene-sharing library, or short onboarding courses for teams migrating workflows into the new studio. Target hobbyist roboticists, RL researchers, and small startups building humanoid or industrial robot simulations who need to get productive with the new tool quickly.
Demand5/10est.Buildability7/10est.Competition10/10est.via Product Hunt0No named competitors