Flow
Use when you need to run Flow type checking, or when seeing Flow type errors in React code.
$ npx promptcreek add flowAuto-detects your installed agents and installs the skill to each one.
What This Skill Does
This skill guides developers in using Flow for type checking in React projects. It provides instructions on how to run Flow with different renderers and report type errors. It helps ensure code correctness and prevent runtime errors by enforcing static typing.
When to Use
- Preventing runtime errors.
- Enforcing type safety.
- Improving code maintainability.
- Catching type-related bugs early.
- Adding type annotations to existing code.
- Refactoring code with type checking.
Key Features
Installation
$ npx promptcreek add flowAuto-detects your installed agents (Claude Code, Cursor, Codex, etc.) and installs the skill to each one.
View Full Skill Content
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
- Run
yarn flow $ARGUMENTS(usedom-nodeif no argument) - Report type errors with file locations
- 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
Supported Agents
Attribution
Details
- License
- MIT
- Source
- admin
- Published
- 3/18/2026
Tags
Related Skills
Agent Protocol
Inter-agent communication protocol for C-suite agent teams. Defines invocation syntax, loop prevention, isolation rules, and response formats. Use when C-suite agents need to query each other, coordinate cross-functional analysis, or run board meetings with multiple agent roles.
Agent Workflow Designer
Agent Workflow Designer
CTO Advisor
Technical leadership guidance for engineering teams, architecture decisions, and technology strategy. Use when assessing technical debt, scaling engineering teams, evaluating technologies, making architecture decisions, establishing engineering metrics, or when user mentions CTO, tech debt, technical debt, team scaling, architecture decisions, technology evaluation, engineering metrics, DORA metrics, or technology strategy.