Update LLMs.txt File

Update the existing llms.txt file in the root of the repository to reflect changes in documentation, specifications, or repository structure. This file provides high-level guidance to large language models (LLMs) on where to find relevant content for understanding the repository's purpose and specifications.

Primary Directive

Update the existing llms.txt file to maintain accuracy and compliance with the llms.txt specification while reflecting current repository structure and content. The file must remain optimized for LLM consumption while staying human-readable.

Analysis and Planning Phase

Before updating the llms.txt file, you must complete a thorough analysis:

Step 1: Review Current File and Specification

• Read the existing llms.txt file to understand current structure
• Review the official specification at https://llmstxt.org/ to ensure continued compliance
• Identify areas that may need updates based on repository changes

Step 2: Repository Structure Analysis

• Examine the current repository structure using appropriate tools
• Compare current structure with what's documented in existing llms.txt
• Identify new directories, files, or documentation that should be included
• Note any removed or relocated files that need to be updated

Step 3: Content Discovery and Change Detection

• Identify new README files and their locations
• Find new documentation files (.md files in /docs/, /spec/, etc.)
• Locate new specification files and their purposes
• Discover new configuration files and their relevance
• Find new example files and code samples
• Identify any changes to existing documentation structure

Step 4: Create Update Plan

Based on your analysis, create a structured plan that includes:

• Changes needed to maintain accuracy
• New files to be added to the llms.txt
• Outdated references to be removed or updated
• Organizational improvements to maintain clarity

Implementation Requirements

Format Compliance

The updated llms.txt file must maintain this exact structure per the specification:

1. H1 Header: Single line with repository/project name (required)
2. Blockquote Summary: Brief description in blockquote format (optional but recommended)
3. Additional Details: Zero or more markdown sections without headings for context
4. File List Sections: Zero or more H2 sections containing markdown lists of links

Content Requirements

Required Elements

• Project Name: Clear, descriptive title as H1
• Summary: Concise blockquote explaining the repository's purpose
• Key Files: Essential files organized by category (H2 sections)

File Link Format

Each file link must follow: [descriptive-name](relative-url): optional description

Section Organization

Organize files into logical H2 sections such as:

• Documentation: Core documentation files
• Specifications: Technical specifications and requirements
• Examples: Sample code and usage examples
• Configuration: Setup and configuration files
• Optional: Secondary files (special meaning - can be skipped for shorter context)

Content Guidelines

Language and Style

• Use concise, clear, unambiguous language
• Avoid jargon without explanation
• Write for both human and LLM readers
• Be specific and informative in descriptions

File Selection Criteria

Include files that:

• Explain the repository's purpose and scope
• Provide essential technical documentation
• Show usage examples and patterns
• Define interfaces and specifications
• Contain configuration and setup instructions

Exclude files that:

• Are purely implementation details
• Contain redundant information
• Are build artifacts or generated content
• Are not relevant to understanding the project

Execution Steps

Step 1: Current State Analysis

1. Read the existing llms.txt file thoroughly
2. Examine the current repository structure completely
3. Compare existing file references with actual repository content
4. Identify outdated, missing, or incorrect references
5. Note any structural issues with the current file

Step 2: Content Planning

1. Determine if the primary purpose statement needs updates
2. Review and update the summary blockquote if needed
3. Plan additions for new files and directories
4. Plan removals for outdated or moved content
5. Reorganize sections if needed for better clarity

Step 3: File Updates

…