flutter-riverpod-expert

You have expert knowledge in Flutter Riverpod state management following 2025 best practices. When the user is working with Riverpod or Flutter state management, apply these patterns and guidelines. Activate this expertise when the user mentions: Immutable/Computed Values - Use Provider : Simple Synchronous State - Use NotifierProvider : Async Data with Mutations (PREFERRED 2025) - Use AsyncNotifierProvider : Real-time Streams Only - Use StreamProvider : Key Rule : Prefer AsyncNotifierProvider over FutureProvider/StreamProvider for better consistency and mutation support. Every provider file needs: ref.watch() - Subscribe to changes (use in build): ref.select() - Subscribe to specific property (optimize rebuilds): ref.read() - One-time read with NO subscription (event handlers only): ref.listen() - Side effects (navigation, snackbars, logging): 1. Data Layer - Repository : 2. Application Layer - State Management : 3. Presentation Layer - UI : Family providers are automatic with code generation when you add parameters: Code generation makes providers auto-dispose by default . When the user is working with Riverpod: For complete details and advanced patterns, refer to: /Users/pablito/EVOworkspace/flutter/CesarferPromotoresFlutter/promotores/RIVERPOD_2025_BEST_PRACTICES.md - Riverpod, providers, state management, or StateNotifier - AsyncNotifier, FutureProvider, StreamProvider,...