feat: add AI chat, federated search, and AI tools documentation

- /api/chat: Anthropic streaming chat via @ai-sdk/anthropic (server-only key)
- /api/search: Orama federated search over content/docs + external/onflow-docs
- src/components/search.tsx: Cmd+/ search panel with AI answer pane,
  draggable, localStorage persistence
- src/lib/external-search-index.ts: indexes onflow-docs submodule content
- content/docs/ai-tools/: new documentation section covering the Cadence MCP
  server (flow mcp), Claude Code plugin, llm-endpoints, and editor integrations
  (Claude, Cursor, Codex, Gemini, Antigravity, OpenCode)

Author: Aliserag

content/docs/ai-tools/index.mdx

@@ -0,0 +1,20 @@
+---
+title: AI Tools
+---
+
+Cadence is designed for AI-native development. Three integrations make Cadence documentation and language intelligence available to any AI agent:
+
+- **[Skills](/docs/ai-tools/skills)** — inject Cadence knowledge into AI coding agents with one command
+- **[MCP Server](/docs/ai-tools/mcp-server)** — `flow mcp` from the Flow CLI: gives AI agents type checking, symbol lookup, contract source fetching, and read-only on-chain script execution
+- **[LLM Endpoints](/docs/ai-tools/llm-endpoints)** — plain-text documentation endpoints optimized for LLM context windows
+
+## Agent integrations
+
+Step-by-step setup guides for specific AI tools:
+
+- [Antigravity](/docs/ai-tools/integrations/antigravity) — skill and MCP setup
+- [Claude](/docs/ai-tools/integrations/claude) — Claude Code, Claude Desktop, Claude API
+- [Cursor](/docs/ai-tools/integrations/cursor) — project rules and MCP setup
+- [OpenAI Codex](/docs/ai-tools/integrations/codex) — AGENTS.md and context injection
+- [Gemini](/docs/ai-tools/integrations/gemini) — Gemini CLI and API
+- [OpenCode](/docs/ai-tools/integrations/opencode) — MCP configuration

content/docs/ai-tools/integrations/antigravity.mdx

@@ -0,0 +1,38 @@
+---
+title: Antigravity
+---
+
+Configure [Antigravity](https://antigravity.dev) to work with Cadence.
+
+## Add Cadence as project context
+
+Antigravity reads project-level context files automatically. Add a `CADENCE.md` (or merge into your existing `AGENTS.md`) pointing at the [`/llms-full.txt`](../llm-endpoints) endpoint so the model has the full reference loaded on startup:
+
+```markdown
+## Cadence Development
+
+This project uses Cadence, the smart contract language for the Flow blockchain.
+Full reference: https://cadence-lang.org/llms-full.txt
+Quick index: https://cadence-lang.org/llms.txt
+
+Resources use `@` prefix and must be moved with `<-`. Use `access(all)` for public access (not `pub`). Capability-based access control with entitlements.
+```
+
+If you also use Claude Code, install the [flow-ai-tools](https://github.com/onflow/flow-ai-tools) marketplace there for richer skill coverage — it ships the full Cadence + Flow skill suite (see [Skills](../skills)).
+
+## Add MCP server
+
+Add the Cadence MCP server to your Antigravity configuration — calls the Flow CLI's built-in `flow mcp` subcommand:
+
+```json
+{
+  "mcpServers": {
+    "cadence-mcp": {
+      "command": "flow",
+      "args": ["mcp"]
+    }
+  }
+}
+```
+
+This gives Antigravity access to all [MCP tools](../mcp-server) — Cadence code checking, type inspection, symbol lookup, contract source fetching, and read-only on-chain script execution. Requires [Flow CLI](https://developers.flow.com/tools/flow-cli) ≥ v2.16.0.

content/docs/ai-tools/integrations/claude.mdx

@@ -0,0 +1,52 @@
+---
+title: Claude
+---
+
+Configure Claude to work with Cadence via skills, MCP, or context injection.
+
+## Claude Code
+
+### Install Flow's skill library
+
+The official [onflow/flow-ai-tools](https://github.com/onflow/flow-ai-tools) marketplace ships the full Cadence + Flow skill suite under one plugin:
+
+```bash
+/plugin marketplace add onflow/flow-ai-tools
+/plugin install flow-dev@flow-ai-tools
+```
+
+See [Skills](../skills) for the full skill list.
+
+### Add MCP server
+
+```bash
+claude mcp add --scope user cadence-mcp -- flow mcp
+```
+
+This registers the [Cadence MCP server](../mcp-server) — built into the Flow CLI as the `flow mcp` subcommand. Gives Claude Code access to Cadence code checking, type inspection, symbol lookup, contract source fetching, and read-only on-chain script execution. Requires [Flow CLI](https://developers.flow.com/tools/flow-cli) ≥ v2.16.0.
+
+## Claude Desktop
+
+Add the Cadence MCP server to your `claude_desktop_config.json`:
+
+```json
+{
+  "mcpServers": {
+    "cadence-mcp": {
+      "command": "flow",
+      "args": ["mcp"]
+    }
+  }
+}
+```
+
+## Claude API
+
+When building with the Claude API, inject Cadence context into the system prompt:
+
+```bash
+# Fetch the full documentation
+curl -s https://cadence-lang.org/llms-full.txt
+```
+
+Or use the [MCP endpoint](../mcp-server) for programmatic access to documentation and language tools.

content/docs/ai-tools/integrations/codex.mdx

@@ -0,0 +1,33 @@
+---
+title: OpenAI Codex
+---
+
+Configure OpenAI Codex (the CLI agent) to work with Cadence.
+
+## Add Cadence to AGENTS.md
+
+Codex reads `AGENTS.md` from the project root automatically. Add a Cadence section that points it at the [`/llms-full.txt`](../llm-endpoints) endpoint:
+
+```markdown
+## Cadence Development
+
+This project uses Cadence, the smart contract language for the Flow blockchain.
+Full reference: https://cadence-lang.org/llms-full.txt
+Quick index: https://cadence-lang.org/llms.txt
+
+Key conventions:
+- Use `access(all)` for public access, not the deprecated `pub`
+- Resources use `@` prefix and must be moved with `<-` (never copied)
+- Always handle resources — they cannot be lost or copied
+- Use capability-based access control with entitlements
+```
+
+If you also use Claude Code, install the [flow-ai-tools](https://github.com/onflow/flow-ai-tools) marketplace there for richer skill coverage — it ships the full Cadence + Flow skill suite (see [Skills](../skills)).
+
+## Context injection
+
+For direct API usage, inject the Cadence documentation into the system prompt:
+
+```bash
+curl -s https://cadence-lang.org/llms-full.txt
+```

content/docs/ai-tools/integrations/cursor.mdx

@@ -0,0 +1,37 @@
+---
+title: Cursor
+---
+
+Configure Cursor to understand Cadence smart contracts.
+
+## Add Cadence as project context
+
+Cursor reads `.cursor/rules/*.mdc` files automatically. Create `.cursor/rules/cadence.mdc` and point it at the [`/llms-full.txt`](../llm-endpoints) endpoint so the model has the full reference:
+
+```mdc
+---
+description: Cadence smart contract development on Flow
+globs: *.cdc
+---
+
+When working with `.cdc` files, follow Cadence language conventions:
+- Use `access(all)` for public access (not the deprecated `pub`)
+- Resources use `@` prefix and must be moved with `<-` (never copied)
+- Always handle resources — they cannot be lost or copied
+- Use capability-based access control with entitlements
+
+Full Cadence reference: https://cadence-lang.org/llms-full.txt
+Quick index: https://cadence-lang.org/llms.txt
+```
+
+If you also use Claude Code, install the [flow-ai-tools](https://github.com/onflow/flow-ai-tools) marketplace there for richer skill coverage — it ships the full Cadence + Flow skill suite (see [Skills](../skills)).
+
+## Add MCP server
+
+In Cursor settings → MCP → Add new server:
+
+- **Name**: `cadence-mcp`
+- **Type**: `command`
+- **Command**: `flow mcp`
+
+This registers the [Cadence MCP server](../mcp-server) — built into the Flow CLI as the `flow mcp` subcommand. Gives Cursor access to Cadence code checking, type inspection, symbol lookup, contract source fetching, and read-only on-chain script execution. Requires [Flow CLI](https://developers.flow.com/tools/flow-cli) ≥ v2.16.0.

content/docs/ai-tools/integrations/gemini.mdx

@@ -0,0 +1,38 @@
+---
+title: Gemini
+---
+
+Configure Google Gemini to work with Cadence.
+
+## Gemini CLI
+
+### Add Cadence to GEMINI.md
+
+Gemini CLI reads `GEMINI.md` from the project root automatically. Create or update it with a Cadence section that points at the [`/llms-full.txt`](../llm-endpoints) endpoint:
+
+```markdown
+## Cadence Development
+
+This project uses Cadence, the smart contract language for the Flow blockchain.
+Full reference: https://cadence-lang.org/llms-full.txt
+Quick index: https://cadence-lang.org/llms.txt
+
+Key conventions:
+- Use `access(all)` for public access, not the deprecated `pub`
+- Resources use `@` prefix and must be moved with `<-` (never copied)
+- Always handle resources — they cannot be lost or copied
+- Use capability-based access control with entitlements
+```
+
+If you also use Claude Code, install the [flow-ai-tools](https://github.com/onflow/flow-ai-tools) marketplace there for richer skill coverage — it ships the full Cadence + Flow skill suite (see [Skills](../skills)).
+
+## Gemini API
+
+When using the Gemini API, inject Cadence context into the system instruction:
+
+```bash
+# Fetch the full documentation
+curl -s https://cadence-lang.org/llms-full.txt
+```
+
+Or fetch specific pages from the [LLM endpoints](../llm-endpoints).

content/docs/ai-tools/integrations/index.mdx

@@ -0,0 +1,28 @@
+---
+title: Integrations
+description: Editor-specific setup for using Cadence with Claude Code, Cursor, OpenAI Codex, Gemini, Antigravity, and OpenCode.
+---
+
+Configure your AI coding agent to understand Cadence smart contracts. Each integration uses the same two building blocks:
+
+1. **Project context** — point your agent at [`/llms-full.txt`](../llm-endpoints) (or [`/llms.txt`](../llm-endpoints) for a leaner index) so it has the full Cadence reference loaded.
+2. **MCP server** — register the [Cadence MCP server](../mcp-server) (built into the [Flow CLI](https://developers.flow.com/tools/flow-cli) as `flow mcp`) for code checking, type inspection, symbol lookup, contract source fetching, and read-only on-chain script execution.
+
+For Claude Code specifically, the [flow-ai-tools](https://github.com/onflow/flow-ai-tools) marketplace bundles the full Cadence + Flow [skill suite](../skills) under one plugin install.
+
+## Editors
+
+| Editor | Project context | Skills | MCP |
+|---|---|---|---|
+| [Claude Code](./claude) | via flow-ai-tools skills | ✓ full suite | ✓ stdio |
+| [Cursor](./cursor) | `.cursor/rules/cadence.mdc` | — | ✓ stdio (deeplink) |
+| [OpenAI Codex](./codex) | `AGENTS.md` | — | — |
+| [Gemini](./gemini) | `GEMINI.md` | — | — |
+| [Antigravity](./antigravity) | `CADENCE.md` / `AGENTS.md` | — | ✓ stdio |
+| [OpenCode](./opencode) | `AGENTS.md` | — | ✓ stdio |
+
+For Claude Desktop and Claude API setup, see the [Claude](./claude) page.
+
+## Don't see your editor?
+
+Any MCP-aware editor can use the Cadence MCP server — point it at `flow mcp` as a stdio command (Flow CLI ≥ v2.16.0). Any agent that reads project-level context files (`AGENTS.md`, etc.) can use the [LLM endpoints](../llm-endpoints) for the full Cadence reference. [Open an issue](https://github.com/onflow/cadence-lang.org/issues) if you'd like first-class instructions for a specific editor.

content/docs/ai-tools/integrations/meta.json

@@ -0,0 +1,12 @@
+{
+  "title": "Integrations",
+  "pages": [
+    "antigravity",
+    "claude",
+    "cursor",
+    "codex",
+    "gemini",
+    "opencode",
+    "..."
+  ]
+}

content/docs/ai-tools/integrations/opencode.mdx

@@ -0,0 +1,38 @@
+---
+title: OpenCode
+---
+
+Configure [OpenCode](https://opencode.ai) to work with Cadence.
+
+## Add Cadence as project context
+
+OpenCode reads project-level context files automatically. Add a section to your `AGENTS.md` pointing at the [`/llms-full.txt`](../llm-endpoints) endpoint:
+
+```markdown
+## Cadence Development
+
+This project uses Cadence, the smart contract language for the Flow blockchain.
+Full reference: https://cadence-lang.org/llms-full.txt
+Quick index: https://cadence-lang.org/llms.txt
+
+Resources use `@` prefix and must be moved with `<-`. Use `access(all)` for public access (not `pub`). Capability-based access control with entitlements.
+```
+
+If you also use Claude Code, install the [flow-ai-tools](https://github.com/onflow/flow-ai-tools) marketplace there for richer skill coverage — it ships the full Cadence + Flow skill suite (see [Skills](../skills)).
+
+## Add MCP server
+
+Add the Cadence MCP server to your OpenCode configuration — calls the Flow CLI's built-in `flow mcp` subcommand:
+
+```json
+{
+  "mcp": {
+    "cadence-mcp": {
+      "type": "local",
+      "command": ["flow", "mcp"]
+    }
+  }
+}
+```
+
+This gives OpenCode access to all [MCP tools](../mcp-server) — Cadence code checking, type inspection, symbol lookup, contract source fetching, and read-only on-chain script execution. Requires [Flow CLI](https://developers.flow.com/tools/flow-cli) ≥ v2.16.0.

content/docs/ai-tools/llm-endpoints.mdx

@@ -0,0 +1,33 @@
+---
+title: LLM Endpoints
+description: "Plain-text endpoints for Cadence docs optimized for LLM context windows: /llms.txt for a page index and /llms-full.txt for the complete documentation as plain text."
+---
+
+The site exposes plain-text endpoints optimized for LLM context windows. These are useful for RAG pipelines or injecting Cadence documentation directly into prompts.
+
+## Endpoints
+
+| Endpoint | Description |
+|---|---|
+| [`/llms.txt`](/llms.txt) | Index of all documentation pages with links |
+| [`/llms-full.txt`](/llms-full.txt) | Complete documentation as plain text |
+
+## llms.txt
+
+A lightweight index listing every documentation page with its title and URL. Use this when you need to find the right page before fetching its full content.
+
+```bash
+curl https://cadence-lang.org/llms.txt
+```
+
+## llms-full.txt
+
+The complete processed markdown for all documentation pages, concatenated into a single file. Use this when you want to inject the entire Cadence knowledge base into an LLM context window.
+
+```bash
+curl https://cadence-lang.org/llms-full.txt
+```
+
+:::tip
+You can also append `.mdx` to any documentation URL to get raw markdown for a single page. For example: `https://cadence-lang.org/docs/language/resources.mdx`
+:::