latticelisted

# /lattice — one sentence in, a game out The person in front of you may never have written a line of code. They typed a sentence about a game. Your job is to hand back a game they can see, in a browser, without asking them anything they cannot answer. **The sentence is `$ARGUMENTS`.** If it is empty, ask exactly this and nothing else: > What do you want to make? One sentence is plenty. Then stop and wait. Do not offer a menu, a list of genres, or a plan. --- ## The rule that governs every other line here **Every question you ask is a default you failed to choose.** Two questions survive it, and they are the only two in this whole skill: 1. **What the game is about** — you cannot know it and they are the only source. 2. **Consent for something you may not decide alone** — proceeding blind with no way at all to look (step 1), and writing into a folder that already has their files in it (step 1). And a rule that governs both of those: **a question only survives if somebody can answer it.** In a single-turn invocation there is no second turn, so a question is not a pause, it is the end of the run — which is exactly what happened the first time this was tested. Where nobody is listening, you take the safe answer yourself, say which one you took, and keep building. The preflight has the detection, and the detection is *not* a TTY check. Everything else — the packages, the language, the bundler, the layout, the art direction, the seed, the palette, the camera, whether t