What problem does it solve? Flutter and Dart projects using build_runner generators (freezed, json_serializable, drift_dev, riverpod_generator, mockito) hit phantom analyzer errors, conflicting-output build failures, stale generated code, and inflated coverage when codegen order, builder scoping, and commit policy are not disciplined. This Skill enforces one deterministic codegen pass with the correct CI gates. ## Core Features & Use Cases - Fixed codegen-first ordering: Runs dart run build_runner build --delete-conflicting-outputs before flutter analyze, eliminating misleading "missing part file" and "undefined class _$Foo" errors. - Builder scoping and policy gates: Fences every builder with generate_for: globs in per-package build.yaml files, and backs the commit-vs-gitignore decision with the matching CI gate (freshness diff or codegen-first). - Toolchain parity and excludes: Pins the SDK so local equals CI, and mirrors generated-file suffixes into both analyzer and lcov coverage excludes. - Use Case: After renaming a model, your build fails with "conflicting outputs" and the analyzer reports undefined _$Task classes. This Skill regenerates with --delete-conflicting-outputs first, then analyzes a clean tree. ## Quick Start Ask the AI to set up the build_runner codegen discipline for your Flutter project, including scoped build.yaml files, analyzer and coverage excludes, and the CI freshness gate.
