Prasith Govin

← All notes

picking the colors before the model does

2 min read

Nearly every Claude Opus 5.5 product video I saw in September had the same look. Purple glow on near-black. Tiny uppercase labels in the corners. "01 / 03" step counters, fake timestamps, scanlines, a particle globe, words flashing in one at a time.

That look is what you get when the model picks the colors and the words. One reply under a popular example asked the author to get rid of the "small caps and 01/03 everywhere."

For the Parker teaser I wrote the brief before any code existed and split the job in two. I owned the words and the look. Opus owned the motion.

The brief was specific enough to check against the render:

Opus built it in Remotion, rendered a 16:9 and a 9:16 cut at 60 frames per second, and checked its own contact sheet against the brief before handing it over.

The light theme started as a way to look different from the wave. It held up for a better reason. Parker is built for people with effortful speech, starting with my dad, and the viewer I care about can't read tiny gray UI on black. Big dark type on warm paper is legible. The trend look would have been wrong for the audience before it was wrong for the brand.

What I'm keeping: when a model has a strong default, the brief has to name the default and ban it. A brief that says "clean and modern" leaves those choices to the model. A hex list, a timing rule, and a banned list got me something I could check line by line.

The teaser is 30 seconds and sits under Parker on the front page.