The Global Llms.txt Index
Searchable directory for llms.txt files when general search engines could index these.

AI-generated docs for their own ERP, not a tool others can use.
ERP users and teams documenting complex systems
We've been putting off the chore of writing technical docs since our team could handle all customer questions directly. However, since releasing an AI tool in the system, users have started asking it system questions as opposed to just data questions like it was designed for. It couldn't answer how-to questions, so, users got confused.
We didn't have a direct way to teach the Ai about our system since our internal docs were thin and the codebase large.
We ended up defining some good documentation practices in best-doc-practices.md, passed it to GPT-5.5, and asked it to write system docs for every module in the system (hundreds), handling 5-10 at a time for context limits.
To our surprise, it worked very well. The tool had read-access to all relevant server/client/database files, so the output was accurate and aligned to what we defined in the best-doc-practices.md.
Searchable directory for llms.txt files when general search engines could index these.
Fast Markdown-to-static-HTML with built-in search, but Docusaurus and MkDocs already own this space.
Day 0/1/2 framework is useful, but this is more educational content than functional tooling.
Validates llms.txt and AI robot rules before AI crawlers ignore your content.
Single Markdown to polished docs in 15 seconds, no config files.
Chat-first ERP cuts implementation costs, but Odoo and NetSuite already dominate.