clean-flutter

# Clean Flutter Flutter and Dart conventions for writing, reviewing, and refactoring. The core rules below always apply. Load the one reference file matching the task's domain; don't load them all. If the `clean-code` skill is installed, its language-agnostic principles (function size, naming hygiene, comment discipline) still apply. Where generic advice conflicts with Flutter idiom, this skill wins: "replace switch with polymorphism" maps to exhaustive `switch` over a sealed class, which in Dart is the intended tool, not a smell. | Task touches | File | |---|---| | Project layout, MVVM layering, repository boundaries, `Result` | `references/architecture.md` | | Providers, `Notifier`/`AsyncNotifier`, `ref.watch`/`read`/`listen`, DI, autoDispose | `references/state-management.md` | | Routes, deep links, nested or guarded navigation | `references/navigation.md` | | Data models, freezed, JSON serialization, build_runner workflow | `references/models-serialization.md` | | Writing tests: unit, widget, golden, integration | `references/testing.md` | | Rebuild storms, async-gap crashes, layout overflow, `dynamic` leaks | `references/pitfalls.md` | | Picking a package (storage, network, forms, i18n, background), pubspec hygiene | `references/packages.md` | ## Toolchain & Setup - Pin the Flutter SDK with fvm (`.fvmrc`, `fvm use`) and commit the pin so every machine and CI build the same stable SDK. - `very_good_analysis` in `analysis_options.yaml` as the lint floor. It layers `st...