Skip to content

Setup questions ​

A handful of questions is all Flutter Kickstart needs. Most have a default, so you can press Enter to accept it. Each answer maps to one generator flag, so you can also skip the questions and pass flags (see Generator flags).

Agents ask one question at a time, skip questions an earlier answer makes pointless, and read everything back before generating.

The questions ​

#QuestionFlagDefault
1App display name and description--app-name, --descriptionfrom --name
2Package name--namesnake_case of the display name
3Organization / reverse domain--orgrequired
4Platforms--platformsandroid,ios
5State management: Bloc or Riverpod--state bloc|riverpodnone, always asked
6Network client: viva_network_kit or plain Dio--network viva|dioviva, always asked
7Navigation: go_router, auto_route or Navigator--router go_router|auto_route|navigatorgo_router, always asked
8API base URL per flavor--base-url flavor=url (repeat)https://<flavor>.api.example.com
9Starter features beyond home--features auth,ordersnone
10Languages besides English--locales en,bnen
11Crash reporting: none, Sentry or Crashlytics--crashnone
12CI/CD: GitHub Actions + Fastlane, or none--ci github|nonegithub
13Minimum test coverage, in percent--coverage-floor80
14Figma file link--figma-urlnone
15AI tools the team uses--agentsall

What the choices change ​

State management ​

Bloc gives you Cubits with get_it + injectable for dependency injection. Riverpod gives you riverpod_generator controllers and a provider graph. Both are asked every time, because the right one depends on the team and the client. See State management.

Network client ​

Feature code only ever depends on the AppApiClient contract. This choice swaps one class in lib/core/network/:

  • viva uses viva_network_kit (VivaApiClient). It also checks connectivity before each call.
  • dio uses plain Dio (DioApiClient) and doesn't add the package at all.

Both share dio_factory.dart, AppFailureConverter and the same JsonSerializer API, so features, repositories and the feature generator are identical either way. See Networking and errors.

go_router is the default, but you pick: auto_route for typed, generated routes, or Navigator for Flutter's built-in named routes with no package. The choice swaps lib/core/routing/app_router.dart, the app widget and the flutter-navigation skill. AppRoutes constants and add_feature.py work the same with all three. See Navigation.

Languages ​

Each extra locale gets lib/l10n/arb/app_<locale>.arb, filled with the English strings until someone translates them. The iOS locale list is updated too. New features add their strings to every ARB file.

Crash reporting ​

none logs to the console through ConsoleCrashReporter. sentry and crashlytics add the SDK, an adapter behind the CrashReporter contract, and raise Android minSdk if the SDK needs it.

CI/CD ​

github generates the workflows, Fastlane and docs/deployment-setup.md. none generates no workflows (Very Good CLI's own are removed too) and leaves the deployment skill out of the AI layer. scripts/quality_gate.sh is always generated. See CI/CD and releases.

Coverage floor ​

CI enforces it on every pull request. The generator also fails if a freshly generated app falls below it, so you start above the bar.

Flavors ​

development, staging and production are fully wired, including native Android and iOS setup. Custom flavors (--flavors) only get Dart entrypoints, and the generator warns about the native parts left to do.

Released under the MIT License.