FeedDiscussion
“Every page gets read twice” is the right line.
Once by the developer, once by the agent that will confidently misuse anything vague or stale.
The line that stood out to me was: "every page now gets read twice." That perfectly captures what's changing in developer tooling.
For years, good documentation was about helping humans understand a system. Now it also has to help agents execute against it correctly. The cost of stale docs isn't just developer frustration anymore it's agents confidently generating incorrect implementations at scale.
What's interesting is that this shifts documentation from being a support asset to being part of the product itself. If APIs, SDKs, and MCP endpoints are the interface, then machine-readable docs become part of the runtime context that determines whether integrations succeed or fail.
The challenge now isn't making docs agent-friendly. It's keeping them synchronized with reality as fast as the product evolves. That's where most teams will struggle.
Really interesting perspective. The idea that every doc page now has two readers — the developer and the agent — feels very accurate.
What stood out to me most is that agent-first docs are not just about formatting content differently. They reduce wrong assumptions by giving agents cleaner, current, machine-readable context. For security or identity protocols, that matters even more because a small misunderstanding can turn into a real implementation risk.
I also like the split between llms.txt, llms-full.txt, Skills, and MCP. It makes the documentation layer feel less like static content and more like part of the developer tooling itself.