Skip to content

llms.txt

A standard text file that gives LLMs everything they need to understand Juice. Served at /llms.txt on the docs site — no setup required.

What Is llms.txt?

llms.txt is an emerging standard for making websites LLM-readable. It is a markdown file at the root of a site that describes the project, its key concepts, and links to relevant documentation.

When an AI assistant encounters a Juice project, it can fetch https://juice-docs.pages.dev/llms.txt to get an accurate overview of the framework instead of guessing from training data.

What It Contains

The Juice llms.txt includes:

  • Architecture overview — the three-piece model (Vite plugin, runtime, client)
  • File-system routing conventions — every special filename and what it does
  • Full API surface — all public exports from runtime and client packages
  • Key patterns — server actions, streaming modes, middleware, typed context
  • Server entry examples — per-runtime (Bun, Cloudflare, Deno, Node)
  • Doc links — every guide, reference, and integration page

Using It

In Chat-Based Tools

Paste the URL when starting a conversation about a Juice project:

I'm working on a Juice app. Here's the framework reference:
https://juice-docs.pages.dev/llms.txt

Most LLMs will fetch and read the file automatically.

In Project Instructions

Add the URL to your project-level AI config. For example, in CLAUDE.md:

## Framework
This project uses Juice (React 19 RSC framework).
Reference: https://juice-docs.pages.dev/llms.txt

In Your Own Docs Site

If you are building your own app with Juice and want AI tools to understand your app's conventions, create your own llms.txt in your public/ directory. The Vite build copies static assets to the output automatically.

File Location

The file lives at docs/public/llms.txt in the Juice repo. Cloudflare Pages serves it as a static asset at https://juice-docs.pages.dev/llms.txt.

Spec Compliance

The file follows the llmstxt.org format:

  • H1 with the package name
  • Blockquote with a one-line summary
  • Prose sections with framework details
  • H2 sections with linked doc pages grouped by category