smartcontractkit / smartcontractkit/documentation

Stop generating llms.txt files for Chainlink Functions and Chainlink Automation

Open
#3,941 0 comments 0 reactions 1 assignee View on GitHub

@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.ts lists chainlink-functions and chainlink-automation in SUPPORTED_LLM_SECTIONS, so generate-llms.ts produces llms-full.txt for them (and the [section]/llms-full.txt route serves them, and validate-llms.ts expects them).
  • Hand-authored llms.txt product indexes exist for both under src/content/, are synced into public/ by sync-product-llms.ts, and are linked from the root public/llms.txt index.
Desired outcome
  • Remove Chainlink Functions and Chainlink Automation from llms.txt generation.
  • Delete the already-generated llms-full.txt and the hand-authored llms.txt index files for both products (including the synced public/ copies).
  • Remove their entries from the root public/llms.txt index.

Note: this only removes the LLM bundles — the underlying product documentation pages are unchanged.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.