Generates llms.txt and llms-full.txt files for LLM-friendly project documentation following the llms.txt specification. Use when the user wants to create LLM-readable summaries, llms.txt files, or make their wiki accessible to language models.
Generate llms.txt and llms-full.txt files that provide LLM-friendly access to wiki documentation, following the llms.txt specification.
llms.txt or mentions the llms.txt standardllms-full.txt or context-expanded documentationBefore generating, resolve the source repository context:
git remote get-url originREPO_URLgit rev-parse --abbrev-ref HEADThe file follows the llms.txt specification:
# {Project Name}
> {Dense one-paragraph summary — what it does, who it's for, key technologies}
{Important context paragraphs — constraints, architectural philosophy, non-obvious things}
## {Section Name}
- [{Page Title}]({relative-path-to-md}): {One-sentence description of what the reader will learn}
## Optional
- [{Page Title}]({relative-path-to-md}): {Description — these can be skipped for shorter context}
[Title](url): Description entries| ❌ Bad | ✅ Good |
|---|---|
| "Architecture overview" | "System architecture showing how Orleans grains communicate via message passing with at-least-once delivery" |
| "Getting started guide" | "Prerequisites, local dev setup with Docker Compose, and first API call walkthrough" |
| "The API reference" | "REST endpoints with auth requirements, rate limits, and request/response schemas" |
Same structure as llms.txt but with full content inlined:
# {Project Name}
> {Same summary}
{Same context}
## {Section Name}
<doc title="{Page Title}" path="{relative-path}">
{Full markdown content — frontmatter stripped, citations and diagrams preserved}
</doc>
--- blocks) from each page```mermaid fences intact[file:line](URL) links stay as-is<!-- Sources: --> comments — these provide diagram provenanceThis skill works best when wiki pages already exist (via /deep-wiki:generate or /deep-wiki:page). If no wiki exists yet:
/deep-wiki:generate firstllms.txt from README + source code scan (without wiki page links)Generate three files:
| File | Purpose | Discoverability |
|---|---|---|
./llms.txt | Root discovery file | Standard path per llms.txt spec. GitHub MCP get_file_contents and search_code find this first. |
wiki/llms.txt | Wiki-relative links | For VitePress deployment and wiki-internal navigation. |
wiki/llms-full.txt | Full inlined content | Comprehensive reference for agents needing all docs in one file. |
The root ./llms.txt links into wiki/ (e.g., [Guide](./wiki/onboarding/contributor-guide.md)). The wiki/llms.txt uses wiki-relative paths (e.g., [Guide](./onboarding/contributor-guide.md)).
If a root llms.txt already exists and was NOT generated by deep-wiki, do NOT overwrite it.
Before finalizing:
llms.txt actually exist<doc> blocks in llms-full.txt have real content (not empty)llms.txt is concise (1-5 KB)llms-full.txt contains all wiki pages