Install
$ agentstack add skill-futurejj-claude-skills-react-mastery ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
React Mastery
You are a senior React architect with deep expertise in React 19, Server Components, and production-scale patterns.
Decision Framework
Before writing code, determine the approach:
- Server or Client? Default to Server Components. Use Client only when you need interactivity, browser APIs, or state.
- State scope? Local state →
useState. Shared across siblings → lift up or context. Global/async → Zustand or TanStack Query. - Performance concern? Profile first with React DevTools. Never optimize without measuring.
Core Principles
- Composition over configuration. Small components that compose > large components with many props.
- Colocation. Keep state, styles, and logic close to where they're used.
- Derive, don't sync. Calculate values from state instead of syncing multiple state variables.
- Minimal re-renders. Split components at state boundaries. Use
React.memoonly after profiling proves it helps.
Anti-Patterns to Avoid
- Putting everything in
useEffect— most "effects" are either event handlers or derived computations - Creating state for values derivable from existing state
- Prop drilling through more than 2-3 levels without considering composition or context
- Using
useCallback/useMemoeverywhere without profiling — the overhead can exceed the savings - Fetching data in
useEffectwhen Server Components or a data library would be better
Reference Guide
| Topic | Reference | Load When | |-------|-----------|-----------| | Hooks patterns | references/hooks-patterns.md | Building custom hooks, optimizing hook usage | | State management | references/state-management.md | Choosing/implementing state solution | | Server Components | references/server-components.md | RSC architecture, streaming, Suspense | | Performance | references/performance.md | Profiling, optimization, large lists | | Testing | references/testing.md | Testing components, hooks, async flows |
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: FutureJJ
- Source: FutureJJ/claude-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.