Run any Skill in Manus with one click

flutter-state-management

Stars6

Forks2

UpdatedMarch 31, 2026 at 12:41

State management architecture for Flutter using Riverpod, Provider, and BLoC patterns. Use when choosing a state solution, implementing reactive state, resolving rebuild issues, or structuring MVVM/BLoC architecture.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

Poorgramer-Zack

Poorgramer-Zack/dart-expert-skills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

5 files

SKILL.md

readonly

name	flutter-state-management
description	State management architecture for Flutter using Riverpod, Provider, and BLoC patterns. Use when choosing a state solution, implementing reactive state, resolving rebuild issues, or structuring MVVM/BLoC architecture.
metadata	{"last_modified":"2026-03-12 11:18:17 (GMT+8)"}

State Management Architecture Guide

Goal

Master the implementation of declarative reactivity inside Flutter applications. Replaces archaic mutable StatefulWidgets with highly testable, globally available, decoupled state management ecosystems (MVVM or BLoC patterns). Accurately determine the exact state architectural deploy depending directly on application complexity.

Process

🚀 High-Level Workflow

Navigating State Management requires understanding explicit UI requirements and data flow directions natively.

Phase 1: Determining State Scale

State Management Overview - Learn to accurately delineate between Ephemeral (local) state and App (global) state natively.

Phase 2: Deploying Framework Implementation

Choose the designated framework strictly corresponding to the project's legacy constraints or architectural requirements:

Provider Best Practices (v6.x) - The legacy standard. Essential for maintaining existing massive environments relying natively atop InheritedWidget arrays utilizing strict context.read/Consumer MVVM separation.
Riverpod Best Practices (v3.x) - Provider's spiritual successor. Employs compile-time safe, context-less global ProviderContainer arrays obliterating scoping errors definitively.
BLoC Best Practices (v9.x) - The enterprise standard. Strictly enforces unidirectional event-driven data flows mapping explicit Events to distinct States (amplified dramatically via Freezed Union Types).

📚 Documentation Library

Consume these highly specialized architectural reference resources sequentially determining data flow structures profoundly:

More from this repository

same repository

routing-with-autoroute

Poorgramer-Zack/dart-expert-skills

Implements type-safe Flutter routing using AutoRoute v11 with code generation and @RoutePage annotations. Activates when setting up AutoRoute navigation, configuring AutoRouterConfig or RootStackRouter, generating route files with build_runner, using @RoutePage, @PathParam, or @QueryParam annotations, implementing AutoTabsRouter for bottom navigation tabs, adding navigation guards with AutoRouteGuard, setting up nested or child routes, handling type-safe route parameters, or migrating from string-based Navigator routing to compile-time-verified routes. Ideal for large apps requiring refactoring confidence and zero string-based routing errors.

2026-04-276

implementing-flutter-bloc

Poorgramer-Zack/dart-expert-skills

Implements BLoC (v9.x) event-driven state management for Flutter with unidirectional data flow using the flutter_bloc package. Use when implementing Bloc/Cubit classes, mapping Events to States, consuming state with BlocBuilder/BlocListener/BlocConsumer, applying event transformers (restartable/droppable/sequential) for concurrency control, setting up BlocProvider/MultiBlocProvider DI, integrating Freezed for sealed union types and exhaustive pattern matching, or testing with blocTest. Ideal for enterprise apps requiring business logic separation, precise concurrency control (search debouncing, form deduplication), or event replay debugging.

2026-04-276

persisting-data-with-drift

Poorgramer-Zack/dart-expert-skills

Implements type-safe reactive SQL persistence in Flutter using Drift v2.32 (formerly Moor) built on SQLite with automatic code generation. Activates when defining table schemas with Drift DSL, writing type-safe join or subquery operations, handling schema migrations with MigrationStrategy, using reactive watch() streams for live UI updates, implementing ACID transactions, defining foreign key constraints or cascade deletes, enabling WAL mode for write performance, troubleshooting generated .g.dart type mismatches, migrating from sqflite or sqlite3 v2 to v3, using DAOs for query separation, or building offline-first apps requiring strong relational data integrity and compile-time SQL verification.

2026-04-276

routing-with-gorouter

Poorgramer-Zack/dart-expert-skills

Implements declarative Flutter routing using GoRouter v17 with URL-based navigation, deep linking, and authentication guards. Activates when configuring GoRoute path patterns, setting up StatefulShellRoute for persistent bottom navigation state, implementing ShellRoute for shared nested layouts, adding redirect guards with loop prevention (idempotent redirects), configuring deep links for iOS (FlutterDeepLinkingEnabled) or Android (intent-filters), debugging redirect loops or navigation stack issues, handling 404 error routes with errorBuilder, using named routes with path/query/extra parameters, or migrating from imperative Navigator.push to declarative routing. Ideal for Flutter web apps requiring URL bar synchronization, mobile apps with universal links or app links, or multi-level navigation hierarchies.

2026-04-276

managing-hive-storage

Poorgramer-Zack/dart-expert-skills

Hive CE (Community Edition v2.19.x) NoSQL object database for Flutter providing blazing-fast key-value and object storage with TypeAdapters. Use this skill when implementing offline-first architecture, high-performance local data caching, NoSQL document-style object stores, custom TypeAdapter serialization for complex objects, lazy loading boxes for memory efficiency, encrypted boxes (HiveAES encryption), database compaction for size optimization, storing large datasets without SQL schema overhead, implementing local-first sync patterns, or migrating from SQLite to NoSQL. Supports primitive types, custom objects, lists, and maps. Ideal for apps requiring ultra-fast read/write operations (microsecond latency), object persistence without ORM complexity, or local-first data architecture.

2026-04-276

implementing-riverpod

Poorgramer-Zack/dart-expert-skills

Implements Riverpod (v3.3.x) compile-safe state management for Flutter apps. Use when implementing @riverpod code generation providers, handling AsyncValue loading/error/data states, using ref.watch/ref.read/ref.listen, setting up ProviderScope, writing Notifier/AsyncNotifier classes, using FutureProvider/StreamProvider, applying autoDispose and family modifiers, combining providers, testing providers in isolation, scoping rebuilds with Consumer instead of ConsumerWidget, using ref.watch with select() for field-level precision, migrating from StateNotifierProvider or Riverpod 2.x patterns, handling Notifier resource lifecycle with ref.onDispose, or using experimental Mutation and offline persistence APIs.

2026-04-276

name	flutter-state-management
description	State management architecture for Flutter using Riverpod, Provider, and BLoC patterns. Use when choosing a state solution, implementing reactive state, resolving rebuild issues, or structuring MVVM/BLoC architecture.
metadata	{"last_modified":"2026-03-12 11:18:17 (GMT+8)"}

State Management Architecture Guide

Goal

Process

🚀 High-Level Workflow

Navigating State Management requires understanding explicit UI requirements and data flow directions natively.

Phase 1: Determining State Scale

State Management Overview - Learn to accurately delineate between Ephemeral (local) state and App (global) state natively.

Phase 2: Deploying Framework Implementation

Choose the designated framework strictly corresponding to the project's legacy constraints or architectural requirements:

Provider Best Practices (v6.x) - The legacy standard. Essential for maintaining existing massive environments relying natively atop InheritedWidget arrays utilizing strict context.read/Consumer MVVM separation.
Riverpod Best Practices (v3.x) - Provider's spiritual successor. Employs compile-time safe, context-less global ProviderContainer arrays obliterating scoping errors definitively.
BLoC Best Practices (v9.x) - The enterprise standard. Strictly enforces unidirectional event-driven data flows mapping explicit Events to distinct States (amplified dramatically via Freezed Union Types).

📚 Documentation Library

Consume these highly specialized architectural reference resources sequentially determining data flow structures profoundly: