From docs
Load project documentation before code tasks (features, refactoring, bugs, architecture) to align with project patterns and conventions. Searches docs/, documentation/, .docs/ folders and loads relevant files into context.
How this skill is triggered — by the user, by Claude, or both
Slash command
/docs:docs-loaderThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Skip this skill when:**
Skip this skill when:
CRITICAL: You MUST use the Task tool with subagent_type=Explore for documentation loading. Do NOT use Glob or Read directly — delegate everything to the Explore agent in a single call.
Compose a prompt for the Explore subagent that includes:
docs/, documentation/, .docs/ or similar directoriesExample prompt:
The user wants to: [describe the task]
Find project documentation and return the contents of files relevant to this task.
1. Search for documentation directories: docs/, documentation/, .docs/
2. Read the index file (index.md or README.md) to understand the documentation structure
3. Based on the user's task, select and read the 2-4 most relevant documentation files
4. For each loaded doc, spot-check that key claims (file paths, function names, patterns) match the actual codebase
5. Return the full contents of each relevant file
If any documentation is outdated or contradicts the code, include a "⚠️ DOCS MISMATCH" section at the end of your response listing each discrepancy: which doc, what it claims, and what the code actually does.
Prioritize: architecture/overview docs first, then task-specific docs.
Use "medium" thoroughness.
The Explore agent will autonomously find, evaluate, and return the relevant documentation. You do not need to specify exact file paths — the agent will discover them.
Once the Explore agent returns, use the loaded documentation to:
If the agent reported "⚠️ DOCS MISMATCH":
Cite documentation when relevant: "According to docs/architecture/overview.md, the project uses a layered architecture..."
If during work you realize you need additional documentation, launch another Explore subagent with a focused prompt.
Task received
↓
Is it code-related? → NO → Skip this skill
↓ YES
↓
Will docs help? → NO → Skip this skill
↓ YES
↓
Launch Explore subagent (task context + docs discovery + read relevant files)
↓
Found? → NO → Ask user where docs are
↓ YES
↓
Begin task using documentation context
User request: "Add a new authentication endpoint"
Skill workflow:
docs/architecture/api-patterns.md and docs/security/auth.mdnpx claudepluginhub flopsstuff/flugins --plugin docsDiscovers project documentation roots and routes questions to the right doc based on query shape. Activates for queries about specs, ADRs, roadmap, bugs, or shared links.
Scans for project documentation files (AGENTS.md, CLAUDE.md, GEMINI.md, COPILOT.md, CURSOR.md, WARP.md, 15+ others), synthesizes unified guidance, and consolidates into AGENTS.md. Useful for codebase reviews and new projects.