How real projects summarise themselves for language models.
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
garrytanllms.txtgarrytan/gstack/gstack/llms.txt
tune/SKILL.md): Self-tuning question sensitivity + developer psychographic for gstack (v1: observational). - [/qa](qa/SKILL.md): Test the site, API or CLI and fix the bugs it finds. - [/qa-only](qa-only/SKILL.md
mrdoobllms.txtmrdoob/three.js/docs/llms-full.txt
# Three.js > Three.js is a cross-browser JavaScript library for creating 3D graphics using WebGL
Panniantongllms.txtPanniantong/Agent-Reach/llms.txt
update` upgrades the program and reinstalls every added channel's tools: tools with a tested version stay at that version, others get the newest version inside floor/exclude. It returns `result.user
Steady11 mentions in 2 weeks
No other project uses it yet
A markdown file at a website's root that gives language models a short guide to the site and links to the pages worth reading.
The same idea with the content included, so an agent can read the documentation in one request.
Agents and tools that fetch documentation on someone's behalf. It's a proposal, not a standard, and support varies.
Start with a one-line summary, then sections of links with a sentence each. The examples here show what real projects do.
