React State Management and Data Fetching

When to use

Invoke when introducing or restructuring client state and data fetching in a standalone React SPA, when translating the frontend-architecture.md state-tier model and data-fetching strategy into concrete libraries and conventions, or when implementing/hardening the auth-token lifecycle the scaffold and routing skills left as a seam.

Do not use for: project scaffolding or the auth provider baseline (use react-app-scaffold-and-runtime), route topology and route gates (use react-routing-and-rendering-strategy), design-system or a11y (use react-design-system-and-accessibility), or perf/bundle work (use react-performance-and-delivery-optimization).

Inputs

Required:

• An existing react app scaffold (react-app-scaffold-and-runtime, provides the auth provider/wrapper seam) and routing (react-routing-and-rendering-strategy, consumes session state and exposes the protected-route gate).
• Approved frontend-architecture.md with the 4-tier state model (what lives in URL, server cache, global client, local) and the data-fetching strategy (library, cache policy, optimistic posture).
• architecture/security decisions on token strategy: token type, storage location (cookie vs memory vs storage), refresh model, CSRF posture, and logout/session-revocation behavior.

Optional: