MAGI vs llms.txt - when to use which? #5
Replies: 5 comments
-
|
From a strategy perspective, The footnote relationships in MAGI are something |
Beta Was this translation helpful? Give feedback.
-
|
That makes a lot of sense. So the stack would be: Thanks for clarifying! I think a comparison guide in the docs would help other newcomers. |
Beta Was this translation helpful? Give feedback.
-
|
I've been evaluating both for our documentation platform and here's my take: llms.txt is great for site-level configuration — telling LLMs "here's what this site is about and how to navigate it." It's like MAGI operates at the document level — each file carries its own context, processing instructions, and relationship graph. It's more like Schema.org markup but for markdown. They're actually complementary rather than competing:
We're planning to use both: |
Beta Was this translation helpful? Give feedback.
-
|
Good framing. We use llms.txt for site-level discovery and |
Beta Was this translation helpful? Give feedback.
-
|
From a dev-rel perspective: llms.txt for the public surface, MDA for the sources of truth in the repo. That mental model has worked for us. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm relatively new to making content AI-friendly and I'm trying to understand the landscape. The README mentions
llms.txtas a comparison point.From what I understand:
llms.txtis a single file at the root that tells LLMs about a siteAre they complementary or competing approaches? Could you use
llms.txtto point to MAGI documents? Would love to hear from people who've evaluated both.Beta Was this translation helpful? Give feedback.
All reactions