flutter-riverpod-expert

Installation
Summary

Expert guidance for Flutter Riverpod state management with 2025 best practices and code generation patterns.

  • Code generation with @riverpod annotations and riverpod_generator is strongly recommended; AsyncNotifierProvider is the preferred pattern for async state, mutations, and data fetching
  • Optimize performance with ref.select() for specific fields, ref.watch() for subscriptions, ref.read() for one-time access, and ref.listen() for side effects
  • Repository pattern architecture separates data, application, and presentation layers; dependency injection via providers enables testable, decoupled code
  • Family providers support parameterized state; autoDispose is enabled by default in codegen, with keepAlive option for permanent caching or timed cache strategies
  • Comprehensive error handling via AsyncValue.guard() and .when() pattern; includes testing patterns for providers and widgets, plus common anti-patterns to avoid
SKILL.md

Flutter Riverpod Expert - 2025 Best Practices

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.

When to Use This Skill

Activate this expertise when the user mentions:

  • Riverpod, providers, state management, or StateNotifier
  • AsyncNotifier, FutureProvider, StreamProvider, NotifierProvider
  • Code generation with riverpod_generator or build_runner
  • Data fetching, API integration, mutations, or reactive state
  • State synchronization, caching, autoDispose, or memory management
  • Provider testing, dependency injection, or repository patterns
  • Performance issues with rebuilds, provider selection, or optimization
  • Migration from old Riverpod patterns to modern approaches

Core Principles (2025)

Related skills

More from juparave/dotfiles

Installs
692
GitHub Stars
1
First Seen
Jan 26, 2026