Brand kit
Read video-edit-rules first. Its rules apply to every step here.
The goal: any edit for this client starts from saved numbers, not from memory. The test: a new chat can make an on-brand video from the kit alone, and no review note comes twice.
Step 1. Make the folders
<client>/
brand/
style.md the style file (step 3)
theme.css colour tokens as CSS variables
fonts/ font files with their licences
logo/ logo files (SVG first, PNG at 2x)
pieces/ reusable HTML pieces (step 4)
sfx/ approved sound effects, each with its level
feedback.md every review note and the rule it became (step 5)
refs/ reference edits the client likes, with a note on each
source/ raw footage, never changed
work/ scratch
out/ versions
NOTES.md
Step 2. Onboarding questions
Ask one question at a time. Offer your best guess as the first answer, so the client can just say yes. Stop at 8 questions. Find the rest from their posts.
- Which 2 or 3 videos (theirs or anyone's) feel most like the look they want?
- Where will the videos run: Reels, TikTok, Shorts, paid ads, YouTube?
- What are the brand colours, as hex? If none: may I sample them from the logo or the website?
- Which fonts do they own or use? If none: may I pick free ones that match the logo?
- Captions: on all the time, or only for key lines? Title Case or sentence case?
- Music: yes or no? Any genre they never want?
- Anything they never want to see or hear? (For example: emojis, sound effects, cut-outs, fast zooms.)
- Who signs off, and how many review rounds per video?
Write the answers into brand/style.md the same day.
Step 3. Measure the style file
Do not write "bold, modern, clean". Write numbers.
- Pick the client's best reference from
refs/. Measure it as incopy-a-reel, step 4. - Sample brand colours from the logo SVG (exact) or from 5x5 px patches on 3 frames (median).
- Fill
brand/style.mdwith these sections:
| Section | Example of a good line |
|---|---|
| Frame | 1080x1920, 30 fps, text in y 220 to 1470, right 140 px clear below y 1100 |
| Captions | Inter 800, 84 px, letter spacing -0.03em, 2 lines max, white, shadow 0 2px 12px rgba(0,0,0,.45), top at y 1180 |
| Hero word | 1.9x the caption size, one per line at most |
| Colours | --base #101820 background; --accent #2f80ed key words; --warn #e5484d problems |
| Pieces | pill 96 px high, radius 48, padding 0 40px; card radius 32, shadow 0 24px 60px rgba(0,0,0,.3) |
| Motion | word pop 0.24 s, ease back-out 1.6, rise 18 px; scene cut on the word, 2 frames early |
| Camera | punch-ins 1.0 / 1.15 / 1.32x, change at each cut |
| Rhythm | scenes at most 15% of runtime; pauses between thoughts 0.25 to 0.4 s |
| Sound | soft pop at -22 dB under the voice; bed at -20 LU; mix -14 LUFS, peak -1.5 dBTP |
| Case | Title Case |
| Do not | (filled from feedback, step 5) |
- Copy the colours into
brand/theme.cssas variables. Every piece reads colours from there. - Put each font file in
brand/fonts/with its licence. Note any font you replaced and why.
Step 4. Build the reusable pieces
Start from $KIT/templates/. Copy what fits into brand/pieces/ and set it to the style file.
A good first set:
- Caption block (2 lines, under the chin).
- Hero word.
- Key-word pill.
- Lower third with name and title (from the client, never invented).
- List card, one item per spoken item.
- Number card that counts to a spoken number.
- Phone frame with a real-looking OS screen.
- End line (the spoken call to action, no extra words).
For each piece:
- Fill it with a real line from the client's footage.
- Run
python $KIT/scripts/layout_check.py brand/pieces/<piece>/index.html. - Render a 3 s sample. Save one still as
brand/pieces/<piece>/preview.png.
Show the client one sheet of all previews. Ask which to change. Fix them before the first real edit.
Step 5. Turn feedback into rules
Every review note becomes a line in brand/feedback.md and, when it is general, a rule in brand/style.md.
Format of a feedback line:
2026-03-14 | v02 at 12.4 s | "the pop is too loud" | pop was -12 dB under voice | Rule: effects at -22 dB or lower
- Write the note in the client's own words.
- Write what you measured at that moment.
- Write the rule as a number or a ban, not as a feeling.
- Add the rule to the right section of
style.md. - Before each new edit, read the "Do not" section and the last 10 feedback lines.
- If the same note comes a second time, the rule was not enough. Add a check to the quality gate for it (a script check, not more text) and say so.
Step 6. Change the brand later
- New colours: edit
theme.cssonly. Render one still per piece and compare old and new. - New fonts: size the new font to the same ink width per word as the old one, so layouts do not break.
- Log the change with its date in
style.md.
Report
- Folders made.
- Answers still missing.
- The style file sections filled, and any value you could not measure.
- Pieces built and their layout check result.