LLM Documentation Files
Point Claude Code, Cursor, Codex, and other AI coding tools at Oviato's LLM-optimized docs.
Oviato ships two LLM-facing documentation artifacts. They're regenerated on every docs deploy, so anything you point your AI tooling at stays in sync with the codebase.
The files
llms.txt — index (llmstxt.org spec)
https://docs.oviato.com/llms.txtFollows the llmstxt.org standard — a concise markdown file with one line per docs page (title + description + URL), organized by sidebar section. Agents that support the spec (Cursor, Claude Code, newer Copilot modes) fetch this first to see what's available, then pull individual pages on demand.
This saves context window: instead of ingesting ~200 KB of full documentation on every query, the agent scans the 6 KB index and fetches only the pages that match the task.
llms-full.txt — full concatenation
https://docs.oviato.com/llms-full.txtEvery docs page concatenated into one file, with a preamble that front-loads the mental model (three API surfaces, two-package story, response envelope, nonce tracker) so any LLM reading has the scope before the method-level reference. Use this when your tool doesn't understand llms.txt or you want one-shot context.
What's included
Both files cover:
- Getting started — install, quickstart, core concepts
- Packages — how to pick between
@oviato/sdkand@oviato/connect - Chain-agnostic — multi-chain actions (
sendTransfer,signMessage,switchNetwork,getBalance, auth, session) - EVM — the
evm.*namespace (reads, writes, recipes, troubleshooting, migration from viem/ethers) - UTXO — the
utxo.*namespace (PSBT signing) - React components — provider, hooks,
<ConnectButton>,<Connect> - x402 payments, RPC reference, developer dashboard
- Full changelog
Both are regenerated from the sidebar's meta.json on every deploy — drift between sidebar and LLM export is structurally impossible.
Setup in Claude Code
Add to your project's CLAUDE.md:
## Documentation
- Oviato LLM index: https://docs.oviato.com/llms.txt
- Oviato full docs: https://docs.oviato.com/llms-full.txt
- Oviato skill (deeper patterns): https://docs.oviato.com/skills/oviato.mdClaude Code will consult these when you ask Oviato-related questions.
Install the Oviato skill for richer guidance (decision trees, recipes, anti-patterns):
curl -o .claude/skills/oviato.md https://docs.oviato.com/skills/oviato.mdSee Skills for details.
Setup in Cursor
- Open Cursor Settings → Features → Docs
- Click Add new doc
- Paste:
https://docs.oviato.com/llms-full.txt - Name it
Oviato
Use @docs Oviato in chat to reference.
Cursor also supports .cursorrules at your project root. Grab our template:
curl -o .cursorrules https://docs.oviato.com/templates/cursorrules.txtSetup in Antigravity / Gemini CLI
Add to your project's GEMINI.md or AGENTS.md:
## Documentation
- Oviato LLM index: https://docs.oviato.com/llms.txt
- Oviato full docs: https://docs.oviato.com/llms-full.txtThe skill also works under .agents/skills/ — copy oviato.md in.
Setup in Codex
Paste the llms-full.txt URL into your repo's setup instructions or system prompt. For CLI agents, you can pre-fetch:
curl https://docs.oviato.com/llms-full.txt > .oviato-docs.txtThen reference .oviato-docs.txt in your agent's context.
Setup in ChatGPT / other web UIs
Download and attach:
curl -O https://docs.oviato.com/llms-full.txtUpload to a conversation or add to a Custom GPT's knowledge base.
How fresh are these files?
Regenerated on every docs deploy. The generator walks the meta.json sidebar — if a page ships in the docs, it's in the LLM files within minutes of deploy.
If your agent ever gives you stale API details (e.g. an old import path),
ask it to re-fetch https://docs.oviato.com/llms-full.txt. The skill file
explicitly instructs agents to do this.