Coding agents interact with documentation differently than humans — they can't recover from truncated indexes, broken links, or missing metadata. This post details how the Prisma docs team audited their documentation against an Agent Readiness Score and fixed five core issues: an oversized llms.txt index (split into per-area files), missing per-page pointers back to the index, Markdown/HTML parity gaps, broken relative links in the full-content feed, and absent agent skill and MCP discovery documents. The post also provides a reusable four-step process (audit, group failures by cause, fix discoverability/parity/links/metadata, add CI checks) for any team wanting to make their docs agent-ready.
Table of contents
Why agents read docs differently than peopleWhat we fixed in the Prisma docsPut the checks in CI, because the score is a snapshotHow to audit your own docsFrequently asked questions1.5K Impressions1 Comment