跳到主内容
智客 ZICQ

技能库 智客分类:Agent 工作流 react

React

如何与 React 有效工作, 开发前端组件时总是使用

31 安装量

官方网址:skills.sh

技能介绍

先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。

做什么

如何与 React 有效工作, 开发前端组件时总是使用

何时用

开发前端组件

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:React、Instructions、Component Structure、Page Props from Controllers、TypeScript Conventions、React 19 + React Compiler。

文件分析

文件分析:这是一份仅含 SKILL.md 的指令型技能,代理激活后整份正文进入上下文。

官方 description(原文)

How to work effectively with React, always use when developing frontend components

ReactInstructionsComponent StructurePage Props from ControllersTypeScript ConventionsReact 19 + React CompilerState ManagementEvent HandlersConditional RenderingFile Naming

来源分类:skills.sh agent-skill

SKILL.md 与 Agent 调用

官方规范 ↗
name
react
description
How to work effectively with React, always use when developing frontend components
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。

具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。

把 Agent Skill「react」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-285e84d05281faa9-%E5%8F%8D%E5%BA%94.html
请存为 .cursor/skills/react/SKILL.md 或 .claude/skills/react/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。

GitHub 完整包 ↗

终端安装 · Skills CLI

需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。

npx skills add 'https://github.com/markhamsquareventures/essentials' --list

npx skills add 'https://github.com/markhamsquareventures/essentials' --skill 'react'

CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。

阅读排版
--- name: react description: How to work effectively with React, always use when developing frontend components --- # React ## Instructions This project uses React 19 with TypeScript and the React Compiler enabled via `babel-plugin-react-compiler`. ### Component Structure - Pages live in `resources/js/pages/` and are rendered via Inertia - Shared components live in `resources/js/components/` - UI primitives (shadcn/ui) live in `resources/js/components/ui/` - Custom hooks live in `resources/js/hooks/` ### Page Props from Controllers Always receive page data as props from the Laravel controller via Inertia. Do NOT fetch data client-side or use `useEffect` to load page data. // In Laravel controller public function edit(Project $project): Response { return Inertia::render('projects/edit', [ 'project' => $project->load('client'), 'clients' => Client::orderBy('name')->get(), ]); } // In React page component import { Project, Client } from '@/types'; interface EditProjectProps { project: Project; clients: Client[]; } export default function EditProject({ project, clients }: EditProjectProps) { return ( {/* Form fields using project and clients data */} ); } This pattern ensures: - **State consistency** - The server is the single source of truth; no client-side caching or stale data issues - Data is loaded server-side before the page renders - No loading states needed for initial page data - SEO-friendly server-rendered content - Type-safe props matching controller output ### TypeScript Conventions - All component props should be typed explicitly - Use interfaces for object shapes, defined in `resources/js/types/index.d.ts` - Prefer `React.ComponentProps<"element">` for extending native element props - Use path aliases: `@/components`, `@/hooks`, `@/lib`, `@/types` import { cn } from '@/lib/utils'; interface CardProps { title: string; description?: string; className?: string; children: React.ReactNode; } export function Card({ title, description, className, children }: CardProps) { return (

{title}

{description &&

{description}

} {children}
); } ### React 19 + React Compiler - The React Compiler automatically memoizes components and hooks - Do NOT manually add `useMemo`, `useCallback`, or `React.memo` unless profiling shows a specific need - Write straightforward code and let the compiler optimize ### State Management - Use React's built-in `useState` and `useReducer` for local state - Use Inertia's shared data for server-provided state (accessed via `usePage()`) - For form state, use the Inertia `` component (see inertia skill) import { usePage } from '@inertiajs/react'; import { SharedData } from '@/types'; export function UserGreeting() { const { auth } = usePage().props; return Hello, {auth.user.name}; } ### Event Handlers - Use inline arrow functions for simple handlers - Extract to named functions only when logic is complex or reused ### Conditional Rendering - Use early returns for guard clauses - Prefer `&&` for simple conditionals, ternaries for if/else - Use separate components for complex conditional logic // Early return for loading state function DataDisplay({ data, isLoading }: Props) { if (isLoading) { return ; } return (
{data.items.length > 0 && } {data.error ? : }
); } ### File Naming - Components: PascalCase (`UserCard.tsx`) - Hooks: camelCase with `use` prefix (`useClipboard.ts`) - Utilities: camelCase (`formatDate.ts`) - Pages: kebab-case matching the route (`edit.tsx`, `create.tsx`, `index.tsx`)

相关技能

Agent 工作流

Skill Creator

创造有效技能指南。 当用户想创造出新的技能(或更新现有的技能),以专业知识,工作流程,或工具集成来扩展克洛德的能力时,应该使用这种技能.

Agent 工作流

Clawdhub

使用ClawdHub CLI搜索,安装,更新并发布从taladhub.com的代理技能. 需要获取苍蝇上的新技能时使用,将安装的技能同步到最新版本或特定版本,或者发布 npm-instainddhub CLI 的新/更新的技能文件夹.

Agent 工作流

Agent Team Orchestration

管弦乐团多代理团队,任务设定周期,交接协议,审查工作流程. 使用时间: (1)建立2+特派员队伍,具有不同专业,(2)确定任务路线和生命周期(收录框_ spec_建设_审查_完成),(3)在特派员之间制定交接协议,(4)建立审查和质量关口,(5)管理特派员之间的交流和文物共享.

Agent 工作流

Superpowers

Spec-first,TDD,子代理驱动的软件开发工作流程. 当:(1)构建任何新功能或应用——触发脑暴_计划_子代理执行回路,(2)调试出一个bug或测试失败——触发系统性的根起过程,(3)用户说"让我们构建","帮助我计划","我想添加X",或"这个被打破",(4)完成一个功…