Brand kits are the new style guide

A saved kit is injected into generations so hex, type, logo and tone survive a hurried prompt. A PDF style guide does not.

The old style guide was a document people forgot the day a deadline arrived. Generation made that failure mode worse, not better. Every run is a fresh sample. Anything that must be identical across runs has to be supplied as a constraint, not hoped for, and not retyped into the prompt by whoever is awake. That is the whole argument for a brand kit: store the non-negotiables once, and let the studio fold them into later jobs by default.

This is not a feature brochure. It is the practical split a team actually hits: what the kit binds, what it only leans on, and what still has to be a reference photograph.

The kit is the constraint that survives hurry

A brand is the part of the work that is not allowed to be stochastic. Models are. If the only copy of "we are #0B1F3A, never Comic Sans, logo clear on the left, 9:16 unless the brief says otherwise" lives in a Notion page, you will get a 16:9 cream thumbnail from a contractor at 11pm. If that same list lives in the kit, the hurried job still inherits it.

On Versely the kit is held per account. Set my brand kit is the named job: colours, fonts, logo, tagline, voice tone, caption style, default aspect ratio. Saving does not spend generation credits. The save is a partial upsert — a caption style this week does not wipe a logo set last month; colours and fonts merge by key. From then on the kit is auto-injected into context so a generate or a workflow does not need the look restated.

That last sentence is the difference between a kit and a pasted paragraph. A pasted paragraph survives only in the thread where you pasted it. A kit survives the teammate, the scheduled run, and the day you were too tired to paste.

What belongs in the kit is the stuff a style guide used to print on page one:

hex values you will actually use on type and surfaces you control
the typefaces for captions and overlays
the logo file, not a description of the logo
the default frame shape, so a vertical brand stops emitting accidental 16:9
tone as a brief a writer would understand: what it never says, not only "friendly"

What does not belong in the kit is a one-off for this request ("make this one darker"), a reusable face (that is an asset upload), or a standing routing rule that is not a brand value ("always 8 seconds on Veo"). Memory jobs exist for durable preferences that are not hex. Mixing those drawers is how every future clip arrives darker, or how a logo description is treated as a sentence instead of a file.

Hard binds and soft leans

A kit is not equally strict in every part of the pipeline. Pretending it is will make you distrust the kit when the model invents a warmer wall.

Hard binds — overlays, captions, surfaces the studio typesets. A hex is that hex. A font is that font. A caption preset is that preset. Caption styles are the catalog of looks; the kit is how the chosen look stops being a per-video decision. Burned-in type is the place a style guide always had teeth. Keep using it that way. If the caption sits in the TikTok UI, that is a safe-area problem, not a "the model ignored our navy."

Soft leans — pixels inside a generated frame. The same navy, written into a prompt via the kit, is guidance competing with the lighting the model chose. A kitchen can go amber because the prompt said late afternoon. The overlay can stay navy. Both things can be true in one file. The pitfall in the glossary is the right one: treating a hex in the kit as a guarantee inside generated imagery.

References beat adjectives for products and people. The reliable way to hold a real pack's shape, colour, and label is to store the product photographs and attach them, not to describe "our teal carton with the white serif." The kit should point at those files. Seedance-class video rows that take a stack of references are how the pack survives a language change or a new camera move. A kit without product stills is a colour story. A colour story will not letter a label you can read.

Tone is a lean unless you enforce it in review. "Playful but not sarcastic" will shape copy the agent writes and will not stop a talking-head generate from smirking. Watch the take. The kit is a prior, not a legal department.

Knowing the bind vs lean split is what makes the kit usable. Teams that expect the wall to match the hex will disable the kit the first time a generate is warm. Teams that expect the caption and the logo lockup to match, and the room to be near, will keep the kit on.

How a team actually runs one

One kit per brand, not one kit per person. If the agency runs three clients, that is three kits, not a super-kit with a paragraph of exceptions. Exceptions are how navy becomes "navy unless we feel it."

Set it before the first batch, not after the fiftieth near-miss. The cheap moment is empty. The expensive moment is a folder of almost-on-brand clips you will not recaption.

A practical order:

Lock the typesetting. Caption family, colours, fonts, default 9:16 or 16:9. Generate one silent talking-head and one product still. Read the type at phone size. If it fails here, nothing later will save it.
Lock the logo as a file. Not "small wordmark, bottom left" as a sentence. A file. Check that it is not being regenerated as a cousin of itself.
Store the product shots. Pack, label, the three angles you actually use. These are references, not decorations.
Write the never-list into tone. Claims you will not make, words you will not use, the difference between dry and cold. This is the part of a style guide that was always more useful than the moodboard.
Run a three-file audit whenever someone changes the kit. One captioned clip, one still, one talking take. Partial upserts are safe until they are not — a new caption style should not surprise you on a client export.

Workflows and scheduled jobs are why the kit has to be the default rather than a prompt habit. A human can remember navy. A queue cannot. If the kit is empty, the queue will invent a look and you will call it a model problem.

The kit is also how captions stay a language of the brand across a multilingual set. The transcription pass can run in 165 language codes; the look of the type should not change because the language did. Line length will change. The family should not.

Do not keep a second, secret style guide in chat memory. If it is a hex, a font, a logo, or a caption preset, it is a kit field. Memory is for "audience is gen-z gamers" and "when I say caption I mean burn-in." The named split exists so a hex is not re-parsed out of a paragraph every generate.

What the kit will not do

It will not make two generated faces the same person. That is character consistency, assets, and references.

It will not make a cinematic model look like a phone UGC ad. That is the brief. If the brief says handheld and the kit says navy and clean type, you can have both: messy picture, strict overlay. If you wanted messy type, you picked the wrong caption family.

It will not replace review. A kit-injected generate can still letter a pack that is almost yours. Almost is how you ship a cousin SKU. Look at the label.

It will not survive a teammate who pastes a full competing brief into the prompt. Injection is a default, not a lock. Overrides exist because one-off jobs exist. Teach people that an override is a decision, not a habit.

It will not be a PDF. Export a human-readable summary if legal wants a document. Do not let the document become the source of truth again. The source of truth is the kit the next generate will actually see.

When the next batch should inherit the look without a pep talk, sign up, save the kit once, and stop pasting the style guide into the prompt.

FAQ

Is a brand kit the same as agent memory?

No. The kit stores brand assets and typesetting: colours, fonts, logo, tone, caption style, default aspect. Memory stores standing rules that are not those fields. A hex in memory will not land as a file. A one-off "make this darker" in the kit will haunt the next month.

Why didn't the generated kitchen match our hex?

Because inside a generated frame the kit is guidance, not a typesetter. Overlays and captions bind hard. Walls and light lean. If the product has to match, attach product photographs as references instead of describing the colour.

Does saving a new caption style wipe the rest of the kit?

No. The save is a partial update. Fields you do not pass stay. Colours and fonts merge by key. Still run one test export after a change, because the caption family is the thing the feed sees first.