What's the problem?
website/public/llms.txt is currently hand-maintained. As the docs and marketing routes evolve, it can drift from the actual website unless updates are automated or explicitly called out in contributor/agent instructions.
This came up during review of the website positioning PR. The reviewer asked whether we should auto-generate llms.txt, or add an agent instruction to consider updating it when new routes are added.
Proposed solution
Pick and implement a maintenance path for llms.txt:
- Auto-generate it from the website route/content source during website build or synthesis, or
- Add clear repo/agent guidance that new, renamed, or materially repositioned website routes should update
llms.txt.
If generation is feasible, prefer that so stale output can be caught by a check.
Alternatives you considered
Leave llms.txt manual-only. That is simple, but it makes drift likely as the website grows.
Additional context
This is a follow-up from review on the private website PR:
https://github.com/contextbridge/planbridge-private/pull/18#discussion_r3242895105
What's the problem?
website/public/llms.txtis currently hand-maintained. As the docs and marketing routes evolve, it can drift from the actual website unless updates are automated or explicitly called out in contributor/agent instructions.This came up during review of the website positioning PR. The reviewer asked whether we should auto-generate
llms.txt, or add an agent instruction to consider updating it when new routes are added.Proposed solution
Pick and implement a maintenance path for
llms.txt:llms.txt.If generation is feasible, prefer that so stale output can be caught by a check.
Alternatives you considered
Leave
llms.txtmanual-only. That is simple, but it makes drift likely as the website grows.Additional context
This is a follow-up from review on the private website PR:
https://github.com/contextbridge/planbridge-private/pull/18#discussion_r3242895105