mcpField
R
react-useeffect

react-useeffect

github.com/nweiiDevelopment1040 installsUpdated today
Repository

About react-useeffect

A React development skill explaining when Effects are appropriate and when render-time calculations, event handlers, or other alternatives fit better. It focuses on avoiding unnecessary useEffect usage.

Key features

  1. 01Guidance on when Effects are needed
  2. 02Alternatives for derived state
  3. 03Event-handler recommendations
  4. 04Data-fetching cleanup guidance
  5. 05Decision tree for choosing an approach

Use cases

  1. 01Reviewing a component that uses useEffect
  2. 02Deriving values from props or state
  3. 03Handling user actions without Effects
  4. 04Fetching data with cleanup

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/nweii/agent-stuff --skill react-useeffect

After installing, type/react-useeffectin Claude Code to confirm it loaded.

Bundled filesalternatives.mdanti-patterns.md

Details

From the project README

You Might Not Need an Effect

Effects are an escape hatch from React. They let you synchronize with external systems. If there is no external system involved, you shouldn't need an Effect.

Quick Reference

SituationDON'TDO
Derived state from props/stateuseState + useEffectCalculate during render
Expensive calculationsuseEffect to cacheuseMemo
Reset state on prop changeuseEffect with setStatekey prop
User event responsesuseEffect watching stateEvent handler directly
Notify parent of changesuseEffect calling onChangeCall in event handler
Fetch datauseEffect without cleanupuseEffect with cleanup OR framework

When You DO Need Effects

  • Synchronizing with external systems (non-React widgets, browser APIs)
  • Subscriptions to external stores (use useSyncExternalStore when possible)
  • Analytics/logging that runs because component displayed
  • Data fetching with proper cleanup (or use framework's built-in mechanism)

When You DON'T Need Effects

  1. Transforming data for rendering - Calculate at top level, re-runs automatically
  2. Handling user events - Use event handlers, you know exactly what happened
  3. Deriving state - Just compute it: const fullName = firstName + ' ' + lastName
  4. Chaining state updates - Calculate all next state in the event handler

Decision Tree

Need to respond to something?
├── User interaction (click, submit, drag)?
│   └── Use EVENT HANDLER
├── Component appeared on screen?
│   └── Use EFFECT (external sync, analytics)
├── Props/state changed and need derived value?
│   └── CALCULATE DURING RENDER
│       └── Expensive? Use useMemo
└── Need to reset state when prop changes?
    └── Use KEY PROP on component

Detailed Guidance

Comments

Markdown supported