PromptZone - AI Prompts, Guides and Tools for Builders: sarah wilson

I Started Testing AI Video Prompts One Variable at a Time

sarah wilson — Fri, 28 Aug 2026 02:11:35 +0000

When an AI video prompt fails, my first instinct used to be adding more detail.

More camera instructions. More lighting. More descriptions of motion. More words explaining what should happen.

That often made debugging harder.

Lately I've been using a simpler approach: change one variable at a time.

I started applying this method while exploring Minimax H3 Max and other short-form video generation workflows. Instead of trying to write the perfect prompt immediately, I use three small prompt passes to figure out where the generation starts to drift.

Pass 1: Test Only the Action

Start without cinematic language.

A ceramic coffee cup sits on a wooden table.

A hand enters from the right, picks up the cup,
and moves it out of frame.

The table and background remain stationary.

At this stage, I don't care much about atmosphere or camera style.

I'm checking three things:

Does the hand enter from the correct direction?
Does it interact with the cup?
Does the rest of the scene remain reasonably stable?

If the basic action doesn't work, adding a dramatic camera move probably won't fix it.

Pass 2: Add the Camera

Once the action is reasonably clear, I add one camera instruction.

A ceramic coffee cup sits on a wooden table.

A hand enters from the right, picks up the cup,
and moves it out of frame.

The camera slowly pushes forward toward the cup.
Keep the movement smooth and continuous.

I avoid adding several camera commands at once.

For example, this is harder to diagnose:

Push forward, orbit around the cup, tilt downward,
then pull back as the hand enters.

If the result fails, I don't know which instruction caused the problem.

One camera behavior gives me a cleaner test.

Pass 3: Add the Look

Only after the action and camera direction are established do I add visual styling.

A ceramic coffee cup sits on a wooden table.

A hand enters from the right, picks up the cup,
and moves it out of frame.

The camera slowly pushes forward toward the cup.
Keep the movement smooth and continuous.

Soft morning window light.
Natural shadows.
Warm, understated commercial photography.
Realistic materials and restrained contrast.

Now the prompt has three layers:

ACTION
+
CAMERA
+
LOOK

That structure makes revisions much easier.

Keep a Failure Note

The most useful change was actually outside the prompt.

After every generation, I write one short note:

v1 — action works, camera missing
v2 — camera works, hand enters too early
v3 — timing improved, cup changes shape
v4 — acceptable

This prevents me from rewriting the entire prompt based on a vague feeling that the previous result was "not quite right."

It also creates a small history of what actually changed.

A Reusable Template

This is the template I now start with:

SUBJECT:
[What must remain recognizable?]

ACTION:
[What should happen?]

CAMERA:
[Choose one primary camera behavior.]

TIMING:
[When should the important action happen?]

ENVIRONMENT:
[What should remain stable?]

LOOK:
[Lighting, mood, texture, visual treatment.]

For example:

SUBJECT:
A red sports shoe on a concrete pedestal.

ACTION:
The shoe remains stationary while a thin layer
of mist moves behind it.

CAMERA:
Slow 30-degree orbit from left to right.

TIMING:
Keep the orbit continuous for the full shot.

ENVIRONMENT:
Do not move the pedestal or background.

LOOK:
Soft directional studio light, subtle shadows,
clean product-photography aesthetic.

The important part isn't the exact wording.

It's the separation of responsibilities.

Why I Prefer This to “Perfect Prompt” Templates

Long prompt templates can be useful, but they sometimes hide the source of a failure.

If a prompt contains subject motion, environmental motion, three camera instructions, lighting, lens language, composition, timing, and style all at once, a bad generation doesn't tell me much.

Testing one variable at a time gives me a better question:

What changed between the last useful result and this one?

For Minimax H3 Max or any other video model, I wouldn't treat this framework as a guarantee that every instruction will be followed. Generative video still varies between runs.

It's simply a more manageable way to iterate.

The Short Version

When a video prompt isn't working, I now avoid immediately making it longer.

I test it in this order:

Action — can the model produce the basic event?
Camera — can it maintain one clear camera behavior?
Look — can styling be added without breaking the first two?

Then I change one thing and run it again.

It sounds slower than writing one giant prompt.

In practice, I've found it makes failed generations much easier to understand.

I Get Better AI Video Prompts When I Write the Camera First

sarah wilson — Tue, 25 Aug 2026 09:01:47 +0000

When I first started writing prompts for AI video, I described what I wanted the final image to look like.

Something like:

A cinematic futuristic city at night, beautiful neon lighting, dramatic atmosphere, highly detailed, realistic.

It sounds descriptive, but there's a problem: almost everything in that prompt describes appearance.

Very little explains what should actually happen during the shot.

Lately I've been using a different approach. Before describing style, I write the camera and action.

Start With the Shot

For a simple product scene, I might begin with:

Medium shot. The camera slowly pushes toward a bottle standing on a table. The bottle remains centered while soft reflections move across the surface.

Only after that do I add the environment:

Dark studio background with soft directional lighting and subtle reflections.

Then I add style if it's actually necessary:

Clean commercial product photography, restrained contrast.

The complete prompt becomes:

Medium shot.

The camera slowly pushes toward a bottle standing
on a table. The bottle remains centered while soft
reflections move across the surface.

Dark studio background with soft directional lighting
and subtle reflections.

Clean commercial product photography with restrained
contrast.

This structure is much easier for me to edit than a long paragraph of adjectives.

The Four Parts I Use

Most of my video prompts now contain four sections:

SHOT
ACTION
ENVIRONMENT
STYLE

For example:

SHOT:
Wide establishing shot. Slow forward camera movement.

ACTION:
A small electric car travels along an empty road.

ENVIRONMENT:
Mountain road shortly after sunrise. Light mist in
the valley.

STYLE:
Natural lighting, realistic materials, quiet travel-film
look.

The advantage isn't that this is some magic syntax.

It's that each section has a job.

If the motion is wrong, I look at ACTION.

If the framing is wrong, I change SHOT.

If the scene feels wrong, I adjust ENVIRONMENT.

I don't have to rewrite everything.

Describe One Camera Move Clearly

Another habit I've dropped is asking for several camera movements in one short shot.

This:

The camera pushes forward, circles the product,
tilts upward and then quickly pulls back.

may describe the sequence I have in my head, but it's also asking the model to solve several motion instructions at once.

For an initial test, I'd rather use:

The camera makes a slow clockwise orbit around
the product while keeping it centered.

Once that works, I can decide whether the shot actually needs anything else.

Simple prompts are also easier to compare because there are fewer instructions competing for attention.

Write Observable Actions

I've also become more careful with abstract words.

Consider:

The character confidently enters the room.

What does "confidently" mean visually?

I can make the action more observable:

The character walks into the room at a steady pace,
keeps their head raised and stops beside the desk.

The second version describes things that could actually appear in frames.

The same principle works for objects.

Instead of:

The car moves dramatically.

I would write:

The car accelerates from a stop and passes the camera
from left to right.

Separate Shots Instead of Writing a Mini-Movie

Long prompts sometimes contain an entire edit:

Start outside the café, move through the door,
show the barista making coffee, cut to a close-up
of the cup and finish with the customer drinking it.

That's several shots disguised as one prompt.

I now split something like this before generation.

Shot 1

Wide exterior shot of a small café.
Slow push toward the entrance.
Morning light.

Shot 2

Medium shot behind the counter.
A barista pours steamed milk into a cup.
Static camera.

Shot 3

Close-up of the finished coffee on the counter.
Very slow push-in.
Soft window light.

Even if I eventually want one continuous sequence, thinking in shots forces me to decide what each part of the video is supposed to accomplish.

Keep the Model Replaceable

I've been applying this structure while testing different AI video workflows rather than designing prompts around one generator.

For example, LTX 2.5 is one of the video models I've been looking at while thinking about more controllable and open video workflows.

But I don't want my prompt library to depend entirely on one model.

My notes therefore look like this:

shot:
medium close-up

camera:
slow push-in

subject_action:
object remains stationary

environment:
dark studio

lighting:
large soft source from camera left

style:
minimal commercial footage

From there I can adapt the wording or parameters for whatever model I'm testing.

That also makes comparisons more useful.

A Template You Can Reuse

Here's the basic template I've settled on:

SHOT:
[shot size and composition]

CAMERA:
[one clear camera movement]

SUBJECT:
[what is visible]

ACTION:
[observable movement or event]

ENVIRONMENT:
[location, background, time]

LIGHTING:
[light direction and character]

STYLE:
[optional visual treatment]

Example:

SHOT:
Medium-wide shot of a desk viewed slightly from above.

CAMERA:
Slow lateral movement from left to right.

SUBJECT:
A laptop, notebook and ceramic coffee cup.

ACTION:
Steam rises gently from the cup. Everything else
remains stationary.

ENVIRONMENT:
Quiet home office in the early morning.

LIGHTING:
Soft window light from the left.

STYLE:
Natural, understated documentary look.

It isn't necessarily shorter than my old prompts.

It's just easier to reason about.

The Prompt Is Really a Shot Specification

The biggest change for me was stopping the question:

What words will make this video look impressive?

and replacing it with:

What should the viewer actually see during these seconds?

That leads naturally to framing, camera movement, subject action, environment and lighting.

Style still matters.

But now I add it after I've decided what the shot is supposed to do.

For video generation, that order has been much more useful than starting with a pile of visual adjectives.

I Stopped Rewriting My AI Video Prompts. Debugging Them Worked Better

sarah wilson — Thu, 13 Aug 2026 02:01:07 +0000

For a long time, my response to a bad AI-generated video was simple: rewrite the prompt.

If the camera moved too fast, I changed the camera description. While I was there, I would usually tweak the lighting, add another sentence about the subject, remove a few words I didn't like, and generate again.

Sometimes the next result looked better.

Great — except I had no idea which change actually helped.

After repeating this enough times, I started treating prompts less like creative writing and more like something I could debug.

I started with five fields

Most of my test prompts now begin like this:

SUBJECT:
A pair of wireless earbuds on a white display stand.

ACTION:
The case slowly opens. The earbuds remain stationary.

CAMERA:
Slow push-in. Fixed camera height. No orbit.

LIGHTING:
Soft daylight from the left with a subtle shadow.

STYLE:
Clean commercial product shot with a neutral background.

There's nothing special about the wording.

The useful part is that each section has one job.

A few weeks ago, for example, I had a product shot where the camera kept moving farther around the object than I wanted.

The original instruction was:

CAMERA:
Cinematic camera movement around the product.

My first instinct was to rewrite the whole prompt.

Instead, I left everything else alone and changed only this:

CAMERA:
Slow push-in only.
Fixed camera height.
No orbit.
No handheld movement.

The next result wasn't perfect, but it answered a useful question: the camera instruction had been too open-ended.

That was much more useful than simply getting another random variation.

One prompt accidentally contained two experiments

Another mistake took me longer to notice.

I had written:

The camera slowly circles the shoe while the shoe rotates.

It sounded perfectly clear when I wrote it.

But when the result became unstable, I couldn't tell what I was debugging. Was the camera movement causing the problem? Was it the rotating object? Or was the combination too much?

So I split the test.

SUBJECT MOTION:
The shoe rotates slowly clockwise.

CAMERA:
Static medium shot.
No camera movement.

I tested the object rotation first.

Only after that looked reasonable did I add camera movement back.

It required an extra generation, but at least the second test told me something.

I've started doing the same thing with lighting and style.

I also use fewer words like "cinematic", "epic", "dynamic", and "professional" now.

Not because those words are always useless. They're just difficult to debug.

If I want a particular lighting setup, I'd rather write:

Strong side light, dark background, visible rim light.

than:

Dramatic cinematic lighting.

The first version gives me something concrete to change later.

The template beside my test folder

After a while, the same structure kept appearing in my prompts, so I saved a blank version:

SUBJECT:
[What needs to remain visually consistent?]

ACTION:
[What should the subject do?]

CAMERA:
[Camera position + one movement]

LIGHTING:
[Direction and quality of light]

ENVIRONMENT:
[Background and surrounding objects]

STYLE:
[Visual treatment]

AVOID:
[Problems observed in previous tests]

The last field used to be much longer.

I had copied a huge negative-prompt list from an older project and kept carrying it forward. Eventually I realized I couldn't explain why half of those terms were there.

Now AVOID starts empty.

If a test produces a recurring problem, I add something relevant. Otherwise I leave it alone.

My notes are intentionally boring

Beside each generation I keep a tiny text file.

A real entry from this kind of test looks roughly like this:

Test 07

Changed:
camera

Before:
slow orbit around product

After:
static camera + slow push-in

Result:
product shape more stable
less background distortion

Next:
keep camera
reduce subject rotation

It takes maybe thirty seconds to write.

That little file becomes surprisingly useful once there are ten or fifteen videos sitting in the same folder.

Before I started doing this, I had files called things like:

video_final.mp4
video_final2.mp4
video_final_good.mp4

I wish I were joking.

A week later, those filenames told me absolutely nothing.

I tried keeping the template when switching models

I was curious whether this approach was only useful with the generator I had been testing, so I started keeping the prompt structure unchanged when trying other video models.

One of those runs was with Wan 3.0.

I kept the same subject/action/camera structure rather than writing a special prompt for the model. That made differences easier to spot because I wasn't changing the model and the entire prompt at the same time.

Some wording still needed adjustment, which I expected. But I had a baseline instead of starting from an empty text box.

That's the part of the workflow I've found most useful.

When a generation looks wrong now, I don't immediately ask myself how to write a better prompt.

I open the last test note and look for the smallest thing I can change.

I Stopped Rewriting My Entire AI Video Prompt After Every Bad Result

sarah wilson — Mon, 10 Aug 2026 09:02:02 +0000

For a while, my response to a bad AI video was always the same: rewrite the prompt.

If the camera felt wrong, I'd change the camera instruction. Then I'd tweak the lighting, rewrite the action, remove a few words, add a few more.

Generate again.

Sometimes the next video was better, but there was an obvious problem: I had no idea which change actually helped.

I'd changed too many things at once.

Recently I've been trying a much less exciting approach with Seedance. I change one thing and leave everything else alone.

Say this is my starting prompt:

A black coffee machine on a kitchen counter. Slow camera push-in. Morning light from the left. Steam rises from a cup beside it. Keep the machine stationary.

The result is usable, except I don't like the camera movement.

Instead of rewriting the prompt, I test only that line.

Test A

Slow camera push-in toward the product.

Test B

Camera moves slowly from left to right while keeping the product centered.

Test C

Static camera. Only the reflections and steam move.

Everything else stays exactly the same.

This gives me three results I can actually compare. If one works noticeably better, at least I have some evidence that the camera instruction made the difference.

It sounds obvious when written down, but I wasn't doing this before.

I was treating every failed generation as a reason to write a better prompt rather than trying to find the part of the existing prompt that wasn't working.

I've been using this approach while experimenting with Seedance, although the method should work with other video models too.

I've also tried the same thing with motion.

If an interaction looks strange, I'll keep the scene, lighting, and camera unchanged and test small variations:

The hand slowly reaches toward the cup.

Then:

The hand reaches toward the cup and pauses before touching it.

And:

The hand remains still beside the cup.

This takes a few generations, but I usually learn more from those generations than I do from repeatedly replacing the entire prompt.

Another thing I've noticed: adding detail isn't always the fix.

Sometimes I remove the instruction that I think is causing trouble and generate again. A shorter prompt occasionally gives me a much cleaner result.

So lately, when a generation goes wrong, I don't immediately ask myself how to improve the whole prompt.

I just try to figure out which instruction I want to test next.

Does anyone else test video prompts this way? I'm curious whether you change one variable at a time or tend to rewrite the prompt when the first result doesn't work.

I Started Keeping the Prompts That Failed

sarah wilson — Fri, 07 Aug 2026 01:48:37 +0000

I used to save only the prompts that worked.

If a generation looked good, I'd copy the prompt into a text file and give it a name like:

camera-good.txt
night-scene-final.txt
character-motion-v2.txt

The failed ones usually disappeared.

At the time that felt sensible. Why keep something that didn't work?

A few weeks later, though, I'd open one of those "good" prompts and have no idea why half the lines were there.

For example:

Keep the subject centered.
Maintain facial identity.
Avoid sudden camera movement.

I knew those lines had probably fixed something at some point.

I just couldn't remember what.

So I changed one small habit: I stopped deleting the bad versions.

My folders are messier now.

A recent one looked like this:

01.txt
02.txt
03-face-changed.txt
04-camera-static.txt
05-better.txt
06-too-fast.txt
07.txt

Not elegant, but at least I can follow what happened.

I usually leave a short note for each version:

03
face changes during turn

04
face is better, camera barely moves

05
camera works, walking too fast

That's normally enough.

I don't score every result. I tried doing that once and stopped after a few days because I was spending too much time deciding whether something deserved a 7 or an 8.

One camera test is a good example of why I keep the old versions now.

I started with:

Camera slowly moves closer while following the subject.

The movement wasn't what I wanted, so I made the instruction more specific:

Smooth cinematic tracking shot, gradually moving
toward the subject while maintaining stable framing.

It got worse.

Then I tried:

Slow forward tracking shot.

That version behaved better.

I wouldn't turn this into a rule about short prompts. I've had other scenes where adding detail helped.

The only thing I wrote in my notes was:

longer camera description didn't help this scene

A month later, that note was more useful than trying to remember why the final prompt was short.

Old prompts became more useful when I changed models

I ran into the same thing again while going back through old prompts during a MiniMax H3 test.

My normal habit had been to take the best prompt from the previous model and use that as the starting point.

It sounds reasonable, but there's a problem with it.

A successful prompt often contains fixes for problems that belonged to the model I was using at the time.

I found a very simple example in an older folder:

v1
Woman turns toward the window.

result
body turns, face changes

Then:

v2
Woman turns toward the window.
Keep the same facial features during the turn.

result
face is more stable

The second line stayed in my prompts for months.

I copied it into other scenes, then into other projects.

At some point I couldn't remember which model had originally needed it.

When I tested the old v1 again with a different workflow, the face stayed reasonably consistent without the extra instruction.

So the sentence I'd been treating as part of my normal prompt wasn't really a rule. It was an old patch.

I started noticing more of these.

Keep camera distance consistent.

Preserve clothing throughout the scene.

Maintain natural body proportions.

Do not change the background layout.

Some are still useful.

Others are probably there because something went wrong in a generation months ago.

If I only keep the successful prompt, I lose that history.

Keeping the version immediately before it tells me why a line was added.

That's also why I don't clean up my test folders as aggressively anymore.

I did try replacing all of this with a spreadsheet once.

It had columns for:

model
prompt
settings
duration
failure
score
notes

I abandoned it fairly quickly.

For short experiments, it felt like more work than the testing itself.

Now I normally keep a folder and a small notes.txt file:

01 - baseline
camera static

02 - added tracking
camera moves, face okay

03 - added cinematic lighting
can't see much difference

04 - changed walking speed
too fast

05 - reduced walking speed
usable

This isn't particularly organized, but I can open the folder a few weeks later and understand what I was doing.

It also makes me a little less likely to rewrite everything after one bad result.

If 04 doesn't work, I usually want 05 to differ in one obvious way. Otherwise I end up with two completely different prompts and no idea which change mattered.

Not every test works like that. Sometimes the result is bad enough that I throw out the prompt and start again.

I just don't delete the old one anymore.

I've also stopped naming files like:

final.txt
final2.txt
final-new.txt
final-really-final.txt

I had enough versions of those that "final" stopped meaning anything.

Numbering them is boring, but it works.

These days I usually keep the whole experiment folder. Text files take almost no space, and three weeks later I rarely remember why 04.txt was bad without the note sitting next to it.

I Stopped Rewriting Product Video Prompts From Scratch

sarah wilson — Fri, 24 Jul 2026 06:13:48 +0000

Yesterday I was putting together a short landing page video for a side project.

Nothing complicated—just an 8-second product clip.

I opened my notes to write another prompt and realized I had already written almost the same thing dozens of times.

The product was different.

The wording changed a little.

But most of the prompt stayed exactly the same.

So instead of starting over again, I copied the version I used last week and only changed the parts that actually mattered.

This is the version I ended up using yesterday.

Subject:
Portable coffee grinder

Action:
Slow 360° rotation on a wooden table

Camera:
Gentle push-in, close-up near the end

Lighting:
Soft morning light from the left

Background:
Minimal workspace

Style:
Simple product commercial

Avoid:
Fast camera movement
Floating objects
Text overlays

I used to rewrite every field because it felt more "creative."

Now I almost never do that.

Most of my changes happen in just two places:

the subject
the action

Everything else usually stays untouched unless I'm testing something specific.

One thing I started doing recently is keeping the prompts that didn't work.

A few weeks ago I would have deleted them.

Now they sit in a folder called rejected.

It's surprisingly useful to look back and remember why something failed.

Sometimes the camera moved too much.

Sometimes the background became too busy.

Sometimes I simply added too many instructions.

Seeing those old prompts again saves me from making the same mistake twice.

Lately I've also been running the exact same prompt through different video models without changing anything.

I don't really care which model "wins."

I'm more interested in how each one interprets identical instructions.

One of the models I tested this week was Seedance 2.5. I left the prompt exactly as it was so I had another point of comparison instead of another rewritten version.

The folder is still messy.

Some prompts have strange names.

Some experiments don't go anywhere.

But copying an old prompt and improving it a little has been much more useful than trying to invent a completely new one every time.

If you keep old prompts around instead of deleting them, I'd be curious to know how you organize them. I'm always looking for better ways to keep this folder under control.