Decide who owns each piece of state, separate server state from client state, keep derived data derived, and draw module boundaries so features don't reach into each other's stores.
Most state bugs aren't about which library you picked. They come from unclear ownership: the same data lives in two places, and they drift apart.
Symptoms you've probably seen:
useEffect that copies props into state, plus another effect that syncs it back.The rule: every piece of state has exactly one owner, the single source of truth. Everything else reads from it or derives from it.
Questions to ask for each piece of state:
Answering these explicitly, in a design doc or ADR, does more for a codebase than any state library choice.