react

A set of rules for writing React components, which are reusable pieces of a web interface. It covers component design, hooks, state, performance, and testing.

In plain words
What is it for?
Writing, reviewing, refactoring, debugging, or explaining React code and its tests.
Why use it?
It gives consistent guidance for deciding where data and behavior belong and helps avoid unnecessary complexity.

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/xobotyi/cc-foundry/react
Any agent
npx skills add xobotyi/cc-foundry --skill react
Clone the repo
git clone --depth 1 https://github.com/xobotyi/cc-foundry

Made for: Claude Code, Codex.

Per session 53 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,376 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. 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.00053 $0.04376
Opus 5 $0.00026 $0.02188
Sonnet 5 $0.00011 $0.00875
Haiku 4.5 $0.00005 $0.00438

Measured 2d ago against content hash 49855a77401a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

react scanned grade B with 1 finding 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 2d ago.

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.

Strips warnings and disclaimersmediumAnti-refusal

Omitting safety caveats hides risk from the user and is a common jailbreak preamble.

- Don't lecture or quote the rule — state what's wrong and how to fix it.
plugins/frontend/skills/react/SKILL.md · 402 lines

How it starts

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

React

Components are pure functions. State is minimal. Effects are escape hatches. If you reach for useEffect, verify you actually need it.

React rewards thinking in components: break UI into pieces, find minimal state, identify where it lives, and wire data flow from parent to child. References contain extended examples, rationale, and edge cases for each topic area.

References

  • Components${CLAUDE_SKILL_DIR}/references/components.md Composition, refs, metadata, custom elements
  • Hooks${CLAUDE_SKILL_DIR}/references/hooks.md Hook rules, custom hooks, useSyncExternalStore
  • State${CLAUDE_SKILL_DIR}/references/state.md Placement, reducers, context, actions
  • Performance${CLAUDE_SKILL_DIR}/references/performance.md Compiler, memoization, server components, streaming
  • Testing${CLAUDE_SKILL_DIR}/references/testing.md Query priority/variants, userEvent catalog, async patterns

Component Design

Thinking in React

Build UI in five steps:

  1. Break UI into a component hierarchy — each component does one thing.
  2. Build a static version first — props only, no state, no interactivity.
  3. Find minimal state — if it doesn't change, is passed from a parent, or can be computed, it is not state.
  4. Identify where state lives — find every component that renders based on the state, find their closest common parent, put state there.
  5. Add inverse data flow — pass state-setter callbacks down so children update parent state through event handlers.

Purity

React assumes every component is a pure function. Same props + same state = same JSX. Never mutate props, state, or variables declared before rendering.

  • Local mutation is fine. Creating and mutating objects/arrays within the same render is safe — the mutation is invisible outside that render.
  • Event handlers don't need to be pure — they run outside of rendering.

Component Structure

  • One component per file. Small helpers co-located in the same file are acceptable but extract when reused.
  • Prefer function declarations for components.
  • Do not use React.FC — it adds implicit children typing and complicates generics. Use function Component(props: Props).

Read the full file on GitHub · 402 lines

Files

What ships with it

6 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. 2d ago First seen · 402 lines · 53 tokens per session scan B 49855a77401a

Subscribe to this mod's changes

react is a skill published in the GitHub repository xobotyi/cc-foundry (20 stars, last pushed 2d ago), licensed MIT. It adds 53 tokens to every session and 4,376 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (strips warnings and disclaimers). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens