# Context7 CLI

Tier 1 lookup commands. Not for Context7 skill registry management.

## Commands

If the user gave `/org/project` or `/org/project/version`, fetch docs with that
ID directly. Otherwise resolve the library first:

```bash
ctx7 library <name> "<specific query>"
ctx7 docs /org/project "<specific query>"
```

- Pass the user's real topic as the query in both commands, never a one-word
  placeholder.
- Pick the ID whose name and description match the topic; prefer a
  version-specific ID when the requested version appears. Ask when the library
  name is ambiguous.
- Quote only the relevant excerpts, and report the library ID and the matched
  version when visible.

## Missing CLI or authentication

If `ctx7` is not installed, run the same commands through `npx ctx7@latest` or
`bunx ctx7@latest`. If the CLI needs an API key, tell the user to set it in
their shell or secret manager; do not ask them to paste it into chat.

## Limits

- At most 3 `ctx7 library` calls and 3 `ctx7 docs` calls per question.
- Then report Tier 1 exhausted and continue to official sources.

# Official Sources

Tier 2 and Tier 3 details. Prefer docs for the exact installed version.

## Version evidence

Resolve the effective version, not only the declared one: account for
overrides, `replace` directives, enabled features, BOM-managed versions,
preview SDKs, and local forks.

## Version-pinned sources

| Ecosystem   | Version-pinned docs                                           | Registry facts worth checking                       |
| ----------- | ------------------------------------------------------------- | --------------------------------------------------- |
| JS/TS       | Library docs linked from npm; MDN for Web APIs; Node.js docs  | npm dist-tags (`latest` vs `next`), `exports` map   |
| Python      | `docs.python.org` for stdlib; project docs linked from PyPI   | "What's New" pages for stdlib changes by release    |
| Go          | `pkg.go.dev/<module>@<version>`                               | Module major version suffix (`/v2`) changes imports |
| Rust        | `docs.rs/<crate>/<version>`                                   | Items gated behind non-default features             |
| Java/Kotlin | Javadoc for the exact artifact version                        | Maven Central coordinates; BOM-managed versions     |
| .NET        | Microsoft Learn API browser with the version selector         | NuGet target frameworks                             |
| Elixir      | HexDocs for the exact version                                 | Hex package metadata                                |
| Swift       | Apple Developer Documentation; Swift Package Index            | Package platform requirements                       |

## GitHub fallback

1. Confirm the repository from registry metadata or official docs.
2. Read the tag that matches the installed version: `CHANGELOG*`,
   `MIGRATION*`, `README*`, `/docs`, and examples before source.
3. Use source and tests only to confirm undocumented behavior or signatures.
4. Cite the tag, file path, and line or section.
5. If only the default branch has docs, say they may not match the installed
   version.