I do agree with the other commenters about this being better solved with a <link rel="llm"> or just an Accept: text/markdown; profile=llm header. It's not give

I do agree with the other commenters about this being better solved with a <link rel="llm"> or just an Accept: text/markdown; profile=llm header. It's not given that a site only contains a single "thing" that LLMs are interested in. To continue your dev-doc example, many projects use github instead of their own website. Github's /llms.txt wouldn't contain anything at all about your FastHTML project, but rather instructions on how to use GitHub. That is not useful for people who asked Cursor about your library. Slightly off topic: An alternative approach to making sites more accessible to LLMs would be to revive the original interpretation of REST (markup with affordances for available actions).