you-might-not-need-state

To fix unnecessary useState and derived state, analyze your React components to detect props mirrored into state and apply refactoring constraints to compute values directly during render instead of storing them locally.

You should use React Query instead of useState for server state to prevent local state duplication and avoid chained state updates, ensuring server data remains external and maintainable across component re-renders.

Common React state management anti-patterns include prop mirroring, derived state stored in useState, and server-state-in-local-state, all of which cause client-side state duplication and reduce maintainability.

Yes, you can analyze an entire codebase for state duplication by applying the analyzer to broader scopes, detecting unnecessary useState usage, and enforcing constraints to keep server data in React Query or Zustand.

To stop mirroring Zustand or React Query state into local useState, enforce architectural constraints that prevent server data duplication and remove derived state updates from your component logic.

The best way to refactor derived state stored in useState during a PR review is to run an analyzer on the diffs to detect unnecessary state duplication and apply fixes to compute values directly.