Claude Code documentation agent keeps project docs up to date with Docusaurus. Created a Docusaurus site: npx create-docusaurus@latest my-docs classic Added the agent: npx claude-code-templates@latest --agent=documentation/docusaurus-expert --yes Then prompt: "Use docusaurus-expert to review that the documentation is correct and up-to-date" Now the docs stay synced with code changes. That’s... how I set up as shown in the video.show more

Check the agent implementation here 👇

So the docusaurus agent generates your project's documentation?

Yes. Setup Docusaurus in your project, deploy to subdomain (like add the agent. Then: "Review staged changes and update Docusaurus docs." Agent analyzes code changes and updates documentation automatically. Works great with CI/CD pipelines too. Should I create a step-by-step guide for this? 😅

Lovely. Thank you for the tip.

Really like this workflow, docs that actually keep pace with code changes is such a pain point. This feels like the way documentation should work by default.

@Dovahkiin_69 How does it compare to context7?

nice was thinking of making a github action to do this when PRs were merged

auto patch + docs sync on merge sounds like black magic honestly

what did you use to make the video?

BS

Doc sync with Docusaurus cuts drift! Claude Code shows agents can own real dev workflows.

Interesting. Automating documentation updates could streamline workflows and improve accuracy. This might free developers to focus on core coding tasks.

really interesting. wondering if there is a cursor replacement for this

Love this! Do you know if it has any compatibility/integration with SuperClaude?

Then you start thinking.. it generates its .TF, bicep, w/e, builds updates its own ci/cd pipeline, with a hook for a self iterative feedback looooooperrr