Are you an LLM? Read llms.txt for a summary of the docs, or llms-full.txt for the full context.
Skip to content

LLMs

The Security Alliance Frameworks documentation is available in LLM-friendly format following the llms.txt standard. These files are generated at build time and designed to be fetched by AI assistants and coding tools to provide accurate, up-to-date framework content as context.

How to use

AI assistants should start with /llms.txt, the routing index. It lists every framework with a description and topic summary, so the AI can identify the best match and fetch the framework index file. From there, per-page files can be fetched for detailed content on a specific topic.

File structure

Three file types are available:

/llms.txt                                   routing index —> lists all framework index files
/llms/{framework-name}.txt                       framework index —> overview + links to per-page files
/llms/{framework-name}/{page}.txt               per-page file —> full content of a single page

The {framework-name} maps to the framework's folder name in the repository and {page} to the page's slug. For example, the Wallet Security seed phrase page lives at docs/pages/wallet-security/seed-phrase-management.mdx and its per-page file is at /llms/wallet-security/seed-phrase-management.txt.

What each file contains

/llms.txt - routing index:

  • One entry per framework with its index file URL, description, and topic list

/llms/{framework-name}.txt - framework index:

  • Header, description, and AI instructions
  • Full content of the overview page for immediate context
  • Links to all per-page files with one-line descriptions

/llms/{framework-name}/{page}.txt - per-page file:

  • Full markdown content of that page
  • Source URL and framework attribution

New frameworks and pages are picked up automatically on the next build.

For agents using a retrieval policy

Agents that load skill or policy files can find a retrieval policy at SKILL.md in the repository root. It defines branch policy (main vs develop), behavior with retrieved content, and what to do when retrieval returns nothing relevant. It complements the inline instructions inside /llms.txt.