wan-3-promptinglisted

# Wan 3.0 prompting Researched against primary sources (Alibaba Model Studio official prompt guide, Runware Wan 3.0 API docs, the Wan 3.0 prompt guide, and a provider OpenAPI schema read directly). Background write-up with the full citation trail: [`docs/wan-3-research.md`](../../docs/wan-3-research.md). `[NV]` = not verified — confirm before relying on it. --- ## 1. The five rules that break scenes Every illogical scene traces back to one of these. They are **documented behaviour**, not bad luck. 1. **No state change inside a shot.** Alibaba is explicit: *"cuts happen BETWEEN clips, not within"*. An object that disappears, clothing that tears, lights that switch — each must become a **cut**. (Cost: two paid generations on a necklace that refused to leave a neck.) 2. **One action beat per shot.** *"Keep actions simple and short."* A 5s clip cannot do "sprints + vaults a planter + shoulders through a door". Two beats = two clips. 3. **Label speakers, never pronouns.** With two people on screen, "He says" makes the model guess. Use `[Man in the black tuxedo, firm]: "..."`. 4. **Address references by identifier.** The model binds `Image1` / `Image2` written in the prompt text to the uploaded reference array. Natural language ("the man from the first reference") is measurably weaker. 5. **Name the camera explicitly.** The default behaviour is a gentle drift. A locked frame requires the literal words `static, locked-off`. Also documented as unreliabl