react-flow
Skill7 starsChanged 46 days agoMITView on GitHub
Analyze, repair, migrate, and scaffold @xyflow/react codebases. Use when users ask to debug React Flow behavior, fix node/edge state wiring, improve type safety or performance, upgrade legacy React Flow APIs, preserve persisted graph compatibility, or generate a complete React Flow starter from scratch.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- udaykumar-dhokia/mcp-flowtheir own version, first seen Nov 15, 2026
- noeltock/react-flowtheir own version, first seen Oct 13, 2026
- SnowBeatRain/skillstheir own version, first seen Oct 12, 2026
- framara/react-flow-skilltheir own version, first seen Sep 28, 2026
- ryonakae/sheltietheir own version, first seen Aug 4, 2026
- shep-ai/sheptheir own version, first seen Apr 14, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- shep-ai/shep★ 277same name
- framara/react-flow-skill★ 55same name
- SnowBeatRain/skills★ 3same name
- udaykumar-dhokia/mcp-flow★ 2same name
- ryonakae/sheltie★ 1same name
- noeltock/react-flow★ 0same name
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 repository83 other files it gives its agents.
- AGENTS.mdAGENTS.md
- accessibility-enforcerSkill
- access-policy-designerSkill
- adaptive-guardSkill
- agent-reviewerSkill
- anti-ai-slop-designSkill
- api-mock-designerSkill
- api-observability-plannerSkill
- app-store-reviewerSkill
- ask-first-act-laterSkill
- assumption-checkerSkill
- auth-flow-designerSkill
- b2b-founder-roadmapSkill
- brand-name-labSkill
- breaking-change-detectorSkill
- changelog-generatorSkill
- checkpoint-guardianSkill
- claude-style-codingSkill
- claw-integration-designSkill
- context-compressorSkill
- contract-first-designerSkill
- coolify-orchestratorSkill
- crash-analystSkill
- data-lineage-tracerSkill
- data-maskerSkill
- deep-link-architectSkill
- design-intelligenceSkill
- design-md-enforcerSkill
- ecosystem-apiSkill
- ecosystem-databaseSkill
- ecosystem-mobileSkill
- ecosystem-orchestrationSkill
- ecosystem-productSkill
- ecosystem-reasoningSkill
- ecosystem-securitySkill
- ecosystem-webSkill
- error-recoverySkill
- fth-design-crafterSkill
- geo-auditorSkill
- geo-optimizerSkill
- index-advisorSkill
- jev-orchestratorSkill
- mastermind-loggerSkill
- memory-ledgerSkill
- migration-strategistSkill
- mobile-perf-auditorSkill
- mobile-security-auditorSkill
- multi-brain-debateSkill
- multi-brain-expertsSkill
- multi-brain-scoreSkill
- multi-brainSkill
- offline-sync-designerSkill
- onboarding-designerSkill
- output-criticSkill
- parallel-plannerSkill
- pgbouncer-architectSkill
- plan-hardenerSkill
- plan-implement-verify-recoverSkill
- proje-analizcisiSkill
- project-analyzerSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
21 rules. 0 are common, 8 are distinctive, and 13 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
13
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 27
Ensure onNodesChange, onEdgesChange, and onConnect are correctly bound.
- Very specific: line 30
Keep nodeTypes and edgeTypes references stable.
- Distinctive: line 36
Run migration pass when legacy APIs are present.
- Distinctive: line 39
Add migration guard for old payload versions when needed.
- Distinctive: line 42
Ensure resulting scaffold compiles in a standard TS React setup.
- Distinctive: line 44
Run available tests or static checks.
- Distinctive: line 45
If checks are missing, provide manual verification steps.
- Distinctive: line 50
Keep node and edge ids stable across operations and persistence cycles.
- Distinctive: line 51
Avoid introducing a second state manager unless explicitly requested.
- Distinctive: line 52
Keep templates framework-agnostic unless the repository enforces a framework.
- Very specific: line 53
Prefer typed interfaces over any for flow data payloads.
- Very specific: line 57
Use references/CHECKLIST.md for systematic auditing.
- Very specific: line 58
Use references/FIX_PATTERNS.md for common issue-to-fix mapping.
- Very specific: line 59
Use references/EXAMPLES.md for prompt and output patterns.
- Very specific: line 60
Use references/MIGRATION_CHECKLIST.md and references/API_RENAMES.md for upgrade work.
- Very specific: line 61
Use references/MIGRATION_EXAMPLES.md for migration request patterns.
- Very specific: line 65
Start from templates/Flow.tsx.tmpl for baseline flow container.
- Very specific: line 66
Start from templates/nodeTypes.tsx.tmpl and templates/edgeTypes.tsx.tmpl for typed registries.
- Very specific: line 67
Use templates/layout.ts.tmpl for deterministic starter layout behavior.
- Very specific: line 68
Use templates/migration-plan.md.tmpl for patch-by-patch upgrade planning.
- Very specific: line 69
Use templates/compat-adapter.ts.tmpl when backward compatibility is required.
“Common” is measured: kept by at least 6 in 10 of the 5 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 Repair, Migration, And Build Protocol
Execute this protocol in order. Keep fixes small, reversible, and validated.
Required Outputs
- Produce a short audit report of the current React Flow architecture.
- Produce a prioritized fix list with risk and expected impact.
- Apply safe fixes in small patches when requested.
- Generate missing typed scaffolding when the project is incomplete.
- Report verification results and any residual risks.
Workflow
- Discover project shape.
- Locate all React Flow usage (
ReactFlow,useNodesState,useEdgesState,addEdge, custom node/edge components). - Confirm framework/runtime details (
vite,next, TypeScript config, lint setup).
- Locate all React Flow usage (
- Validate graph model contracts.
- Centralize
NodeandEdgetype definitions. - Validate id strategy,
dataschema stability, and custom type names.
- Centralize
- Validate state and event wiring.
- Ensure
onNodesChange,onEdgesChange, andonConnectare correctly bound. - Detect duplicated or conflicting state sources.
- Ensure
- Validate rendering and performance.
- Keep
nodeTypesandedgeTypesreferences stable. - Detect avoidable re-renders and unsafe inline object creation in hot paths.
- Keep
- Apply auto-fixes.
- Apply highest-impact, low-risk fixes first.
- Preserve behavior unless an explicit bug fix requires a behavior change.
- Include migration notes for any public API or schema changes.
- Run migration pass when legacy APIs are present.
- Detect legacy package/import usage and map to modern
@xyflow/react. - Migrate types first, then runtime wiring, then persistence compatibility.
- Add migration guard for old payload versions when needed.
- Detect legacy package/import usage and map to modern
- Scaffold from scratch when needed.
- Generate a minimal typed baseline with custom node support and layout helper.
- Ensure resulting scaffold compiles in a standard TS React setup.
- Verify.
- Run available tests or static checks.
- If checks are missing, provide manual verification steps.
Guardrails
- Preserve existing business logic unless the bug requires change.
- Keep node and edge ids stable across operations and persistence cycles.
- Avoid introducing a second state manager unless explicitly requested.
- Keep templates framework-agnostic unless the repository enforces a framework.
- Prefer typed interfaces over
anyfor flowdatapayloads.
References
- Use
references/CHECKLIST.mdfor systematic auditing. - Use
references/FIX_PATTERNS.mdfor common issue-to-fix mapping. - Use
references/EXAMPLES.mdfor prompt and output patterns. - Use
references/MIGRATION_CHECKLIST.mdandreferences/API_RENAMES.mdfor upgrade work. - Use
references/MIGRATION_EXAMPLES.mdfor migration request patterns.
Templates
- Start from
templates/Flow.tsx.tmplfor baseline flow container. - Start from
templates/nodeTypes.tsx.tmplandtemplates/edgeTypes.tsx.tmplfor typed registries. - Use
templates/layout.ts.tmplfor deterministic starter layout behavior. - Use
templates/migration-plan.md.tmplfor patch-by-patch upgrade planning. - Use
templates/compat-adapter.ts.tmplwhen backward compatibility is required.
🔗 Next Steps & Handoffs
<!-- BEGIN GENERATED: handoffs (generated from the ecosystem workflow map by build_ecosystems.py — do not edit by hand) -->Ecosystem: @ecosystem-web — Web, Design & Delivery.
Direct handoffs:
@claude-style-coding— The flow editor needs product-level UX polish.
Handoff contract: pass results to the next skill through an inline Handoff block in your reply with the fields skill, workflow, created_at, inputs, summary, and next (the handoff contract of @ecosystem-web). If a next skill is not installed, continue with its step from the ecosystem map, or install it with npx skills add fatih-developer/fth-skills --skill <name> after the user agrees.
<!-- END GENERATED: handoffs -->Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
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.

