flutter-dart-code-review

Comprehensive, library-agnostic checklist for reviewing Flutter/Dart applications. These principles apply regardless of which state management solution, routing library, or DI framework is used. These principles apply to all Flutter state management solutions (BLoC, Riverpod, Provider, GetX, MobX, Signals, ValueNotifier, etc.). The table below maps universal principles to their implementation in popular solutions. Use this to adapt review rules to whichever solution the project uses. - In Riverpod : providers depending on providers via ref.watch is expected — flag only circular or overly tangled chains - In BLoC : blocs should not directly depend on other blocs — prefer shared repositories or presentation-layer coordination - In other solutions: follow the documented conventions for inter-component communication - Effective Dart: Style - Effective Dart: Usage - Effective Dart: Design - Flutter Performance Best Practices - Flutter Testing Overview - Flutter Accessibility - Flutter Internationalization - Flutter Navigation and Routing - Flutter Error Handling - Flutter State Management Options