Documentation for agents

Use a single page

Choose Copy for LLM below any page title to copy that page’s authored content as Markdown. View as Markdown opens the same content without navigation or interface elements. If clipboard access is blocked, use that link and copy the text manually.

Page exports live at /markdown/<page-path>.md and regenerate on every build. For example, Skills as Markdown.

Use the same documentation you read here as plain-text context for an agent. The files are generated from the authored pages used by this Astro/Starlight site on every build. They do not include the site’s navigation, HTML interface, or footers.

Start with the index

Every docs page, organized by topic, with a link and a one-line description.

→Read all documentation

All page content in one Markdown file, with page titles as headers.

→

What is llms.txt?

llms.txt is a plain-text, Markdown-formatted guide to documentation for language models. It helps an agent find the right page without reading menus or guessing routes. It is a documentation convention, not an executable instruction, an MCP connection, or an automatic installation. A client will not necessarily discover or load it by itself.

Prefer the index first. Ask the agent to read the relevant linked pages; use the full file when it needs broad context and has room for it. Reading the entire file can consume more of your model’s context window.

Use it in V3Code

Paste this into your agent chat:

Read https://docs.v3code.dev/llms.txt and follow the documentation links relevant
to my question. Explain how to connect my existing provider plan in V3Code.
Distinguish provider models from external ACP agents and MCP tools.
Cite the pages you used and say if you could not access them.

The selected agent must have a way to fetch the URLs. If it cannot, download the text and attach it using the client’s normal file-context controls. Do not assume it has read a page merely because you pasted its address.

Use it in Claude Code or Cursor

Give Claude Code or Cursor the same prompt and documentation URL in its agent chat. When it asks to fetch the documentation, review that request normally. If web access is unavailable, attach a downloaded copy instead.

For a recurring project instruction, add a short note to the instruction file that your client actually uses:

For V3Code-specific behavior, consult https://docs.v3code.dev/llms.txt first.
Read the relevant linked guides. Do not invent settings, commands, or capabilities.
If the documentation is unavailable, say so instead of assuming its contents.

This does not change the agent’s tools or permissions. Client capabilities and context limits still apply; the documentation does not override your project’s instructions.

Download a local copy

curl -fL https://docs.v3code.dev/llms.txt -o v3code-docs-index.md
curl -fL https://docs.v3code.dev/llms-full.txt -o v3code-docs-full.md

Review files before adding them to a shared repository. A downloaded copy does not update itself: download it again when you need current documentation.

What is included?

The index follows the docs sidebar: Get Started, The Editor, Models & Tokens, Studio & Discover, Connect, Account, and Reference. This guide is included too. The full file preserves prose, links, lists, tables, and code examples as Markdown. Visual components become readable headings, links, image descriptions, and captions—not HTML widgets.

Screenshots are still images: an agent without vision can read their descriptions, but cannot infer details that are only visible in the image. No account credentials or private editor sessions are included in these public documentation exports.