Token导航 LogoToken导航TokenDH.com
研究检索需要联网clawhub未标认证来源可访问clear审计通过

reactReact 开发

Agent Skill

用于辅助前端页面、组件、样式和交互逻辑的开发与维护。它适合让 Agent 生成或审查 React、Next.js、Vue、Tailwind、CSS 等相关代码,整理组件结构,或定位布局和性能问题。使用时需要结合项目现有设计系统、路由和构建方式,避免只生成孤立片段;涉及页面改动时,应配合本地预览和构建检查确认视觉效果。

总安装

188,698

周安装

7,560

GitHub Stars

3

下载量

61,085
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:react(React 开发)
来源仓库:https://github.com/ivangdavila/react
安装命令:
openclaw skills install react
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install react

简介

完整的 React 19 工程、架构、服务器组件、钩子、Zustand、TanStack 查询、表单、性能、测试、生产部署。

SKILL.md

name
React
slug
react
version
1.0.4
homepage
https://clawic.com/skills/react
changelog
Added React 19 coverage, Server Components, AI Mistakes section, Core Rules, state management patterns, setup system
description
Full React 19 engineering, architecture, Server Components, hooks, Zustand, TanStack Query, forms, performance, testing, production deploy.

React

Production-grade React engineering. This skill transforms how you build React applications — from component architecture to deployment.

When to Use

  • Building React components, pages, or features
  • Implementing state management (useState, Context, Zustand, TanStack Query)
  • Working with React 19 (Server Components, use(), Actions)
  • Optimizing performance (memo, lazy, Suspense)
  • Debugging rendering issues, infinite loops, stale closures
  • Setting up project architecture and folder structure

Architecture Decisions

Before writing code, make these decisions:

DecisionOptionsDefault
RenderingSPA / SSR / Static / HybridSSR (Next.js)
State (server)TanStack Query / SWR / use()TanStack Query
State (client)useState / Zustand / JotaiZustand if shared
StylingTailwind / CSS Modules / styledTailwind
FormsReact Hook Form + Zod / nativeRHF + Zod

Rule: Server state (API data) and client state (UI state) are DIFFERENT. Never mix them.

Component Rules

// ✅ The correct pattern
export function UserCard({ user, onEdit }: UserCardProps) {
  // 1. Hooks first (always)
  const [isOpen, setIsOpen] = useState(false)
  
  // 2. Derived state (NO useEffect for this)
  const fullName = `${user.firstName} ${user.lastName}`
  
  // 3. Handlers
  const handleEdit = useCallback(() => onEdit(user.id), [onEdit, user.id])
  
  // 4. Early returns
  if (!user) return null
  
  // 5. JSX (max 50 lines)
  return (...)
}
RuleWhy
Named exports onlyRefactoring safety, IDE support
Props interface exportedReusable, documented
Max 50 lines JSXExtract if bigger
Max 300 lines fileSplit into components
Hooks at topReact rules + predictable

State Management

Is it from an API?
├─ YES → TanStack Query (NOT Redux, NOT Zustand)
└─ NO → Is it shared across components?
    ├─ YES → Zustand (simple) or Context (if rarely changes)
    └─ NO → useState

TanStack Query (Server State)

// Query key factory — prevents key typos
export const userKeys = {
  all: ['users'] as const,
  detail: (id: string) => [...userKeys.all, id] as const,
}

export function useUser(id: string) {
  return useQuery({
    queryKey: userKeys.detail(id),
    queryFn: () => fetchUser(id),
    staleTime: 5 * 60 * 1000, // 5 min
  })
}

Zustand (Client State)

// Thin stores, one concern each
export const useUIStore = create<UIState>()((set) => ({
  sidebarOpen: true,
  toggleSidebar: () => set((s) => ({ sidebarOpen: !s.sidebarOpen })),
}))

// ALWAYS use selectors — prevents unnecessary rerenders
const isOpen = useUIStore((s) => s.sidebarOpen)

React 19

Server Components (Default in Next.js App Router)

// Server Component — runs on server, zero JS to client
async function ProductList() {
  const products = await db.products.findMany() // Direct DB access
  return <ul>{products.map(p => <ProductCard key={p.id} product={p} />)}</ul>
}

// Client Component — needs 'use client' directive
'use client'
function AddToCartButton({ productId }: { productId: string }) {
  const [loading, setLoading] = useState(false)
  return <button onClick={() => addToCart(productId)}>Add</button>
}
Server ComponentClient Component
async/await ✅useState ✅
Direct DB ✅onClick ✅
No bundle sizeAdds to bundle
useState ❌async ❌

use() Hook

// Read promises in render (with Suspense)
function Comments({ promise }: { promise: Promise<Comment[]> }) {
  const comments = use(promise) // Suspends until resolved
  return <ul>{comments.map(c => <li key={c.id}>{c.text}</li>)}</ul>
}

useActionState (Forms)

'use client'
async function submitAction(prev: State, formData: FormData) {
  'use server'
  // ... server logic
  return { success: true }
}

function Form() {
  const [state, action, pending] = useActionState(submitAction, {})
  return (
    <form action={action}>
      <input name="email" disabled={pending} />
      <button disabled={pending}>{pending ? 'Saving...' : 'Save'}</button>
      {state.error && <p>{state.error}</p>}
    </form>
  )
}

Performance

PriorityTechniqueImpact
P0Route-based code splitting🔴 High
P0Image optimization (next/image)🔴 High
P1Virtualize long lists (tanstack-virtual)🟡 Medium
P1Debounce expensive operations🟡 Medium
P2React.memo on expensive components🟢 Low-Med
P2useMemo for expensive calculations🟢 Low-Med

React Compiler (React 19+): Auto-memoizes. Remove manual memo/useMemo/useCallback.

Common Traps

Rendering Traps

// ❌ Renders "0" when count is 0
{count && <Component />}

// ✅ Explicit boolean
{count > 0 && <Component />}
// ❌ Mutating state — React won't detect
array.push(item)
setArray(array)

// ✅ New reference
setArray([...array, item])
// ❌ New key every render — destroys component
<Item key={Math.random()} />

// ✅ Stable key
<Item key={item.id} />

Hooks Traps

// ❌ useEffect cannot be async
useEffect(async () => { ... }, [])

// ✅ Define async inside
useEffect(() => {
  async function load() { ... }
  load()
}, [])
// ❌ Missing cleanup — memory leak
useEffect(() => {
  const sub = subscribe()
}, [])

// ✅ Return cleanup
useEffect(() => {
  const sub = subscribe()
  return () => sub.unsubscribe()
}, [])
// ❌ Object in deps — triggers every render
useEffect(() => { ... }, [{ id: 1 }])

// ✅ Extract primitives or memoize
useEffect(() => { ... }, [id])

Data Fetching Traps

// ❌ Sequential fetches — slow
const users = await fetchUsers()
const orders = await fetchOrders()

// ✅ Parallel
const [users, orders] = await Promise.all([fetchUsers(), fetchOrders()])
// ❌ Race condition — no abort
useEffect(() => {
  fetch(url).then(setData)
}, [url])

// ✅ Abort controller
useEffect(() => {
  const controller = new AbortController()
  fetch(url, { signal: controller.signal }).then(setData)
  return () => controller.abort()
}, [url])

AI Mistakes to Avoid

Common errors AI assistants make with React:

MistakeCorrect Pattern
useEffect for derived stateCompute inline: const x = a + b
Redux for API dataTanStack Query for server state
Default exportsNamed exports: export function X
Index as key in dynamic listsStable IDs: key={item.id}
Fetching in useEffectTanStack Query or loader patterns
Giant components (500+ lines)Split at 50 lines JSX, 300 lines file
No error boundariesAdd at app, feature, component level
Ignoring TypeScript strictEnable strict: true, fix all errors

Quick Reference

Hooks

HookPurpose
useStateLocal state
useEffectSide effects (subscriptions, DOM)
useCallbackStable function reference
useMemoExpensive calculation
useRefMutable ref, DOM access
use()Read promise/context (React 19)
useActionStateForm action state (React 19)
useOptimisticOptimistic UI (React 19)

File Structure

src/
├── app/                 # Routes (Next.js)
├── features/            # Feature modules
│   └── auth/
│       ├── components/  # Feature components
│       ├── hooks/       # Feature hooks
│       ├── api/         # API calls
│       └── index.ts     # Public exports
├── shared/              # Cross-feature
│   ├── components/ui/   # Button, Input, etc.
│   └── hooks/           # useDebounce, etc.
└── providers/           # Context providers

Setup

See setup.md for first-time configuration. Uses memory-template.md for project tracking.

Core Rules

  1. Server state ≠ client state — API data goes in TanStack Query, UI state in useState/Zustand. Never mix.
  2. Named exports onlyexport function X not export default. Enables safe refactoring.
  3. Colocate, then extract — Start with state near usage. Lift only when needed.
  4. No useEffect for derived state — Compute inline: const total = items.reduce(...). Effects are for side effects.
  5. Stable keys always — Use item.id, never index for dynamic lists.
  6. Max 50 lines JSX — If bigger, extract components. Max 300 lines per file.
  7. TypeScript strict: true — No any, no implicit nulls. Catch bugs at compile time.

Related Skills

Install with clawhub install <slug> if user confirms:

  • frontend-design-ultimate — Build complete UIs with React + Tailwind
  • typescript — TypeScript patterns and strict configuration
  • nextjs — Next.js App Router and deployment
  • testing — Testing React components with Testing Library

Feedback

  • If useful: clawhub star react
  • Stay updated: clawhub sync

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

79.41%
按下载量换算48,508

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

未展示

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills