← ClaudeAtlas

seed-locked-iterationlisted

Use the seed parameter to isolate what a prompt change actually did, instead of rolling new dice every generation. Use whenever the user is iterating on an APImage generation, says output is inconsistent or unpredictable, mentions seeds or reproducibility, or can't tell whether an edit improved anything.
apimageorg/apimage-skills · ★ 0 · AI & Automation · score 72
Install: claude install-skill apimageorg/apimage-skills
# Seed-Locked Iteration Without a fixed seed, every generation is a fresh roll. You change one word in the prompt, the output changes completely, and you have no idea whether your edit helped or you just got a different dice throw. Locking the seed makes iteration a controlled experiment instead of a slot machine. It costs nothing and it's the difference between converging in four generations and flailing through twenty. ## How it works `seed` is accepted on both image and video generation. Same seed plus same prompt plus same parameters gives you the same output. Change the prompt and hold the seed, and the delta you see is attributable to the prompt. ``` seed unset: gen 1 "product on marble, soft light" → overhead shot, warm gen 2 "product on marble, soft light, 4k" → side shot, cool Did "4k" change the angle? No idea. seed=8812: gen 1 "product on marble, soft light" → side shot, warm gen 2 "product on marble, soft light, 4k" → side shot, warm, sharper Now you know what "4k" did. ``` ## The loop ``` 1. Generate unseeded 3-4 times → find a composition you like 2. Note that job's seed → from the generation record 3. Lock it → seed=<that value> 4. Change ONE thing per generation → prompt, or one parameter 5. Judge the delta → it's now attributable 6. Unlock when composition is wrong → back to step 1 ``` **Step 1 matters.** Locking a seed too early locks you into a bad composition and