flutter-app

Bootstrap a new Flutter app the way this owner builds them: FVM-pinned SDK, clean architecture (feature-first), Riverpod for state, an Either/Failure error model, current stable packages, and the house git and CI workflow with release-please and Play Store delivery.

First read the shared rules (they override anything you remember): ../shared/house-rules.md, ../shared/no-ai-attribution.md, ../shared/git-and-ci.md, ../shared/docs-and-context.md, ../shared/hardening.md, and (for public repos) ../shared/open-source-docs.md.

Step 0. Get the brief, then ask the variant questions (hard stop)

This is a hard stop. Do not run any scaffolding command until the user has answered.

First, get the project brief: one paragraph on what the app does, its main features, target users, and any hard constraints. If the user has not given one, ask for it. The brief drives naming, the feature list, and the data model.

Then ask the variant questions. If a choice has multiple options, ask; do not assume. Ask in one batch, then proceed.

1. Repo visibility: private, open-source, or private-plus-open-source.
2. Backend: BYOK (each user supplies their own LLM key, no backend), a custom backend (Dio + JWT auth), or none yet. See references/architecture.md.
3. State codegen: Riverpod with codegen (@riverpod + build_runner) or plain Riverpod with hand-written providers. Default: codegen.
4. Local data: Drift, Isar, shared_preferences only, or none yet.
5. Auth: Google Sign-In, none, or backend-driven.
6. Release target: Play Store (default), App Store, or both.

If the user already answered some, do not re-ask.

Step 1. Pin the SDK with FVM and verify versions