docs
/docs
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.
- Author
- pmndrs ↗
- Repository
- claude-code-plugin ↗
- Licence
- MIT
- Last repository change
- 14.08.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 14.08.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
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.
Original author 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.
How it works
- Always index first
- Coverage
- Budget
SKILL.md preview
---
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.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · pmndrs/claude-code-plugin | 95 | MIT |
| tanstack/ai | 100 | MIT |
| mthines/agent-skills | 100 | MIT |
| lilly-logic-labs/lll-skills | 100 | MIT |
| kriscard/kriscard-claude-plugins | 100 | MIT |
| imgly/agent-skills | 100 | MIT |
| kriscard/Skills | 100 | MIT |
| The01Geek/prflow | 100 | MIT |
| grimoire-rs/grimoire | 100 | Apache-2.0 |
Database snapshot: 13.11.2026 · package version 5979460d47dd (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100r3f-best-practices
React Three Fiber (R3F) and Poimandres ecosystem best practices. Use when writing, reviewing, or optimizing R3F code. Triggers on tasks involving @react-three/fiber, @react-three/drei, zustand, @react-three/postprocessing, @react-three/rapier, or leva. - 100react-three-fiber-patterns
Build interactive 3D experiences in React using react-three-fiber (R3F), drei helpers, and shader integration. Covers scene composition, performance optimization, and animation patterns. Triggers on R3F development, React + Three.js, or declarative 3D scene requests. - 100threejs-react-three-fiber
Building three.js scenes from React with React Three Fiber and drei: renderer setup, the scene graph as JSX, frame-loop, state and loading hooks, pointer events, and adaptive performance, on WebGL or with WebGPU and TSL. Use when writing React components that render three.js. - 90local-react-three-fiber-game-abb82834
Build React-hosted 3D browser games with React Three Fiber. Use when the user wants pmndrs-based scene composition, shared React state, and 3D HUD integration inside a React app. - 91webmaker-drei
Add Drei helpers to React Three Fiber websites for loading glTF, camera controls, lighting, and performance. Use for /webmaker-drei or an existing R3F scene that needs reusable scene components. - 100drei
Drei (@react-three/drei) is the helper library for React Three Fiber with ready-made 3D components: orbit controls, environment lighting, text, HTML overlays, model and texture loaders, instancing and performance tools. Use when someone asks to "add OrbitControls", "load a GLTF…