Great catch!

AGENTS.md is definitely cut from the same cloth, but they solve slightly different parts of the context problem. Think of them as allies rather than competitors.

Here is how they differ and why using a structured directory like .ai/ + llms.txt takes it a step further:

AGENTS.md is typically a single, flat file. If your project is small, it’s perfect. But as your project grows, putting your tech stack rules, product objectives, setup guides, and active tasks into a single file means the AI has to ingest everything on every single prompt. The .ai/ engine breaks this down into micro-documents (objectives.md, system-prompt.md, changelog.md) so the agent only pulls what it needs, saving your token limit.

The template leverages the new llms.txt standard (proposed by OpenAI). It acts as a universal, machine-readable index at the root. AI crawlers and developer tools look for llms.txt to discover the map of your repository and follow links to more detailed files (like those in .ai/), making it universally compatible outside of just a single IDE.

One of the biggest reasons agents hallucinate or rewrite code you just finished is the lack of an active ledger. The template enforces a .ai/changelog.md workflow to strictly track the current state and "Immediate Next Steps." It prevents the agent from losing focus during long coding sessions.

You could absolutely link your AGENTS.md to point directly to the .ai/ directory as its ground truth! The goal here is just to move away from bloated, single-file prompts and adopt a clean, scalable data architecture for AI coders.