react

A set of standards for writing and reviewing React with TypeScript, React being a library for building user interfaces and TypeScript being JavaScript with type checking.

In plain words
What is it for?
Building or reviewing React components, JSX, TSX, hooks, and TypeScript props. It covers cleanup, cancellation, and safe component structure.
Why use it?
It helps prevent mistakes with hooks, effects, component boundaries, asynchronous work, and typed properties.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/ndisisnd/cook/react
Any agent
npx skills add ndisisnd/cook --skill react
Clone the repo
git clone --depth 1 https://github.com/ndisisnd/cook

Made for: Claude Code, Codex.

Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,682 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00041 $0.01682
Opus 5 $0.00020 $0.00841
Sonnet 5 $0.00008 $0.00336
Haiku 4.5 $0.00004 $0.00168

Measured yesterday against content hash 50f921153486, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

react scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

standards/react/SKILL.md · 116 lines

How it starts

The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.

React

Load this file by default for any .tsx or .jsx task. Pull refs only when the task explicitly requires that depth — see the References section.

P0 — Hook Correctness

  • Dependency arrays must be exhaustive (exhaustive-deps). Never suppress the linter to silence a warning — fix the logic.
  • Objects, arrays, and functions in dependency arrays: first move creation inside the effect, hoist constants, or remove the effect. Use useMemo/useCallback only when identity stability is required or measured work is expensive.
  • useEffect is for syncing with external systems only. Derived data belongs in render; event-specific logic belongs in event handlers. Prefer framework data APIs, route loaders, TanStack Query, or SWR over raw fetch effects when available.
  • Effects must clean up subscriptions, timers, and event listeners. Use AbortController for cancellable fetches and stale-response guards for non-abortable async work.
  • Never call hooks inside conditions, loops, nested functions, event handlers, class components, callbacks passed to hooks, try/catch/finally, or after a conditional return.
  • Do not use useEffect to sync derived state — compute it during render instead.
  • Lazy-initialize expensive state: useState(() => compute()).
  • useMemo and useCallback: measure before adding. React Compiler may reduce manual memoization; keep manual memoization where identity is observable or profiling proves value.
  • useRef for mutable values that must not trigger re-renders (DOM nodes, timers, previous-value tracking).
  • useTransition / useDeferredValue for non-blocking UI updates that should not block input.
  • React 19+: use useEffectEvent for effect-local callbacks that need latest committed values without re-synchronizing the effect. Do not use it to hide real dependencies. For older React or non-effect callbacks, use the latest-ref pattern.

P0 — Component Basics

  • Function components only. No class components.
  • One exported component per file; keep small helper components module-local when they only serve that file. Prefer named exports. PascalCase names.
  • Treat ~250 lines as a review smell, not a hard rule. Split by responsibility before a component accumulates unrelated state, effects, or rendering branches.
  • No nested component definitions — define at module scope.
  • Use stable IDs as list keys; never use array index.
  • Use useId for generated accessibility IDs; never use it for list keys.
  • Prefer ternary (cond ? <A /> : <B />) over && for conditional rendering — && renders 0 when the left side is falsy.
  • Define event handlers before the return statement; avoid non-trivial inline arrow functions in JSX props.
  • Do not thread props through components that do not use them — use composition, Context API, or a state manager when state crosses several layers.
  • Custom accordions, dialogs, menus, tabs, and compound widgets must implement keyboard interaction, focus management, and ARIA semantics or use a proven accessible primitive.

Read the full file on GitHub · 116 lines

Files

What ships with it

8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 116 lines · 41 tokens per session scan A 50f921153486

Subscribe to this mod's changes

react is a skill published in the GitHub repository ndisisnd/cook (2 stars, last pushed 21d ago), licensed MIT. It adds 41 tokens to every session and 1,682 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

pre-landing-review

Pre-landing PR review. Analyzes diff against the base branch for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues. Use when explicitly asked for the specialized pre-landing workflow. Product /review requests are handled by BitFun's unified Review mechanism instead.…

GCWing/BitFun · 74 tokens

wechat-article-writer

公众号/自媒体全流程。根据用户表述自动匹配:撰写文章、封面图、正文插图、风格提取。支持多种写作风格。当用户提到写公众号、技术博客、公众号封面、正文插图、步骤图、演示图、流程示意、分析写作风格、克隆文风、模仿爆款、提取风格时使用。详见 reference 目录。.

xstongxue/best-skills · 105 tokens

miniapp-dev

Develops, maintains, and generates BitFun MiniApps (Zero-Dialect Runtime). Use when (1) working on miniapp framework code under src/crates/assembly/core/src/miniapp/ or src/web-ui/src/app/scenes/miniapps/; or (2) generating / creating / designing a NEW MiniApp for the user — including any request like "做一个小应用 / 生成…

GCWing/BitFun · 143 tokens

vibe-research

Deep research and market validation for app ideas. Use when starting a new project, validating an idea, or when the user says "research my idea", "validate my app", or "help me start a new project".

KhazP/vibe-coding-prompt-template · 49 tokens

commit-push-pr

Commit selected local changes, push the branch, and create or update a GitHub pull request with BitFun attribution. Use when the user asks to 提交 PR、提代码、commit and push、开 PR、create a pull request, or wants a Claude Code-like one-command PR publishing flow from BitFun.

GCWing/BitFun · 68 tokens

investigate

Systematic debugging with root cause investigation. Four phases: investigate, analyze, hypothesize, implement. Iron Law: no fixes without root cause. Use when asked to "debug this", "fix this bug", "why is this broken", "investigate this error", or "root cause analysis". Proactively invoke this skill (do NOT debug…

GCWing/BitFun · 112 tokens