[tylrcc]

Closes #755.

The docs site had no llms.txt, so AI tools and coding agents had no simple way to read the user guide. Following the implementation the issue lays out:

• vitepress-plugin-llms added as a devDependency in docs/package.json only — not the root package, whose postinstall (electron-builder, esbuild) a docs build should not pay for.
• docs/.vitepress/config.mjs imports it and adds it to vite.plugins, next to the existing vite.server block, with a comment saying why the files are generated rather than hand-written.
• The lockfile changes are the plugin's dependency subtree from npm install --save-dev vitepress-plugin-llms; the vitepress version is unchanged.

As the issue notes, the files will be served at https://wordpress.github.io/contributor-toolkit/llms.txt (project Pages subpath) and go live with the next manually-run docs.yml release, not on merge.

Verification — npm run docs:build from the repo root, then the three checks from the issue against docs/.vitepress/dist/:

• llms.txt lists every guide page with a link — all 21 pages under docs/guide/ are present.
• llms-full.txt (119 KB) contains the full guide text.
• testing.md is in neither file. It is in srcExclude; the only 'testing' hits in llms-full.txt are ordinary prose inside guide pages.

Pre-PR review (per AGENTS.md, against .github/instructions/code-review.instructions.md, on this branch's diff — 3 files, all under docs/): Architecture — the plugin sits in the docs package, matching the separation that package exists for; generation at build time keeps the files in sync with the guide. Security — build-time-only devDependency in the docs package; nothing ships in the app and no app dependency changed. Performance — no runtime cost; the build measured 57s here including generation. Cross-platform — the plugin is plain JS with no platform-specific behaviour. Tests — the docs package has no test suite; the build-and-inspect checks above are the verification, and a dead link would fail the build (ignoreDeadLinks: false). No findings needed fixing; nothing deferred.

[coderabbitai]

Pre-merge checks: 1

Failed checks: 1 inconclusive

Check name	Status	Explanation	Resolution
Description check		This assessment has not completed. The check will be retried on the next pre-merge check run.

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

• X
• Mastodon
• Reddit
• LinkedIn

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.