documentation-lookup

Files (1)

• SKILL.md

SKILL.md (first lines)

# Documentation Lookup

Use current official documentation instead of relying on memory when the answer depends on a library, framework, API, or version.

## Workflow

1. Identify the exact project, package, and version from the request or local dependency files.
2. Prefer an installed documentation set, package source, or purpose-built connector, API, or CLI that reaches the official primary source.
3. Read only the pages needed to answer the question.
4. State the version or documentation date when it affects the answer.
5. Cite the official page or local source path used.

If a current official source is unavailable, say what could not be verified and do not guess. Do not install or recommend an unrelated documentation service as a workaround.

## Selection Rules

- Prefer the library owner's documentation over tutorials, aggregators, and community mirrors.
- Match version-specific questions to the same version of the documentation.
- Keep examples limited to the user's requested API and environment.
- Separate verified documentation facts from implementation advice.

From foryourhealth111-pixel/Vibe-Skills, Apache-2.0.

More from foryourhealth111-pixel/Vibe-Skills