Stats
Actions
Tags
From project-lens
Search .lens feature docs by topic before starting any task. Returns the relevant feature doc so you have full context before touching code. Use this before every task involving an unfamiliar feature.
How this skill is triggered — by the user, by Claude, or both
Slash command
/project-lens:searchThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Find and load the relevant feature documentation before starting work.
Find and load the relevant feature documentation before starting work.
/lens:search search
/lens:search authentication
/lens:search match statistics
/lens:search documents upload
$ARGUMENTSbash ${CLAUDE_PLUGIN_ROOT}/scripts/search.sh "$ARGUMENTS" "$(pwd)"
⚠ UNCERTAIN markers — flag those to the user explicitlyThe script will output available features. Tell the user:
"No doc found for '[topic]'. Want me to scan the relevant files now?"
If yes: find the files with Grep and run /lens:scan on them.
Never start editing code related to a feature without first running this search. The search script does the heavy lifting via OpenRouter — your job is to read the output it returns.
npx claudepluginhub 0serenvale/project-lens --plugin project-lensGuides doc lookup and web search workflow for investigating libraries, APIs, or unfamiliar patterns before implementation.
Fetches live documentation and implementation guidance for any library, framework, or API. Invoked when the user asks for documentation, examples, or best practices.
Fetches up-to-date GitHub documentation for libraries, frameworks, and APIs via search and chunk/TOC retrieval for usage, references, configs.