create

floot create <project_name> [arguments]

project_name must be a valid Dart package name: lowercase letters, digits and underscores, starting with a letter or underscore.

What it does

floot create composes your project from layers instead of producing a single fixed shape. It asks (or takes flags for) which layers to include, then runs flutter create, applies the chosen layers, restamps each supabase/migrations/*.sql filename to the moment of generation, records the answers in .floot.yaml, runs pub get, generates icons and splash screens, sorts the imports so the project passes its own flutter analyze, and finishes with a non-blocking report of anything floot requirements would flag.

# Generated by `floot create`. Do not edit.
cli_version: 0.3.0-alpha.1
layers:
  - base
  - supabase
  - harness-claude

Flags

Layer names come from the release, not from the CLI

The layers a release ships are listed in the signed manifest the CLI downloads before it asks you anything, so --with and --without address a layer that shipped after your CLI did. --multi-tenancy, --seat-based-billing and --harness are kept as shorthands for the layers they have always named, and resolve against the same list.

Because the list arrives with the release, a misspelled name is only caught once the download finishes. When one misses, the error names every value that release accepts. Naming one layer in both --with and --without, or in a shorthand and its --with spelling, is rejected rather than silently resolved one way.

--seat-based-billing implies --multi-tenancy unless --no-multi-tenancy is passed explicitly, in which case the combination is rejected rather than silently repaired. all and none cannot be combined with another harness value.

The layer questions are asked interactively when a terminal is attached; without one, the release's own defaults apply. The rest are never prompted for: omitting one silently takes the default in the table. That makes the whole thing scriptable, for CI or a non-interactive shell:

floot create my_app --org com.acme --multi-tenancy --seat-based-billing --harness all

Working offline

Offline is a fallback, not a mode. A floot create that cannot reach Floot uses the newest release already cached on this machine and says which one:

offline: using cached Floot 1.4.0

That happens on its own, so --offline is only needed to stop the attempt being made at all, on a metered connection or a plane. Everything else is the same: the same checks run against the same signed lease and the same signed manifest, and only the layers you pick are ever decrypted.

A cached release still has to earn its way in. The CLI checks the lease's signature, that your clock has not moved backwards, that the lease has not expired, that this machine holds the keys the lease was issued to, that the manifest is the one Floot signed, that your seat's update window reaches the release, and that every byte hashes to what the manifest says. Whichever check fails, the message names it and the one thing that fixes it. Most of them are answered by running online once.

Two flags matter more offline than online. --bundle serves that exact version from the cache, or refuses when it is the one version you do not have. --seat-org picks which license to build under, by organization slug, on a machine licensed by more than one organization; without it, the CLI uses whichever organization you last worked under online. Offline the slug is matched against the organizations the CLI saw the last time it was online. Online it is looked up with Floot first, so a run that passes --seat-org and cannot reach Floot stops with the network error instead of falling back; add --offline to build from the cache under that organization.

floot license --offline reports the same way, printing what the stored lease says without contacting Floot.