Token导航 LogoToken导航

Agent Skill · 前端设计

react-flow(React flow 前端)

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

react-flow 是前端设计类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为操作浏览器;许可证信息还不明确,第三方扫描有提醒项,按安装量在前端设计类的 10,216 个 Skill 里排第 1,468。

总安装 5,645周安装 240GitHub Stars 21下载 1,978核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/framara/react-flow-skill --skill react-flow

这个 Skill 是做什么的

前端设计类 Skill 关注页面结构、视觉规范和组件写法,输出通常是可运行的界面代码。

react-flow 用于辅助前端页面、组件和交互逻辑的开发与维护。适合生成或审查 React、Next.js、Vue、Tailwind、CSS 等相关代码。通过 npx skills add 命令从指定 GitHub 仓库安装,需确认权限和维护状态。使用时需结合项目现有设计系统和路由方式,避免生成孤立片段。

涉及页面改动时应配合本地预览和构建检查确认视觉效果。

来源仓库内路径:skills/react-flow

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/framara/react-flow-skill --skill react-flow;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要操作浏览器,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

react-flow 怎么安装?

在终端执行 npx skills add https://github.com/framara/react-flow-skill --skill react-flow。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

react-flow 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

react-flow 需要什么权限?

权限级别是操作浏览器。该 Skill 可能涉及浏览器控制能力,使用时可能读取或操作网页内容,需要在受控环境中确认权限边界。

react-flow 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

react-flow 用的人多吗?

公开数据是累计安装 5,645 次,近一周安装 240 次,下载 1,978 次,GitHub 21 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

react-flow 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理前端设计类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

前端设计类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
frontend-design

前端设计 · Codex、Claude

8,823,360126,072只读MIT通过
vercel-composition-patterns

Vercel 组合模式 · Codex、Claude

3,858,81625,893需要联网MIT通过
vercel-react-native-skills

Vercel React native skills 前端 · Codex、Claude

2,468,66425,878只读MIT通过
adapt

adapt 搜索 · Codex、Claude

2,027,04023,125操作浏览器未明确通过
bolder

bolder 分析 · Codex、Claude

2,004,28823,130只读未明确通过
react-flow

React flow 前端 · 本页

5,64521操作浏览器未明确有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

React Flow

Overview

Use this skill to build, customize, debug, and optimize interactive node-based UIs with React Flow (@xyflow/react v12+). Covers everything from basic setup to advanced patterns like computed flows, sub-flows, and external layout integration.

Agent behavior contract (follow these rules)

  1. Always import from @xyflow/react — never from legacy reactflow or react-flow-renderer packages.
  2. Always import the stylesheet: import '@xyflow/react/dist/style.css' (or base.css for custom styling frameworks).
  3. The <ReactFlow> parent container must have explicit width and height — this is the #1 cause of blank canvases.
  4. Define nodeTypes and edgeTypes objects outside component bodies or wrap in useMemo to prevent re-renders.
  5. Prefer custom nodes over built-in nodes — the React Flow team explicitly recommends this.
  6. Use the nodrag class on interactive elements inside custom nodes (inputs, buttons, selects).
  7. Use nowheel class on scrollable elements inside custom nodes to prevent zoom interference.
  8. When hiding handles, use visibility: hidden or opacity: 0 — never display: none (breaks dimension calculation).
  9. When using multiple handles of the same type on a node, always assign unique id props.
  10. After programmatically adding/removing handles, call useUpdateNodeInternals to refresh the node.
  11. Always create new objects when updating node/edge state — mutations are not detected by React Flow.
  12. Prefer controlled flows (with onNodesChange/onEdgesChange/onConnect) for any non-trivial application.

First 60 seconds (triage template)

  • Clarify the goal: new flow setup, custom nodes/edges, state management, layout, performance, styling, E2E testing, advanced patterns (undo/redo, copy/paste, computed flows, collaboration), or debugging.
  • Collect minimal facts:

- React Flow version (v12+ uses @xyflow/react) - TypeScript or JavaScript - State management approach (local state, Zustand, Redux) - Number of nodes expected (affects performance strategy) - Styling approach (CSS, Tailwind, styled-components)

  • Branch quickly:

- migrating from legacy reactflow or react-flow-renderer -> package rename, import changes, API differences - blank canvas or missing nodes -> container dimensions or missing CSS import - edges not rendering -> missing handles, missing CSS, or display: none on handles - re-renders or sluggish performance -> nodeTypes defined inside component, missing memoization - connecting nodes not working -> missing onConnect handler or handle configuration - layout/positioning -> external layout library integration (dagre, elkjs) - type errors -> TypeScript generic patterns for Node/Edge types

Routing map (read the right reference fast)

  • Migrating from reactflow or react-flow-renderer to @xyflow/react v12 -> references/migration.md
  • Installation, setup, first flow, node/edge objects -> references/fundamentals.md
  • Custom node components, Handle, multiple handles, drag handles -> references/custom-nodes.md
  • Custom edge components, path utilities, edge labels, markers -> references/custom-edges.md
  • Event handlers, callbacks, connection validation, selection, keyboard -> references/interactivity.md
  • Controlled vs uncontrolled, Zustand integration, state update patterns -> references/state-management.md
  • Node/Edge types, generics, union types, type guards -> references/typescript.md
  • External layout libraries (dagre, elkjs, d3), sub-flows, parent-child -> references/layouting.md
  • Background, Controls, MiniMap, Panel, NodeToolbar, NodeResizer, hooks -> references/components-and-hooks.md
  • Memoization, render optimization, theming, CSS variables, Tailwind -> references/performance-and-styling.md
  • Common errors, debugging, edge display issues, Zustand warnings -> references/troubleshooting.md
  • Playwright E2E tests, flow selectors, drag/viewport/connection testing -> references/e2e-testing.md
  • Undo/redo, copy/paste, computed flows, dynamic handles, save/restore, collaboration -> references/advanced-patterns.md
  • Context menu add node, drag-and-drop sidebar, detail panel, export as image -> references/recipes.md

Common pitfalls -> next best move

  • Blank canvas with no errors -> parent container has no height; set explicit height: 100vh or equivalent.
  • nodeTypes / edgeTypes warning -> move object definition outside component body or wrap in useMemo.
  • Edges render but in wrong position -> handles use display: none; switch to opacity: 0.
  • Cannot interact with inputs inside nodes -> add className="nodrag" to interactive elements.
  • Nodes snap back after drag -> onNodesChange not wired up or not applying changes correctly.
  • Connection line appears but edge never creates -> onConnect handler missing or not calling addEdge.
  • Multiple handles on same side overlap -> position them with CSS (top offset) and assign unique ids.
  • State updates don't reflect in nodes -> creating mutations instead of new objects; spread operator required.
  • Zustand context warning -> two versions of @xyflow/react installed or missing <ReactFlowProvider>.
  • Sub-flow child nodes render behind parent -> ensure parent nodes appear before children in the nodes array.

Verification checklist

  • Confirm @xyflow/react/dist/style.css is imported (or base.css + custom styles).
  • Confirm parent container has explicit width and height.
  • Confirm nodeTypes / edgeTypes are stable references (defined outside component or memoized).
  • Confirm custom nodes use <Handle> components with proper type and position.
  • Confirm interactive elements inside nodes have nodrag class.
  • Confirm controlled flows wire up all three handlers: onNodesChange, onEdgesChange, onConnect.
  • Confirm state updates create new node/edge objects (no mutations).
  • Confirm TypeScript generics are applied to hooks and callbacks for type safety.
  • Confirm performance-sensitive flows memoize custom node/edge components with React.memo.

References

  • references/migration.md
  • references/fundamentals.md
  • references/custom-nodes.md
  • references/custom-edges.md
  • references/interactivity.md
  • references/state-management.md
  • references/typescript.md
  • references/layouting.md
  • references/components-and-hooks.md
  • references/performance-and-styling.md
  • references/troubleshooting.md
  • references/e2e-testing.md
  • references/advanced-patterns.md
  • references/recipes.md

平台分布

Codex

36.95%
按下载量换算731

Claude

31.05%
按下载量换算614

Cursor

19.75%
按下载量换算391

Gemini CLI

9.81%
按下载量换算194

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

操作浏览器

该 Skill 可能涉及浏览器控制能力,使用时可能读取或操作网页内容,需要在受控环境中确认权限边界。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills