Skip to main content

Using with AI

These docs are built to be consumed by AI coding assistants, not just humans. Every build publishes machine-readable bundles following the llmstxt.org standard, generated by docusaurus-plugin-llms.

llms.txt bundles​

FileContents
/llms.txtIndex of every documentation section with links.
/llms-full.txtThe entire documentation set concatenated into one file.

Use /llms.txt when you want an assistant to discover the structure and pull only the pages it needs, and /llms-full.txt when you want to drop the whole reference into context at once.

How to use them​

  • Paste a URL. Give your assistant the /llms.txt or /llms-full.txt URL and ask it to read the docs before answering.
  • Let tools fetch automatically. Assistants and editors that understand the llms.txt convention can discover and load these bundles on their own.
  • Attach as context. Download /llms-full.txt and add it to your project or prompt so answers stay grounded in the real API rather than guesses.
tip

Prefer /llms.txt for day-to-day questions to keep context small, and reach for /llms-full.txt only when you need the complete API surface — for example, when migrating a large codebase or generating new pipelines from scratch.

A note on accuracy​

The bundles are generated directly from these docs, which are written against the shipped v2.0.0 API (Result, Result<T>, Maybe<T>, the UnambitiousFx.Functional.Failures types, and metadata). Pointing an assistant at them is the most reliable way to get code that compiles against the current library instead of training-data approximations.