Flow
- 1k installs
- 247k repo stars
- Updated July 27, 2026
- facebook/react
flow is a Claude Code skill that runs Flow static type checking on React components across multiple renderers to catch type errors before runtime.
About
flow is an official skill from facebook/react that instructs agents to run yarn flow with a renderer argument—dom-node by default, or dom-browser, native, and fabric for platform-specific code. It reports type errors with file locations and supports comprehensive CI checks via yarn flow-ci when slower full validation is needed. Developers reach for flow when Flow type errors appear in React code or when validating renderer-specific changes in the React monorepo. The skill prevents common mistakes like running Flow without specifying a renderer.
- Runs `yarn flow` with renderer argument support
- 3 renderer modes: dom-node (default), dom-browser, native, fabric
- Reports exact file locations for every type error
- Supports fast local checks and comprehensive yarn flow-ci mode
- Explicitly flags common mistakes like missing renderer or ignored suppressions
Flow by the numbers
- 1,015 all-time installs (skills.sh)
- +18 installs in the week ending Jul 28, 2026 (Skillselion tracking)
- Ranked #522 of 2,184 Testing & QA skills by installs in the Skillselion catalog
- Security screen: HIGH risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
npx skills add https://github.com/facebook/react --skill flowAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1k |
|---|---|
| repo stars | ★ 247k |
| Security audit | 2 / 3 scanners passed |
| Last updated | July 27, 2026 |
| Repository | facebook/react ↗ |
How do you run Flow type checking on React renderers?
Run Flow static type checking on React components and catch type errors before they reach runtime.
Who is it for?
React contributors and maintainers working in the facebook/react monorepo who need renderer-aware Flow checks during development.
Skip if: TypeScript-only React projects or codebases that do not use Flow type annotations.
When should I use this skill?
The user needs Flow type checking or reports Flow type errors in React renderer code.
What you get
Flow type error report with file paths and renderer-specific validation results.
- Flow type error report
- Renderer-specific validation results
By the numbers
- Supports 4 Flow renderers: dom-node, dom-browser, native, and fabric
Files
Flow Type Checking
Arguments:
- $ARGUMENTS: Renderer to check (default: dom-node)
Renderers
| Renderer | When to Use |
|---|---|
dom-node | Default, recommended for most changes |
dom-browser | Browser-specific DOM code |
native | React Native |
fabric | React Native Fabric |
Instructions
1. Run yarn flow $ARGUMENTS (use dom-node if no argument) 2. Report type errors with file locations 3. For comprehensive checking (slow), use yarn flow-ci
Common Mistakes
- Running without a renderer - Always specify or use default
dom-node - Ignoring suppressions - Check if
$FlowFixMecomments are masking real issues - Missing type imports - Ensure types are imported from the correct package
Related skills
TddFollow test-driven development with a strict red-green-refactor loop when creating reliable features or fixing bugs.510k185k
Test Driven DevelopmentEnforce writing failing tests before any production implementation code.176k260kQaRun conversational QA sessions that turn user-reported bugs into well-written, domain-aware GitHub issues without manual ticket writing.164k185kMigrate To ShoehornAutomatically update TypeScript test files that rely on unsafe `as` type assertions by replacing them with type-safe partial objects from @total-typescript/shoehorn.151k185k
Webapp TestingVerify frontend behavior, debug UI issues, capture screenshots, and inspect logs of a running local web application using Playwright.121k164k
Playwright CliRun browser automation, generate element snapshots, inspect DOM attributes, and execute Playwright tests from the terminal.96.3k12.2kFAQ
Which Flow renderer should flow use by default?
flow defaults to the dom-node renderer via yarn flow dom-node when no argument is provided, which is recommended for most React DOM changes in the facebook/react repository.
When should developers run yarn flow-ci instead of yarn flow?
flow directs developers to yarn flow-ci for comprehensive Flow checking when slower full validation is acceptable, while yarn flow with a renderer suits routine local type checks.
Is Flow safe to install?
skills.sh reports 2 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.