docs-searchlisted
Install: claude install-skill real-case/marvin-toolkit
# Docs Search
Find and synthesize project documentation so the user gets answers, not a list of files.
## Core principle
**Answer the question, not just find the file.** The user needs an explanation, not a file path. Search broadly, read the relevant sources, and synthesize a clear answer with citations.
## Phase 1 — Discover documentation landscape
Before searching for specific content, understand what documentation exists in the project.
Scan for documentation entry points:
```
# Root-level docs
README.md, CLAUDE.md, CONTRIBUTING.md, CHANGELOG.md, ARCHITECTURE.md
# Documentation directories
docs/, wiki/, doc/, documentation/, guides/, .github/
# Architecture Decision Records
docs/adr/, docs/decisions/, adr/
# API specifications
openapi.yaml, openapi.json, swagger.yaml, swagger.json, api-docs/
# Config and setup documentation
.env.example, docker-compose.yml (comments), Makefile (help targets)
```
Use `Glob` patterns to find what's available:
- `**/*.md` — all markdown files
- `**/docs/**` — everything under docs directories
- `**/*.{yaml,yml,json}` — potential API specs and config
Note what's present and what's missing — this shapes both the search and the response.
## Phase 2 — Search for the answer
Use multiple search strategies in parallel, not sequentially — cast a wide net first, then narrow down.
**By content (Grep):**
- Search for the user's query terms and related synonyms across docs and source code
- Try both the concept name and its common aliases