feat: add llms.txt — first step toward agent-driven adoption#42
Open
enricopiovesan wants to merge 1 commit into
Open
feat: add llms.txt — first step toward agent-driven adoption#42enricopiovesan wants to merge 1 commit into
enricopiovesan wants to merge 1 commit into
Conversation
First concrete piece of a strategy for getting coding agents (Claude Code, Cursor, etc.) to build with Traverse: a structured, agent-legible summary at the conventional /llms.txt path, following the llmstxt.org format (H1, blockquote summary, linked sections, an Optional tail for lower-priority pages). Content is a curated path through what's already on the site, not new claims: quickstart and concepts first, the MCP tool list and setup guide for agent-building specifically, platforms.html called out explicitly as the source of truth on what's actually shipped (so an agent doesn't take the blockquote's target list as a promise), and the security audit and roadmap for anyone checking project maturity. Every linked URL verified against the actual build output. This addresses the "agent succeeds when a developer points it at Traverse" half of the adoption strategy. The other half floated in discussion — auditing whether the quickstart is actually followable by an agent end-to-end without hitting an undocumented wall, and MCP registry listing — are separate next steps, not done here. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
First concrete step of an "get coding agents building with Traverse" strategy: a structured, agent-legible summary at the conventional
/llms.txtpath, following the llmstxt.org format (H1, blockquote summary, linked sections, an## Optionaltail for lower-priority pages).The realistic near-term goal here isn't "agents discover Traverse unprompted" (a slow, low-control bet for a solo 0.x project) — it's making sure an agent succeeds when a developer says "use Traverse for this." This file is the entry point for that: quickstart and concepts first, the MCP tool list and setup guide for agent-building specifically, and
/platforms.htmlcalled out explicitly as the source of truth so an agent doesn't take the summary's target list as a promise beyond what's actually shipped.Content is entirely a curated path through what's already on the site — no new claims. Every linked URL checked against the actual build output.
Test plan
npm run buildcleandist//llms.txtin the browserNot done here
Two other pieces of the same strategy came up in discussion and are separate next steps: auditing whether
/docs/quickstartis actually followable by an agent end-to-end without hitting an undocumented wall, and what MCP registry listing fortraverse-mcpactually requires.🤖 Generated with Claude Code