AgentStack
SKILL verified MIT Self-run

React Mastery

skill-futurejj-claude-skills-react-mastery · by FutureJJ

Expert-level React development including React 19, Server Components, hooks composition, state management, and performance optimization. Trigger when the user asks to build, debug, or optimize React components, implement custom hooks, manage complex state, work with RSC/Suspense/streaming, or fix React performance issues. Also trigger for React architecture decisions, component design patterns, o…

No reviews yet
0 installs
16 views
0.0% view→install

Install

$ agentstack add skill-futurejj-claude-skills-react-mastery

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No 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.

Are you the author of React Mastery? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

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:

  1. Server or Client? Default to Server Components. Use Client only when you need interactivity, browser APIs, or state.
  2. State scope? Local state → useState. Shared across siblings → lift up or context. Global/async → Zustand or TanStack Query.
  3. 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.memo only 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/useMemo everywhere without profiling — the overhead can exceed the savings
  • Fetching data in useEffect when 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.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.