A practical reference that cuts through the noise about when Effects are actually necessary versus when you're reaching for the wrong tool. It's structured around a clear decision tree: user interactions belong in event handlers, derived values should be calculated during render, and Effects are for synchronizing with external systems. The quick reference table alone will save you from common mistakes like using Effects for transformations or event responses. What makes this genuinely useful is that it teaches you to identify the anti-patterns before you write them, which is more valuable than just knowing the API. Keep it handy during code reviews.
npx -y skills add softaworks/agent-toolkit --skill react-useeffect --agent claude-codeInstalls into .claude/skills of the current project.
Select a file.
mindrally/skills
giuseppe-trisciuoglio/developer-kit
syncfusion/react-ui-components-skills
supercent-io/skills-template
binjuhor/shadcn-lar