smartcontractkit / smartcontractkit/documentation
Stop generating llms.txt files for Chainlink Functions and Chainlink Automation
Open
@thodges-gh is already working on this.
Since Jul 6, 2026.
- Dominant language
- MDX
- Stars
- 526
- Forks
- 478
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 75
Description
Problem
We generate llms.txt and llms-full.txt documentation bundles for every product section, including Chainlink Functions and Chainlink Automation. For these two products we are steering developers toward CRE for new use cases, so we do not want LLMs pulling in and focusing on the full Functions/Automation documentation bundles.
Today this happens because:
src/config/llms.tslistschainlink-functionsandchainlink-automationinSUPPORTED_LLM_SECTIONS, sogenerate-llms.tsproducesllms-full.txtfor them (and the[section]/llms-full.txtroute serves them, andvalidate-llms.tsexpects them).- Hand-authored
llms.txtproduct indexes exist for both undersrc/content/, are synced intopublic/bysync-product-llms.ts, and are linked from the rootpublic/llms.txtindex.
Desired outcome
- Remove Chainlink Functions and Chainlink Automation from llms.txt generation.
- Delete the already-generated
llms-full.txtand the hand-authoredllms.txtindex files for both products (including the syncedpublic/copies). - Remove their entries from the root
public/llms.txtindex.
Note: this only removes the LLM bundles — the underlying product documentation pages are unchanged.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.