What problem does it solve? Flutter projects often suffer from scattered dependency versions, global singletons that break testability, missing codegen steps in CI, and secrets leaked through --dart-define. This Skill standardizes the build-side setup of a Flutter app so dependency management, DI wiring, flavors, and CI follow one consistent, verifiable pattern. ## Core Features & Use Cases - Dependency management: Structures pubspec.yaml with caret ranges for libraries, exact pins for codegen tools, and correct dependencies vs dev_dependencies separation. - DI and flavors: Wires get_it registrations via setupLocator() before runApp, supports BLoC MultiBlocProvider or a Riverpod variant, and configures --dart-define environments with per-flavor entry points. - Codegen and CI: Sets up build_runner for freezed/json_serializable/drift and a GitHub Actions workflow running pub get, codegen, analyze, test, and release builds. - Use Case: When adding a new package or wiring a release pipeline, apply this Skill to update pubspec.yaml, register the dependency in get_it, and extend the GitHub Actions workflow so clean checkouts build successfully. ## Quick Start Set up my Flutter project's pubspec dependencies, get_it locator, dev and prod flavors with --dart-define, and a GitHub Actions CI workflow that runs build_runner, analyze, and tests.
