A style is not a prompt

A prompt is a description of something you want. You write it, you look at what comes back, you adjust. The loop is short and you are inside it, which means the prompt never has to be complete — your judgement fills in whatever it leaves out.

A style is different, because you are not in the loop. Somebody else picks it from a list, points it at footage you have never seen, and ships whatever comes out. Every gap your judgement was quietly filling is now a gap in the product.

So the useful question stops being does this look good and becomes what am I guaranteeing, and under what conditions does the guarantee hold.

What a guarantee looks like

Not “warm, cinematic, shallow depth of field.” That is a description. It cannot be checked, and two people will read it differently.

Something closer to:

• Contrast structure is fixed. Shadow sits at a defined level regardless of source.
• Colour adapts to the source within a bounded range.
• Fine texture is applied once, at a known stage, so it cannot destabilise.
• Below a certain source light quality, the style declines rather than degrades.

Each of those is testable. You can put a clip through and say whether it held. That turns disagreements about taste into disagreements about whether a specific guarantee held on a specific clip — a much shorter conversation, and one that can be had without both people in the room.

The part that changes how you work

Once a style is a set of guarantees, stating where it fails becomes part of delivering it. Not a caveat you add if someone asks — a section of the spec.

That felt wrong to me at first. Naming the conditions where your work falls apart seems like an argument against the work. In practice it is the opposite: a style with documented limits is one someone else can use correctly, and a style with no stated limits will be used somewhere it does not belong and get blamed for the result.

The version of this I keep coming back to: a look is something you make. A style is something you hand over.