Dart-Flutter-conventions-for-this-repo-Riverpod-go-router-lints

Instruction file imported from edbecnel/speakup-connect (.cursor/rules/Dart-Flutter-conventions-for-this-repo-Riverpod-go-router-lints.mdc). Copyright stays with the author.

Dart/Flutter standards:

• File names: snake_case.dart. Classes: PascalCase. Providers: camelCase…Provider.
• Prefer ConsumerWidget for screens; only use Stateful when truly needed.
• AsyncValue: ALWAYS handle loading/error/data (use AppLoadingIndicator/AppErrorWidget where appropriate).
• Widgets contain no business logic; providers/usecases do the work.
• Route usage:
  • Routes are centralized in lib/core/router/app_router.dart.
  • Use named routes/constants; no stringly-typed path concatenation in widgets.
• Localization:
  • No hardcoded user-facing strings in widgets.
  • Add English keys to speakup_connect_app/lib/l10n/app_en.arb and use context.l10n.<key>().
• Error handling:
  • Catch Firebase exceptions in datasource/repository and translate to domain Failure types; don’t leak raw Firebase exceptions to UI.
• Keep files/classes small (target ≤300 lines/file, ≤200 lines/class); split when needed.
• Respect analyzer strictness (analysis_options.yaml: strict-casts/strict-inference/strict-raw-types).