naming-conventions

Classes, enums, mixins, and typedefs use UpperCamelCase, while files and folders use lowercase_with_underscores. The file name must match its primary declaration, so TaskNotifier lives in task_notifier.dart with one primary public type per file.

Dart constants use lowerCamelCase, such as maxItemsPerPage, never SCREAMING_CAPS. Dart dropped the C-style convention, and the analyzer enforces this through the constant_identifier_names lint rule.

Name Riverpod ViewModels with the Notifier suffix, such as TaskListNotifier in task_list_notifier.dart, one per Screen. Avoid ViewModel, Controller, or VM suffixes on the Riverpod path; ViewModel is reserved for the Provider appendix only.

A Service is a capability interface you define, like ShareService, while a Gateway wraps a specific external plugin or native channel, like NotificationGateway over flutter_local_notifications. Concrete implementations stay in the composition root and never leak into shared code.

Yes, booleans should read as assertions using is, has, can, or should prefixes, such as isLoading, hasError, and canSubmit. This makes conditions read like prose and avoids ambiguous names like loading or valid.

Group imports with dart: first, then package:, then relative imports, each group alphabetized, with exports in their own section after imports. Let dart format and the directives_ordering lint enforce this rather than sorting by hand.