General React fundamentals - components and JSX, props and state, the core hooks (useState/useEffect/useRef/useMemo/useCallback/useContext), composition, conditional and list rendering, and controlled inputs. The canonical "depends on React" reference.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
General React fundamentals - components and JSX, props and state, the core hooks (useState/useEffect/useRef/useMemo/useCallback/useContext), composition, conditional and list rendering, and controlled inputs. The canonical "depends on React" reference.
user-invocable
false
disable-model-invocation
true
version
1.0.1
category
toolchain
author
Claude MPM Team
license
MIT
progressive_disclosure
{"entry_point":{"summary":"React fundamentals: components, JSX, props/state, core hooks, composition, conditional/list rendering, controlled inputs","when_to_use":"Building any React UI, or as the baseline dependency for React-ecosystem skills that require core React knowledge","quick_start":"1. Write a function component returning JSX 2. Hold state with useState 3. Run effects with useEffect 4. Compose via children and props"}}
The canonical reference for general React fundamentals. This skill covers the building blocks every React application shares: components and JSX, props and state, the core hooks, composition patterns, conditional and list rendering, and controlled inputs. It is the baseline "depends on React" target for ecosystem skills (styling, data fetching, state management, deployment) that assume core React knowledge.
Keep this skill focused on fundamentals. For advanced hook composition (SWR-backed custom hooks, debounced contexts, memoized providers), use the sibling react-hooks-composition skill. For explicit finite-state-machine modeling of complex UI flows, use the sibling react-state-machine skill.
When to Use This Skill
Reach for this skill when:
Building components, wiring props, or managing local state
Choosing among the core hooks for a given problem
Rendering lists or conditional UI
Implementing controlled form inputs
Establishing the React baseline that another ecosystem skill depends on
Components and JSX
A React component is a function that returns JSX. Name components in PascalCase. Return a single root node, or wrap siblings in a fragment (<>...</>).
JSX embeds expressions inside {}. Attributes use camelCase (className, onClick, htmlFor). JSX returns a description of the UI; React reconciles it against the DOM.
Props and State
Props pass data down from parent to child and are read-only inside the child. State holds data a component owns and mutates over time.
Treat props and state as immutable. Update state through the setter, and prefer the functional updater (setCount(prev => prev + 1)) when the next value derives from the previous one.
Core Hooks Overview
Call hooks only at the top level of a component or custom hook, never inside conditionals, loops, or nested functions. This rule keeps hook call order stable across renders.
useState — local component state
Holds a value and a setter. Re-renders the component when the value changes.
const [open, setOpen] = useState(false);
useEffect — synchronize with external systems
Runs after render to perform side effects: subscriptions, timers, data fetching, manual DOM work. The dependency array controls when the effect re-runs. Return a cleanup function to tear down subscriptions.
import { useEffect, useState } from'react';
functionWindowWidth() {
const [width, setWidth] = useState(window.innerWidth);
useEffect(() => {
constonResize = () => setWidth(window.innerWidth);
window.addEventListener('resize', onResize);
return() =>window.removeEventListener('resize', onResize);
}, []); // empty deps: subscribe once on mount, clean up on unmountreturn<span>{width}px</span>;
}
useRef — mutable value that survives renders
Stores a mutable value without triggering re-renders. Common uses: referencing a DOM node, or holding a value across renders (timer ids, previous values).
Recomputes a value only when its dependencies change. Apply it for genuinely expensive calculations or to stabilize reference identity passed to memoized children.
Returns the same function instance across renders while dependencies stay equal. Pass stable callbacks to memoized children or to effect dependency arrays.
Extract shared logic into custom hooks (useSomething) rather than copying it between components. Keep components small and single-purpose.
Conditional and List Rendering
Render conditionally with && for presence or a ternary for either/or. Render lists with map, and give each item a stable key derived from its identity (not the array index where order can change).
Direct mutation skips the setter, so React does not re-render.
// BAD: mutates the array in place; React sees the same referencefunctionaddItem(items: string[], next: string) {
items.push(next);
setItems(items);
}
// GOOD: create a new array so the reference changesfunctionaddItem(items: string[], next: string) {
setItems([...items, next]);
}
❌ Don't: Call hooks conditionally
Conditional hook calls break the stable call order React relies on.
// BAD: hook call order changes between rendersfunctionProfile({ id }: { id?: string }) {
if (id) {
const data = useUser(id); // conditional hook callreturn<span>{data.name}</span>;
}
returnnull;
}
// GOOD: call the hook unconditionally; branch on its resultfunctionProfile({ id }: { id?: string }) {
const data = useUser(id); // useUser must accept an undefined id (no fetch / returns null) so the hook is always calledif (!id || !data) returnnull;
return<span>{data.name}</span>;
}
❌ Don't: Use array index as key for reorderable lists
Index keys cause React to misattribute state when items move.
// BAD: index key breaks on reorder/insert/delete
{items.map((item, i) =><Rowkey={i}item={item} />)}
react-hooks-composition: advanced custom-hook composition — SWR-backed data fetching, debounced search with dual loading states, memoized context providers, and reusable async state hooks.
react-state-machine: explicit finite-state-machine modeling with XState v5 for complex flows (multi-step forms, media players, modals with animations) where impossible states must be unrepresentable.
react-advanced: React 19 platform features and rendering architecture — the React Compiler (auto-memoization), concurrent rendering, the use() hook, Actions, virtualization, code-splitting, and the RSC boundary.
Best Practices Summary
Components return JSX: PascalCase names, single root or fragment.
Props are read-only: pass data down, lift state up when sharing.
Update state immutably: use the setter, prefer the functional updater.
Top-level hooks only: never call hooks conditionally.
Effects synchronize external systems: scope with dependencies, clean up subscriptions.
Memoize deliberately: apply useMemo/useCallback for expensive work or stable identity, not by default.
Stable keys: key lists by identity, not array index.
Controlled inputs: state is the single source of truth.
