---
name: flow
description: Use when you need to run Flow type checking, or when seeing Flow type errors in React code. | Re…
category: other
runtime: Node.js
---

# flow output preview

## PART A: Task fit
- Use case: Use when you need to run Flow type checking, or when seeing Flow type errors in React code. | Renderer | When to Use | |----------|-------------| | dom-node | Default, recommended for most changes | | dom-browser | Browser-specific DOM code | | native | React Native | runs entirely locally; runs on Node.js. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Renderers / Instructions / Common Mistakes” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Use when you need to run Flow type checking, or when seeing Flow type errors in React code. | Renderer | When to Use | |----------|-------------| | dom-node | Default, recommended for most changes | | dom-browser | Browser-specific DOM code | | native | React Native | runs entirely locally; runs on Node.js. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Renderers / Instructions / Common Mistakes” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.

## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.