We Love Claude
A feature-by-feature Claude guide that updates itself via pull requests.
The question I was chasing
Is a documentation site that keeps itself current, with me out of the loop, actually possible?
Claude changes constantly, features land on desktop and web at different times, and a hand-maintained guide is stale before it is published. A static guide would be wrong within a week. I wanted to know whether the maintenance could be the product.
The constraints
The whole premise collapses if a human has to babysit it. So the maintenance loop had to be genuinely autonomous (notice a change, draft a correct edit, propose it) and safe enough to trust without watching it. Autonomy that can silently publish wrong information is not worth having.
The decisions that mattered
Two agents, not one. Desktop and web drift independently, so each surface gets its own watcher.
PRs, not auto-merge. The agents draft changes and open pull requests; a human still gates what ships. That single decision is what makes autonomous maintenance trustworthy instead of reckless.
Astro and MDX, so the content is plain files an agent can edit like code.
Teach the agents what counts as a change. Telling a genuine feature update from UI noise was most of the work. Without it they open a pull request every time a button moves two pixels.
Built with: Astro, TypeScript, MDX, Claude Code, Cursor
Where it landed
Both watchers are running at weloveclaude.com, in beta, opening pull requests as Claude changes. The site keeps itself current, but nothing lands until I approve it, which is the version of autonomy I will actually trust.
Part of the Rolling Waves work archive.