# docs

Looks up official docs for React Three Fiber, drei and zustand before answering API questions, so answers match current signatures.

Skill by Poimandres (Zustand, R3F). Category: Knowledge.

## Install

Project (for this project only):

```sh
npx skills add pmndrs/claude-code-plugin --skill docs
```

Works with: Claude Code, Codex CLI, Cursor, Antigravity, Copilot CLI, opencode.

Global (for every project on this machine):

```sh
npx skills add pmndrs/claude-code-plugin --skill docs -g
```

Works with: Claude Code, Codex CLI, Cursor, Antigravity, Copilot CLI, opencode.

## Tags

- Runs on your computer: It runs as a program on your machine, with your access.

## Security audits

- Gen Agent Trust Hub: Pass
- Socket: Pass
- Snyk: Pass

Installs: 2. Installs counted by skills.sh. [Open on skills.sh](https://www.skills.sh/pmndrs/claude-code-plugin/docs)

## Source

[Open the source](https://github.com/pmndrs/claude-code-plugin/tree/HEAD/skills/docs). Checked 2026-10-10. This summary may contain AI-generated text, so it can be wrong. Check the source before you rely on it.

## SKILL.md

````markdown
---
name: docs
description: Look up the official pmndrs documentation before answering anything about react-three-fiber (R3F), drei or zustand — hooks, components, props, signatures, store patterns, migrations. Use it whenever code or an answer depends on one of these APIs, rather than recalling the API from memory.
---

# pmndrs docs

The `pmndrs` MCP server serves the official docs from docs.pmnd.rs. Prefer it over
memory: these libraries move fast and recalled APIs go stale.

The same server also serves the example gallery — see `pmndrs:examples`. The docs say
what an API takes; an example shows a whole scene that works. A question about how
something is put together usually wants both, in that order: find the demo, then
confirm against the docs that its API is still current.

## Always index first

Never guess a page path — `get_page_content` matches exactly, and route shapes differ
per library (`/api/hooks` for react-three-fiber, `/learn/guides/...` and
`/reference/apis/...` for zustand, `/abstractions/...` for drei). Read the index
resource, pick the path, then fetch.

1. `ReadMcpResourceTool` on `docs://{lib}/index` — one `{path} - {title}` per line,
   200–1,300 tokens.
2. `mcp__pmndrs__get_page_content` with `lib` and the exact `path` from step 1.

A bad path returns `MCP server error: Page not found: {path}` — re-read the index
instead of retrying variants.

## Coverage

Served — route these through the MCP: `react-three-fiber`, `drei`, `zustand`, `docs`
(the generator itself). Names are case-sensitive.

Anything else is unserved. The tool's `lib` enum advertises more libraries than that,
but the extra entries have no `llms-full.txt` behind them: every call fails and every
index comes back empty. Treat a library missing from the list above as absent, and use
WebFetch on its docs site. Fix in flight: pmndrs/docs#555.

## Budget

Pages run 1,200–4,000 tokens each. Fetch the one page that answers the question. If
three or more look relevant, read the index titles first and narrow — don't fetch the
set and sort it out afterwards.
````

- Previous: [workflow](https://syn4pse.dev/terminal/convex-backend-skill-workflow.md)
- Next: [aks-automatic-readiness](https://syn4pse.dev/terminal/aks-automatic-readiness.md)
- [Terminal](https://syn4pse.dev/terminal.md)
- [Suggest a change](mailto:terminal@syn4pse.dev?subject=Terminal%20suggestion)
