documentation-update-llms

LLM Documentation Update Guide

This prompt guides the systematic update of existing llms.md files to ensure accuracy, completeness, and technical correctness while preserving the document's optimization for LLM developers and AI assistants.

🎯 UPDATE OBJECTIVES:

1. VERIFY current project state and synchronize documentation
2. UPDATE technical information to reflect current versions and capabilities
3. VALIDATE all examples and integration patterns for functionality
4. MAINTAIN structural integrity optimized for AI consumption
5. ENSURE comprehensive coverage of all system capabilities

📋 LLM DOCUMENTATION UPDATE PROCESS:

STEP 1: Current State Analysis

Project State Verification:

echo "🔍 Current Project State Analysis"
echo "================================"

# Verify current structure and counts
find .cursor/prompts -name "*.mdc" | wc -l
find .cursor/rules -name "*.mdc" | wc -l

# Analyze prompt categories
echo "Prompt Categories:"
ls .cursor/prompts/

# Check rules available
echo "Available Rules:"
ls .cursor/rules/

# Verify key files exist
echo "Key Documentation Files:"
ls docs/standards/

Change Detection:

• New prompts added since last update
• Technology versions changed in project dependencies
• Project structure modifications affecting documentation
• Standards updates in documentation files
• Integration patterns that have evolved

Content Gap Analysis:

• Missing categories not yet documented
• Outdated examples that no longer work
• Incorrect counts of prompts/rules
• Broken references to files or standards
• Incomplete workflows missing steps

STEP 2: Technical Accuracy Validation

Technology Stack Verification:

# Check current versions
echo "🔧 Technology Stack Verification"
echo "==============================="

# Verify framework versions (if package.json exists)
if [ -f "package.json" ]; then
    echo "Package.json versions:"
    cat package.json | grep -E "(next|typescript|react|vitest|tailwind)"
fi

# Check for version info in documentation
echo "Documented versions in standards:"
grep -r "version" docs/standards/ | head -10