no-use-effect

Enforces a no-direct-`useEffect` rule in React and React Native codebases.

64|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/alejandrobailo/no-use-effect --skill no-use-effect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: no-use-effect
Source: https://github.com/alejandrobailo/no-use-effect/tree/main
Command: npx skills add https://github.com/alejandrobailo/no-use-effect --skill no-use-effect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces a strict no-direct-useEffect rule in React and React Native codebases, guiding developers toward derived state, inline computations, and the appropriate use of useMemo, data-fetching libraries, or mount-time wrappers.

Core Features & Use Cases

  • Enforces the no-useEffect rule across component code in React/React Native projects.
  • Suggests best practices like deriving state inline, using useMemo, and preferring event handlers or data-fetching libraries over effects.
  • Supports guidance during writing, code reviews, and refactoring, including detection of direct useEffect mentions.

Quick Start

Install the skill in your project and enable enforcement so any direct useEffect usage surfaces guidance.

Frequently Asked Questions about no-use-effect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I avoid useEffect in React components?

To avoid useEffect in React components, derive state inline, use useMemo for expensive computations, or prefer event handlers and data-fetching libraries over effects for managing component logic.

What is the best way to refactor React Native code to remove direct useEffect calls?

The best way to refactor React Native code to remove direct useEffect calls is by replacing them with derived state, inline computations, useMemo, or dedicated data-fetching libraries during code reviews and refactoring.

Why should I enforce a no-useEffect rule in my React codebase?

Enforcing a no-useEffect rule in your React codebase prevents unnecessary side effects, reduces complex re-render cycles, and guides developers toward best practices like inline state derivation and proper data fetching.

Can I use this no-useEffect enforcement with React Native projects?

Yes, this no-useEffect enforcement applies directly to React Native projects, guiding developers through appropriate primitives during writing, editing, reviewing, or refactoring component code.

What are the limitations of enforcing a strict no-direct-useEffect rule?

A strict no-direct-useEffect rule limits direct side effect management, requiring developers to substitute effects with mount-time wrappers, useMemo, or external data-fetching libraries for operations traditionally handled by useEffect.

Does no-use-effect provide guidance during code reviews?

Yes, no-use-effect provides guidance during code reviews by detecting direct useEffect mentions and suggesting best practices like deriving state inline or using data-fetching libraries instead.