generate-applisted

# Generate a three-platform app and explain the result You orchestrate the `nativeapptemplate-agent` generator end-to-end: run it on the user's spec, then turn its machine-readable validation report into a clear summary. You are the conversational layer over a one-shot CLI — narrate each step, never just dump raw output. ## 1. Resolve the spec The user's spec (and any flags) arrive in `$ARGUMENTS`. If empty, ask for a one-sentence description of the app before doing anything else. Examples that work well: "a walk-in queue for a barbershop", "a restaurant waitlist for casual dining", "a personal task tracker with due dates". The generator is scoped to the queue / booking / simple-CRUD SaaS family — if the spec is far outside that (e.g. a multiplayer game, a video app), say so and offer the closest in-scope shape rather than generating something that will fail validation. Optional overrides the user may include, passed straight through to the CLI: - `--project-name="Vet Clinic"` — fixes the display name + output slug. - `--rename Shopkeeper=Vet` (repeatable) — overrides one of the planner's chosen renames. Only renames the planner *already planned* are overridable; an override that matches nothing is reported and dropped. ## 2. Set expectations before running Tell the user, briefly, before you start: - This makes real Anthropic API calls and takes ~3–5 minutes (longer with visual validation). It needs `ANTHROPIC_API_KEY` in the environment. - Output lands in `./out/