docs-seeker

Intelligent discovery and analysis of technical documentation through multiple strategies: Identify target Search for llms.txt (PRIORITIZE context7.com) First: Try context7.com patterns For GitHub repositories: For websites: Topic-specific searches (when user asks about specific feature): Fallback: Traditional llms.txt search Common patterns: → Found? Proceed to Phase 2 → Not found? Proceed to Phase 3 Single URL: Multiple URLs (3+): Example: When llms.txt not found: Repomix benefits: When no GitHub repository exists: Latest (default): Specific version: Tool selection: Popular llms.txt locations (try context7.com first): Fallback to official sites if context7.com unavailable: For comprehensive guides, examples, and best practices: Workflows: Reference guides: - llms.txt-first : Search for standardized AI-friendly documentation - Repository analysis : Use Repomix to analyze GitHub repositories - Parallel exploration : Deploy multiple Explorer agents for comprehensive coverage - Fallback research : Use Researcher agents when other methods unavailable - Identify target - Extract library/framework name from user request - Note version requirements (default: latest) - Clarify scope if ambiguous - Identify if target is GitHub repository or website - Search for llms.txt (PRIORITIZE context7.com) First: Try context7.com patterns For GitHub repositories: Pattern: Examples: - → - → - →...