Overview
Two files are generated:| File | Purpose | Typical Size |
|---|---|---|
llms.txt | Index with links and descriptions | ~30 KB |
llms-full.txt | Complete docs concatenated | ~1 MB (~300k tokens) |
Output Directories
Understanding where files are generated is important:| Command | Output Location | Purpose |
|---|---|---|
gen:llms | docs-mkdocs/ | Local generation |
gen:llms --deploy | docs-mkdocs/ + website | Local + deploy to website |
gen:mkdocs --with-llms | docs-mkdocs/ | Generate MkDocs then LLM docs |
Directory Structure
Commands
Basic Generation
With Deployment
Combined with MkDocs
--with-llms does NOT deploy to the website. It only generates files in docs-mkdocs/.
Typical Workflows
Development: Generate Locally
Production: Generate and Deploy
CI/CD Pipeline
Output Files
llms.txt
A markdown index file with links to all documentation:llms-full.txt
All documentation concatenated into a single file with clear separators:- YAML frontmatter is stripped
- Files are ordered according to navigation structure
- Clear separators between files
- Token estimate included in generation output
- Release notes excluded by default (configurable)
Configuration
Configure LLM docs inconfig/docs.yaml:
Configuration Options
| Option | Default | Description |
|---|---|---|
enabled | true | Enable/disable LLM docs generation |
index_file | llms.txt | Filename for the index |
full_file | llms-full.txt | Filename for concatenated docs |
project_description | (see config) | Description in file headers |
exclude_sections | ['release-notes/'] | Patterns to exclude from full file |
deploy.target | '' | Deployment target directory |
deploy.docs_folder | docs | Subfolder for markdown files |
Deployment Details
When using--deploy, files are copied to the website:
- Copies
llms.txtandllms-full.txtto the target root - Copies all markdown files to
docs/subfolder - Preserves directory structure
API
LlmsDocsGenerator
GenerationResult
Both methods return aGenerationResult with: