executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
nextjs-state-managementApply best practices for managing URL, server, and client state in Next.js applications. Use when choosing between URL params, SWR/TanStack Query, Zustand, or Context for state, or when fixing hydration mismatches from localStorage.
Independent GitHub snapshot · Automated classification · Original documentation governs
useSearchParams + useRouter).useState.'use client' only) or Jotai.useState. Colocate as close to consumer as possible.Wrap localStorage reads in useEffect or mounted flag to avoid hydration mismatches. Manage optimistic updates with useOptimistic in Next.js 15+.
If project already uses redux@4 + createStore + redux-thunk + next-redux-wrapper:
useSelector / useDispatch hooks — never connect HOC.RootState and typed AppDispatch for all selectors and dispatch calls.@reduxjs/toolkit) → RTK Query → then consider TanStack Query.See references/redux.md for typed selector and thunk patterns.
useState or URL params; avoid Zustand for basic UI.useEffect for data fetching: Use SWR or TanStack Query for server state.