Agents

VLLNT UI exposes agent-readable surfaces so coding agents can discover components, inspect install contracts, and cite current documentation without scraping the rendered site.

llms.txt

Use /llms.txt for a compact overview of the registry. It includes install guidance, core docs links, and component links grouped by category.

llms-full.txt

Use /llms-full.txt when the agent needs one larger text context. It includes the main docs pages and component metadata summaries.

Registry JSON

Use /r/registry.json for discovery and /r/<name>.json for exact install descriptors. JSON is the most reliable source for file paths, dependencies, and registry dependencies.

MCP

The /mcp route is reserved for agent workflows that need a structured protocol endpoint. Treat registry JSON as the canonical install contract and MCP as an integration surface.

Safe agent workflow

• Fetch /llms.txt for orientation.
• Fetch /r/registry.json to choose components.
• Fetch individual /r/<name>.json descriptors before editing code.
• Prefer package source over generated registry files when contributing upstream.
• Run the project gates before opening a PR.