# llms.txt - AI-Friendly Documentation

URL: https://research-memex.org/docs/introduction/llms
Description: A machine-readable summary of Research Memex documentation following the llms.txt standard for AI consumption



*A site built for AI partnership should be legible to the partners themselves.*

llms.txt is an emerging standard for making documentation easy for large language models to consume. Think of it as a `robots.txt` for AI: one file providing a structured overview of an entire project.

## Three ways AI can access this site [#three-ways-ai-can-access-this-site]

| Method            | URL                              | What it provides                                                                |
| ----------------- | -------------------------------- | ------------------------------------------------------------------------------- |
| **llms.txt**      | [/llms.txt](/llms.txt)           | Generated orientation index with links to public docs pages and the full corpus |
| **llms-full.txt** | [/llms-full.txt](/llms-full.txt) | Complete site content in one file (auto-generated, always current)              |
| **.md suffix**    | Any page + `.md`                 | Markdown version of individual pages for token-efficient loading                |

Start with `llms.txt` for orientation, use `llms-full.txt` for comprehensive context, and use a `.md` suffix when you need only one page.

## Why llms.txt? [#why-llmstxt]

<Columns cols="2">
  <Card title="Fast context loading" icon="gauge-high">
    AI tools can load the entire documentation structure in one request
  </Card>

  <Card title="Structured navigation" icon="map">
    Hierarchical organization helps AI understand relationships between topics
  </Card>

  <Card title="Complete coverage" icon="book">
    Every page, concept, and resource listed in one place
  </Card>

  <Card title="Standard format" icon="file-lines">
    Following emerging best practices for AI-readable documentation
  </Card>
</Columns>

## How it works [#how-it-works]

When you ask an AI assistant about Research Memex:

```text
1. AI fetches research-memex.org/llms.txt
2. Reads the generated site summary and public documentation links
3. Parses the structured documentation map
4. Identifies relevant sections for your query
5. Fetches specific pages via .md suffix or llms-full.txt
6. Provides contextualized answers in the right voice
```

Try it yourself: ask an AI assistant, "Fetch the llms.txt from research-memex.org and tell me about [interpretive orchestration](/docs/introduction/core-principles#1-interpretive-orchestration)."

## What's included [#whats-included]

The generated `llms.txt` contains:

<AccordionGroup>
  <Accordion title="Project Overview" icon="circle-info">
    * Site title and description
    * Canonical link to the full generated corpus
    * Public docs pages grouped as readable links
  </Accordion>

  <Accordion title="Complete Navigation" icon="sitemap">
    * Public documentation pages with descriptions
    * Hierarchical structure (Introduction → Implementation → Case Studies → Toolkit → Advanced)
    * Direct links to each section
  </Accordion>

  <Accordion title="Tools & Stack" icon="wrench">
    * Essential tools and research platforms
    * Claude Code plugins and MCP servers in the Toolkit
    * AI-readable page links for focused loading
  </Accordion>

  <Accordion title="Frequently Asked Questions" icon="circle-question">
    * Generated links to pages that carry the detailed answers
    * No separate hand-written FAQ layer
    * No stale manual navigation map
  </Accordion>

  <Accordion title="Meta Information" icon="database">
    * Contact information
    * Repository links
  </Accordion>
</AccordionGroup>

## Use cases [#use-cases]

### For AI assistants [#for-ai-assistants]

<CodeGroup>
  ```bash Claude Code
  # AI can directly fetch and parse
  curl https://research-memex.org/llms.txt
  ```

  ```bash Antigravity CLI
  # Quick project understanding
  "Analyze the Research Memex based on its llms.txt"
  ```

  ```bash Cherry Studio
  # Direct markdown fetch
  "Fetch research-memex.org/llms-full.txt and explain cognitive blueprints"
  ```
</CodeGroup>

### For developers [#for-developers]

<Tabs>
  <Tab title="Quick Reference">
    Useful when working with an AI assistant while coding:

    ```
    "Using research-memex.org/llms.txt, show me the
    Zotero MCP setup steps"
    ```
  </Tab>

  <Tab title="Integration">
    Reference it in your own documentation:

    ```markdown
    This project uses the Research Memex approach.
    See: research-memex.org/llms.txt
    ```
  </Tab>

  <Tab title="Learning">
    Study it as an example:

    ```
    "Compare research-memex.org/llms.txt structure
    to other documentation approaches"
    ```
  </Tab>
</Tabs>

## View the files [#view-the-files]

<Columns cols="3">
  <Card title="llms.txt" icon="file-code" href="/llms.txt">
    Generated index for orientation
  </Card>

  <Card title="llms-full.txt" icon="file-lines" href="/llms-full.txt">
    Complete site content (auto-generated)
  </Card>

  <Card title="Page as Markdown" icon="markdown" href="/docs/introduction/core-principles.md">
    Example: Core Principles as .md
  </Card>
</Columns>

Access directly:

```text
https://research-memex.org/llms.txt
https://research-memex.org/llms-full.txt
https://research-memex.org/docs/introduction/core-principles.md
```

## The standard [#the-standard]

The llms.txt format is an emerging community standard for AI-readable documentation. Learn more:

<Columns cols="2">
  <Card title="llmstxt.org" icon="link" href="https://llmstxt.org">
    Official llms.txt specification and examples
  </Card>

  <Card title="Best practices" icon="star">
    * Plain text format (Markdown)
    * Hierarchical structure
    * Complete navigation
    * Concepts upfront
    * Links to full content
  </Card>
</Columns>

## For the meta-curious [#for-the-meta-curious]

<Aside label="Recursive documentation">
  This page explains AI-readable documentation while using the same conventions itself: the Research Memex method applying to its own surface.
</Aside>

This creates a beautiful loop:

1. We write docs about research with AI
2. We make those docs AI-readable (llms.txt + llms-full.txt + per-page `.md`)
3. Students learn the approach through dialogue with AI
4. The approach becomes embedded through practice
5. Students understand both the framework and how AI accesses knowledge

## Next steps [#next-steps]

<IndexRows>
  <IndexRow title="Dear Fellow AIs" href="/docs/introduction/ai-to-ai">
    AI-to-AI communication guidelines
  </IndexRow>
</IndexRows>