react-flow-node-ts
Skill424 starsChanged 35 days agoMITView on GitHub
Create React Flow node components with TypeScript types, handles, and Zustand integration. Use when building custom nodes for React Flow canvas, creating visual workflow editors, or implementing node-based UI components.
3 other projects use a version of this, 3 of them edited.
Adopted by
Most recently taken up by
- microsoft/skillsedited, first seen Oct 13, 2026
- microsoft/agent-skillsedited, first seen Oct 8, 2026
- NaviAndrei/AgentFlow-Studioedited, first seen Jun 30, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 3
- microsoft/agent-skills★ 3.2k98% same
- microsoft/skills★ 3.2k98% same
- NaviAndrei/AgentFlow-Studio★ 198% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ant-designSkill
- maafwSkill
- mpe-background-artSkill
- shadcnSkill
- sync-reference-projectsSkill
- tauri-for-mpeSkill
- ui-ux-pro-maxSkill
- update-local-mfwSkill
- web-design-guidelinesSkill
- zustand-store-tsSkill
The file
We split this skill into the rules it gives an agent
8 rules. 2 are common, 3 are distinctive, and 3 are very specific to this project.
2
Common
Most of the 3 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 12
Create React Flow node components following established patterns with proper TypeScript types and store integration.
- Distinctive: line 21
Start with api-reference/index.md for an overview.
- Distinctive: line 24
Start with learn/index.md for the quick start.
- Distinctive: line 27
Start with ui/index.md for setup and usage.
- Very specific: line 83
Add type to src/frontend/src/types/index.ts
- Very specific: line 84
Create component in src/frontend/src/components/nodes/
- Very specific: line 86
Add defaults in src/frontend/src/store/app-store.ts
- Common: line 88
Add to AddBlockMenu and ConnectMenu
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
React Flow Node
Create React Flow node components following established patterns with proper TypeScript types and store integration.
Website: https://reactflow.dev/
References
This skill includes a local mirror of the React Flow official documentation under references/. Use it when you need detailed API signatures, guides, or UI component references without relying on network access:
- references/api-reference/ — Full API reference for components, hooks, types, and utilities.
- Start with api-reference/index.md for an overview.
- Common node-related entries: components/handle.md, components/node-resizer.md, types/node.md, hooks/use-nodes.md.
- references/learn/ — Tutorials, concepts, customization guides, and layouting best practices.
- Start with learn/index.md for the quick start.
- Relevant guides: learn/customization/custom-nodes.md, learn/layouting/layouting.md.
- references/ui/ — React Flow UI components and templates built on shadcn/ui.
- Start with ui/index.md for setup and usage.
Prefer the local references over the website when exact API behavior or TypeScript types matter, because the mirrored docs are pinned to the same version this skill targets.
Quick Start
Copy templates from assets/ and replace placeholders:
{{NodeName}}→ PascalCase component name (e.g.,VideoNode){{nodeType}}→ kebab-case type identifier (e.g.,video-node){{NodeData}}→ Data interface name (e.g.,VideoNodeData)
Templates
- assets/template.tsx - Node component
- assets/types.template.ts - TypeScript definitions
Node Component Pattern
export const MyNode = memo(function MyNode({
id,
data,
selected,
width,
height,
}: MyNodeProps) {
const updateNode = useAppStore((state) => state.updateNode);
const canvasMode = useAppStore((state) => state.canvasMode);
return (
<>
<NodeResizer isVisible={selected && canvasMode === "editing"} />
<div className="node-container">
<Handle type="target" position={Position.Top} />
{/* Node content */}
<Handle type="source" position={Position.Bottom} />
</div>
</>
);
});Type Definition Pattern
export interface MyNodeData extends Record<string, unknown> {
title: string;
description?: string;
}
export type MyNode = Node<MyNodeData, "my-node">;Integration Steps
- Add type to
src/frontend/src/types/index.ts - Create component in
src/frontend/src/components/nodes/ - Export from
src/frontend/src/components/nodes/index.ts - Add defaults in
src/frontend/src/store/app-store.ts - Register in canvas
nodeTypes - Add to AddBlockMenu and ConnectMenu
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

