ReactBits Skill
You have access to the ReactBits MCP server via the following tools:
mcp__reactbits__list_categories — List all component categories
mcp__reactbits__list_components — List components, optionally filter by category (Animations, Backgrounds, Text Animations, Components, Buttons, Forms, Loaders), style (tailwind, css, default), limit
mcp__reactbits__search_components — Search components by query, filter by category, limit
mcp__reactbits__get_component — Get full source code for a component by name (slug), optionally specify style (tailwind, css, default)
mcp__reactbits__get_component_demo — Get usage example and demo code for a component by name
Website Builder Mode
When the user says they want to "build a website", "make a site", "create a landing page", "做一个网站", "帮我搭个页面", or any similar intent — DO NOT wait for them to specify what components they need. Instead, ASK these questions first:
- Purpose — 这个网站是做什么的?(个人作品集 / 公司官网 / 产品落地页 / 博客 / 活动页 / 其他)
- Style — 你喜欢什么风格?(极简 / 科技感 / 复古 / 可爱卡通 / 暗黑炫酷 / 商务专业)
- Color — 有偏好的主色调吗?(紫色 / 蓝色 / 绿色 / 暖色 / 黑白 / 让我推荐)
- Pages — 需要哪些页面?(首页 / 关于 / 作品展示 / 联系 / 博客 / 其他)
- Key Features — 有什么特别想要的功能?(3D 背景 / 粒子效果 / 滚动动画 / 视频展示 / 卡片交互 / 文字动画)
After getting answers, DO this:
- Search ReactBits for components that match their style and needs
- Recommend 3-5 components with brief descriptions
- Ask which ones they want to add
- Install and integrate them one by one
How to use
When the user asks about ReactBits components:
- List available components: Use
list_components or list_categories to show what's available
- Search for something specific: Use
search_components with the user's query
- Get source code: Use
get_component to retrieve the full component source
- Get demo/usage example: Use
get_component_demo to see how to use it
Integration workflow
When the user wants to add a component to their project:
- Get the component source via
get_component with the user's preferred style (tailwind or css)
- Get the demo code via
get_component_demo to understand usage
- Check dependencies — the component metadata includes required packages (framer-motion, GSAP, Three.js, etc.). Install any missing ones.
- Write the component file to the project's
components/ directory
- Import CSS if needed — if
hasCSS: true, create the corresponding CSS file
- Import and use the component in the appropriate page/section
Style preference
Always ask the user which style they prefer:
- Tailwind (recommended for this project) — uses Tailwind CSS classes
- CSS — uses separate CSS modules
- TypeScript — always use the TypeScript variant
Categories reference
| Category |
Count |
Common components |
| Text Animations |
23 |
BlurText, ShinyText, SplitText, ShuffleText, CircularText |
| Animations |
27 |
ClickSpark, BlobCursor, FadeContent, Crosshair, Cubes |
| Components |
35 |
Stack, FlowingMenu, GooeyNav, BounceCards, CircularGallery |
| Backgrounds |
35 |
Dither, ColorBends, GridScan, PixelSnow, LiquidEther |
| Buttons |
— |
Various animated button components |
| Forms |
— |
Animated form elements |
| Loaders |
— |
Loading animations |
1---2name: reactbits3description: Search, browse, and install animated React components from ReactBits.dev (135+ components). Use when the user wants to add UI effects, animations, backgrounds, or interactive components to their React/Next.js project.4---5
6# ReactBits Skill
7
8You have access to the ReactBits MCP server via the following tools:
9
10- `mcp__reactbits__list_categories` — List all component categories
11- `mcp__reactbits__list_components` — List components, optionally filter by `category` (Animations, Backgrounds, Text Animations, Components, Buttons, Forms, Loaders), `style` (tailwind, css, default), `limit`
12- `mcp__reactbits__search_components` — Search components by `query`, filter by `category`, `limit`
13- `mcp__reactbits__get_component` — Get full source code for a component by `name` (slug), optionally specify `style` (tailwind, css, default)
14- `mcp__reactbits__get_component_demo` — Get usage example and demo code for a component by `name`
15
16## Website Builder Mode
17
18**When the user says they want to "build a website", "make a site", "create a landing page", "做一个网站", "帮我搭个页面", or any similar intent — DO NOT wait for them to specify what components they need. Instead, ASK these questions first:**
19
201. **Purpose** — 这个网站是做什么的?(个人作品集 / 公司官网 / 产品落地页 / 博客 / 活动页 / 其他)
212. **Style** — 你喜欢什么风格?(极简 / 科技感 / 复古 / 可爱卡通 / 暗黑炫酷 / 商务专业)
223. **Color** — 有偏好的主色调吗?(紫色 / 蓝色 / 绿色 / 暖色 / 黑白 / 让我推荐)
234. **Pages** — 需要哪些页面?(首页 / 关于 / 作品展示 / 联系 / 博客 / 其他)
245. **Key Features** — 有什么特别想要的功能?(3D 背景 / 粒子效果 / 滚动动画 / 视频展示 / 卡片交互 / 文字动画)
25
26**After getting answers, DO this:**
271. Search ReactBits for components that match their style and needs
282. Recommend 3-5 components with brief descriptions
293. Ask which ones they want to add
304. Install and integrate them one by one
31
32## How to use
33
34When the user asks about ReactBits components:
35
361. **List available components**: Use `list_components` or `list_categories` to show what's available
372. **Search for something specific**: Use `search_components` with the user's query
383. **Get source code**: Use `get_component` to retrieve the full component source
394. **Get demo/usage example**: Use `get_component_demo` to see how to use it
40
41## Integration workflow
42
43When the user wants to add a component to their project:
44
451. **Get the component source** via `get_component` with the user's preferred style (tailwind or css)
462. **Get the demo code** via `get_component_demo` to understand usage
473. **Check dependencies** — the component metadata includes required packages (framer-motion, GSAP, Three.js, etc.). Install any missing ones.
484. **Write the component file** to the project's `components/` directory
495. **Import CSS if needed** — if `hasCSS: true`, create the corresponding CSS file
506. **Import and use** the component in the appropriate page/section
51
52## Style preference
53
54Always ask the user which style they prefer:
55- **Tailwind** (recommended for this project) — uses Tailwind CSS classes
56- **CSS** — uses separate CSS modules
57- **TypeScript** — always use the TypeScript variant
58
59## Categories reference
60
61| Category | Count | Common components |
62|----------|-------|-------------------|
63| Text Animations | 23 | BlurText, ShinyText, SplitText, ShuffleText, CircularText |
64| Animations | 27 | ClickSpark, BlobCursor, FadeContent, Crosshair, Cubes |
65| Components | 35 | Stack, FlowingMenu, GooeyNav, BounceCards, CircularGallery |
66| Backgrounds | 35 | Dither, ColorBends, GridScan, PixelSnow, LiquidEther |
67| Buttons | — | Various animated button components |
68| Forms | — | Animated form elements |
69| Loaders | — | Loading animations |