game-tutoriallisted

# Game Tutorial Teach the next meaningful action at the moment it becomes relevant, while keeping full rules available as reference. ## 1. Inspect the project and request Identify the engine or runtime, entry flow, run command, input-binding system, tutorial state storage, and string organization. Determine whether the user requested an audit or implementation; an audit ends with findings and a proposed form. ## 2. Audit the first-time experience Play from a clean state and learn only from what a new player can see, try, and receive as feedback. If the game cannot run, trace the displayed entry flow from source and mark the result inferred. Inventory controls, goal and failure conditions, score meaning, and non-obvious rules. Classify every gap: - **First-action essential** — needed before the player can take a meaningful action. - **Contextual** — teach when the mechanic or input first becomes relevant. - **Reference** — useful but not needed in the active flow. - **Discoverable** — safe experimentation and feedback already teach it. Teach the first three classes in their proper channel. Leave discoverable behavior alone so necessary guidance is not buried under the obvious. ## 3. Choose the form Use the least intrusive form the existing game can support: 1. **Guided first steps.** Attach one prompt to an existing level, wave, encounter, or event when the action first matters. 2. **Staged first run.** Script the opening of an existing mode to expose mechanics i