The machine-readable front door, parsed and checked
Parse, validate, and build llms.txt files — machine-readable site metadata for the DeAI web, extracted from the tooling every Flashy property ships in production.
Parse, validate and build llms.txt — the file that tells a model what a site is and where its real documents live. Extracted from what every Flashy property already ships, so it is the working implementation rather than a reading of the spec.
`@flashyos/llms-txt` parses, validates and builds `llms.txt` — the file that tells a model what a site is and where its real documents live. It is extracted from what every Flashy property already serves in production, so it is the working implementation rather than a reading of the spec.
The format is one `# Title`, an optional `> summary` blockquote a model reads first, then `##` sections of markdown links. `validate` checks a local file and `check` fetches a live URL; both report every problem at once, never just the first, because a fix-one-rerun loop trains people to stop running the validator.
Exit 0 when there are no errors; warnings inform without gating.
Installing it puts this command on your path — read from the package’s own manifest, so this list cannot drift from what you actually get.
llms-txtThe validator is extracted from what every Flashy property already serves in production, not designed on a whiteboard, so the rules it enforces are the rules real files already pass. It reports every problem at once rather than the first, so a fix-one-rerun loop cannot train people to stop checking. Verify any site’s front door yourself with `npx @flashyos/llms-txt check https://flashyos.com`.
Apache-2.0, read from the package’s own manifest. Embed it in anything, including closed software — that is what makes a spec adoptable and a verifier worth running. FlashyOS’s server side is AGPL-3.0-only instead, and a test in the monorepo asserts the direction between them: AGPL code may consume this, this may never consume AGPL code.