react-bits · philotheephilix — Claude Code skill: what it does, how to install
react-bits is a skill for Claude Code that adds animated UI components, text effects, and WebGL/canvas backgrounds to React projects. It activates when fetching current React Bits component code from the public registry.
MIT 617 installs ★ 10 updated 2026-09-28
npx skills add Philotheephilix/reactbits.dev-skill --skill react-bits -a claude-codeWhat react-bits does
The react-bits skill integrates animated components from the React Bits library into React projects. Instead of generating code from memory using training data, the skill retrieves current component source directly from the reactbits.dev public registry.
React Bits offers 165 animated components, including Text Animations, Animations, UI Components, and Backgrounds. Each component is available in four variants: JavaScript/TypeScript combined with CSS or Tailwind. It is crucial to always fetch live component code, as AI model training data can become outdated while the library is regularly updated. If the registry is unreachable, the skill will report this rather than attempting to generate code.
This skill requires Node.js to operate. Components are added using the node scripts/rb-add.mjs <Component> --variant <JS|TS>-<CSS|TW> --dest <path> script. This script writes source files to the specified directory (default src/components) and prints the exact npm install command for the component's dependencies. Direct curl requests can also fetch component JSON data or the full registry index. When using curl, it is important to verify that the response is valid JSON, not an HTML shell from the SPA.
What it helps with
- Add an animated UI component to a React project
- Integrate text effects or WebGL/canvas backgrounds
- Obtain current and correct React Bits component code
- Avoid AI agent code hallucinations
- Correctly install component dependencies
Example prompts for the agent
- Add the
Auroracomponent to my React project with TypeScript and Tailwind. - List all available React Bits components.
- Install the
PixelTrailcomponent with its dependencies.
How to install react-bits
1Skills CLI (Vercel)
npx skills add Philotheephilix/reactbits.dev-skill --skill react-bits -a claude-code2Manually: put the files in place
~/.claude/skills/react-bits/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/react-bits/
1Skills CLI (Vercel)
npx skills add Philotheephilix/reactbits.dev-skill --skill react-bits -a codex2Manually: put the files in place
.agents/skills/react-bits/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Philotheephilix/reactbits.dev-skill --skill react-bits -a cursor2Manually: put the files in place
.cursor/skills/react-bits/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Philotheephilix/reactbits.dev-skill react-bits2Manually: put the files in place
.github/skills/react-bits/SKILL.md1Skills CLI (Vercel)
npx skills add Philotheephilix/reactbits.dev-skill --skill react-bits -a gemini-cli2Platform CLI
gemini skills install https://github.com/Philotheephilix/reactbits.dev-skill --path react-bitsManually: put the files in place
.devin/skills/react-bits/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add Philotheephilix/reactbits.dev-skill --skill react-bits -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about react-bits
How to install react-bits in Claude Code?
To install react-bits in Claude Code, execute two commands: first npx skills add Philotheephilix/reactbits.dev-skill --skill react-bits -a claude-code, then ~/.claude/skills/react-bits/SKILL.md.
What does the react-bits skill do?
The react-bits skill helps add animated UI components, text effects, cursor/hover effects, and WebGL/canvas backgrounds to React projects. It fetches up-to-date component code directly from the React Bits public registry, preventing the use of stale data.
What do I need to run react-bits?
The skill requires Node.js to be installed. Internet access is also necessary to retrieve current data from reactbits.dev.
Source text
SKILL.md · MIT
---
name: react-bits
description: Use when adding an animated UI component, text effect, cursor/hover effect, or WebGL/canvas background to a React project via React Bits (reactbits.dev) — or when asked to recall/write a React Bits component's code, props, or install steps from memory instead of fetching it.
---
# React Bits
Fetches real, current component source from the React Bits public registry instead of recalling it from training data. React Bits (reactbits.dev, MIT + Commons Clause, by David Haz) publishes 165 animated components — Text Animations, Animations, Components, Backgrounds — each in 4 variants (JS/TS × CSS/Tailwind).
## The hard rule
**Never write React Bits component code from memory. Always fetch it live.**
Verified failure mode (baseline test, no skill): asked for Aurora + BlurText, an agent hallucinated plausible-looking code, guessed `framer-motion` as a dependency (the live package is `motion`), invented prop defaults, and only disclosed the guessing when explicitly asked. The code looked complete and shippable. It wasn't current.
Training data goes stale; this library updates variants in sync. If you can't reach the registry, say so — don't fall back to recalled code.
## Fetch
```bash
node scripts/rb-add.mjs <Component> [<Component>...] --variant <JS|TS>-<CSS|TW> --dest <path> [--install]
node scripts/rb-add.mjs --list # print all 165 names
```
Writes real source files to `--dest` (default `src/components`) and prints the exact `npm install` line for that component's dependencies (default variant: `TS-TW`). `--install` runs it for you.
No script access? Fetch directly — same registry, same rules:
```bash
curl -s https://reactbits.dev/r/<Name>-<JS|TS>-<CSS|TW>.json # one component, files[].content = source
curl -s https://reactbits.dev/r/registry.json # index, 660 entries, no source, no category field
```
**reactbits.dev is an SPA** — an unknown path still returns HTTP 200 with an HTML shell. A 200 status proves nothing; parse the body as JSON and check it before trusting it.
## Workflow
1. **Confirm the variant** — JS or TS, CSS or Tailwind. Default to matching the project's existing files; ask if genuinely ambiguous.
2. **Find the component** — grep [references/catalog.md](references/catalog.md) (offline, 165 entries with category + description + deps) or `--list`.
3. **Fetch it** with `rb-add.mjs` (above). Never hand-write the file.
4. **Read the fetched file's own prop type/interface before wiring it up.** Don't guess prop names or defaults even for a component you fetched — read what's actually in the file.
5. **Install the printed dependencies** (or pass `--install`).
## Gotchas
- **Scoped-package deps break naive parsing.** 10 components depend on scoped packages, e.g. `PixelTrail` → `@react-three/fiber@^9.3.0`. Splitting a dep string on `@` to get the name yields `""` for these. `rb-add.mjs` parses correctly (`/^(@[^/]+\/[^@]+|[^@]+)@?(.*)$/`); don't reimplement this by hand.
- **CSS variants are multi-file.** `JS-CSS`/`TS-CSS` ship a component file *and* a sibling `.css` file (both must be written). `JS-TW`/`TS-TW` are single-file with Tailwind utility classes.
- **No category field in the registry.** `registry.json` has name/title/deps/files only. Category (Text Animations / Animations / Components / Backgrounds) lives only in `references/catalog.md` (sourced from `reactbits.dev/llms.txt`).
- **`verbatimModuleSyntax` TS projects**: some fetched files import types alongside values in one `import {...}` statement (e.g. `import { motion, Transition } from 'motion/react'`) — split into a separate `import type {...}` if the project's tsconfig has `verbatimModuleSyntax: true`. This is a mechanical fix, not a reason to rewrite the component.
## Categories (165 total)
Text Animations (32) · Animations (36) · Components (44) · Backgrounds (53). Full list with one-line descriptions and dependencies: [references/catalog.md](references/catalog.md) — a GitHub Action regenerates it daily from the live registry, so it stays current without a skill update. Manual refresh: `node scripts/gen-catalog.mjs`.
## After installing
For a craft-bar review of the motion you just wired up (easing, duration, frequency-appropriateness, reduced-motion), the upstream repo ships separate skills at `DavidHDev/react-bits/AGENTS/SKILLS/` (`review-animations`, `improve-animations`, `find-animation-opportunities`, `apple-design`) — not bundled here, distinct concern (craft review vs. correct fetch/install).
© Philotheephilix · MIT · Philotheephilix/reactbits.dev-skill
Similar skills
All skills for Frontend and UI →react-bits by other authors comes first.