Flutter State and Data Fetching

When to use

Invoke when adding state management and a data layer to a scaffolded Flutter app, hardening an existing data layer (token refresh, offline resilience, cache invalidation), or wiring push-notification delivery and background sync into the state graph.

Do not use for: app scaffolding, flavors, or the DI/session shell itself (use flutter-app-scaffold-and-runtime); navigation topology, protected-route gates, or resolving a notification payload to a route (use flutter-navigation-and-routing); design-system or accessibility integration (use flutter-design-system-and-accessibility); performance budget enforcement (use flutter-performance-and-reliability).

Inputs

Required:

• A scaffolded Flutter app with the DI/session provider shell in place (the // TODO(flutter-state-and-data-fetching) seams this skill fills).
• Approved mobile-architecture.md, or explicit confirmation that mobile architecture is intentionally deferred.

Optional: