0:35 · Iterate Like a Director
Goal: turn one lucky result into a deliberate one — and then teach Loft what you learned so you never have to say it again. Ten minutes. This is the lesson that separates using Loft from using a prompt box.
Three levers, in order of leverage
1 · The words
2 · The inputs
3 · The model
Step 1 — Regenerate with one change
- Expand your completed queue card and click Regenerate — it brings the whole setup back, prompt and parameters intact.
- Change one thing. Swap "dusk" for "hard noon light", or "wide establishing" for "low-angle close".
- Generate again, and compare the two results side by side in the asset's Files.
Do this twice. Two deliberate revisions teach you more about a model than twenty random rerolls.
Step 2 — Bring in a reference
Now use the image you marked Reference in lesson 2. Pick a model that takes image input (an image-to-image or image-to-video type pill). Its setup form shows input slots above the prompt, each labeled by the role it plays — First Frame, End Frame, Reference Images, Input Video, Reference Audio.
- Click a slot to open the picker; it browses this asset's own files. Click Pinned to see what's pinned in the Assistant instead. Select your reference and click Done.
- Each tile carries a status badge. By default the picker offers only Published files, plus Selected ones when they belong to this asset. The status dropdown widens that if you need a New or Dropped take.
- Notice the @-mention badge it gets —
@Image1,@Image2, and so on. - Name the badge in your prompt to say what each image is for: "match the color palette of @Image1". Attaching an image without saying its job is the most common way references get ignored.
Step 3 — Keep the language that worked
When a phrasing earns its keep, click Save current prompt as primer above the prompt box. A primer is a reusable prompt block you inject on demand — yours (My Primers), the project's, or system-wide. Next time you generate, it's one click instead of retyping.
Step 4 — Write your project playbook
This is the highest-value five minutes in the whole hour. Go to Project Detail and click the book icon in the header to open the Project Playbook.
A playbook is free-form standing guidance the Assistant reads every turn — house style, default sizes, naming conventions, model preferences. Write three or four short declarative lines, like:
- House look is 35mm film, warm, slightly hazy. Avoid clean digital renders.
- Default to 16:9 for shots, square for character reference.
- Always generate one image first; only make variations when I ask.
- Name shots SHxxx, three digits, zero-padded.
Keep it short and declarative — it's read on every request, so concise rules beat long prose. Playbooks layer: project, then asset, then your personal defaults, each refining the last. Primers are pull; playbooks are always-on.
Step 5 — Try it in words instead
Now open the Assistant from the header and just ask: "generate another take of this shot, tighter framing, same light."Same generation machinery, no form. The Assistant reads your playbooks on every turn, so the guidance you just wrote is already in play.
One phrasing rule worth internalizing: imperative phrasing executes, desiderative phrasing discusses. "Generate X" acts. "I'd like to explore X" talks it through first. Choose deliberately.
Checkpoint
- Your asset holds three or more takes, and you can say why each differs from the last.
- At least one generation used a reference image, named in the prompt by its @-badge.
- Your project playbook has a few lines in it.
- You've asked the Assistant for something and gotten a result.