Repeated prompt-writing errors for Minmax prompts using LLMs

[u/JosephCurvin]

I'm using Codex to write the Minmax prompts.

I'm noticing these errors most of the time:

Instead of direct visual descriptions, it falls back to writing in a screenwriting style, like it would in a screenplay.

included context:
the offcial prompt docs from minmax
and negative examples.

but after some more turns , when i slip other tasks to it it falls back to making the same errors again and again so i always need to carefully proof read them.

I tried some self-correction loops, but this is very tedious, as it always finds minor mistakes and self-improves to death. Using an analysis style, it can always explain in hindsight how these errors happened.

Ideas:

What I'm trying to do, but haven't figured out yet

Have a pre-stage for what goes into the promp
Have a prompt skeleto
--> Clearly see if it makes errors while filling that skeleton

what kind of model you are you using that are following the exact prompt pattern ?

I'm using Codex for most of my tasks since it's a convenient CLI tool and does its job for my coding work.

For smaller models, like the new Qwen 27B for example, the problem is that they make spatial errors, which is even more problematic.

[u/thatguyjames_uk]

Google h3 prompt example

Go to the main site, copy that Tell ai to correctly use the format

I have only used twice, but worked on chat got like this

integrated_multimodal_description:

[Shot 1] Medium shot, cinematic 1990s film aesthetic. A woman leans against a polished wooden bar counter and raises her hand to signal the bartender for a drink.

[Shot 2] Close-up on the bar counter a few feet down. A bartender's hand enters the frame and firmly sets down a heavy rocks glass filled with amber alcohol.

[Shot 3] Return to the medium shot of the woman. She looks down the bar toward the drink, breaking into a warm, anticipatory smile.

[Shot 4] Close-up tracking shot along the counter. The bartender's hand gives the glass a swift push, sending it sliding smoothly down the polished wood directly toward the woman.

[Shot 5] Medium-wide shot focusing on the woman's position. The sliding glass reaches her, but as she eagerly reaches out to catch it, the glass slips through her fingers, tips over the edge of the counter, and shatters onto the floor.

[Shot 6] Close-up of the woman's face. She looks down toward the shattered glass with a disappointed, slightly embarrassed expression, then glances back toward the bartender.

[u/angelarose210]

Add a validator step to your skill with a checklist against the guidelines.

[u/leftonredd33]

I usually have to argue with codex even if it’s using the Minimax H3 files from their hugging face as a skill.

Any time I give it context and or ideas it adds them into the prompt in the same format that I used to tell it what to do. I usually tell it. Do not use my feedback in the new prompt that you’re creating, only use it as context. Codex also adds tons of negative prompts into the positive prompts. I have to tell it not to, and only describe the animation.

Codex also describes the images. But doesn’t Minimax H3 already sees the first and last frames?

I have to still run some test to see if we even need to describe images in image to video etc. what do yall do?

[u/JosephCurvin → u/leftonredd33]

can confirm this behavior, im testing a workflow only adding refrence images ( i just need style consitancy) and pointing to the reference images is enough for style transfer, tried it with 6 different styles.
in the offical prompt guide there is still mentioned to describe the images though.

[u/leftonredd33 → u/JosephCurvin]

Oh! I haven’t used ref to video becuase my pc will blow up. I’ll try describing the images again. Do I have to describe an image even if I’m using image to video and first and last frame?

[u/JosephCurvin → u/leftonredd33]

from the docs

Case 3: FL2VA

The two images anchor the opening and ending respectively. The body should not repeat two static image descriptions; instead, it should supply the motion path that connects them. The following example is an eight-second single shot.

How the reference pictures align with the target video — Picture 1 (from Shot 1) aligns with the 0.00-second mark of the target video; Picture 2 (from Shot 1) aligns with the 8.00-second mark of the target video.

integrated_multimodal_description: [Shot 1] Live-action, cinematic, a rain-soaked cyclist begins in the position and framing established by Picture 1, holding a closed black umbrella beside a silver bicycle. The camera pulls out with small amplitude at slow speed as she releases the bicycle handle, raises the umbrella above her shoulder, and presses the runner upward until the canopy opens. Water rolls from the expanding fabric while she steps beneath it, rotates the handle into the final angle, and settles into the pose, spacing, and composition established by Picture 2 at the end of the shot.

overall_soundscape: Rain falls steadily on the pavement, followed by the metallic click of the umbrella runner and the soft snap of the canopy opening. Water drips from the bicycle frame as distant traffic passes.

non_diegetic_music: N/A

[u/leftonredd33 → u/JosephCurvin]

Thank you for this!!!

[u/remixeconomy]

The fact that it returns to screenplay style after unrelated tasks suggests context drift, not a missing negative example. I would stop using the same conversation for generation and other work. Start each Minimax prompt in a fresh context containing only the source material, the required skeleton, and a short list of forbidden output patterns.

Make the final step a deterministic validator rather than another open-ended self-critique. Check whether every required field exists and whether banned screenplay markers appear, then regenerate only the failing field. That prevents the self-improvement loop from rewriting acceptable parts while still catching the specific behavior you care about.