video-brand-system
Skill18 starsChanged 48 days agoMITView on GitHub
Define or apply a product's consistent video style across demos, tutorials, films, and clips. Use when establishing video colors, type, motion, sound, framing, covers, and export rules from a real brand.
In this repository10 other files it gives its agents.
- brand-filmSkill
- brand-grid-videoSkill
- creator-videoSkill
- feature-videoSkill
- narrated-product-filmSkill
- silent-product-demoSkill
- social-video-hooksSkill
- ui-component-clipSkill
- ui-tutorial-videoSkill
- video-thumbnailsSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Create a small set of production rules that lets separate videos read as the same product.
- Distinctive: line 28
Do not force every genre into one template: a component loop, tutorial, and brand film may use different shot grammar while sharing the …
- Distinctive: line 30
Before delivery, compare exports side by side.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Video brand system
Create a small set of production rules that lets separate videos read as the same product. Derive the rules from approved brand sources and the actual interface rather than inventing a parallel visual identity.
Gather the source of truth
Inspect the product's design tokens, UI, mark, typography, motion, and approved examples. Record the source for each choice. Separate facts from preferences: a UI component's dimensions and easing may be fixed, while the background treatment for a campaign can be chosen.
Define only what production repeatedly needs:
- palette roles for background, surface, text, and accent;
- type families, weights, and safe text sizes by format;
- framing and camera behavior;
- entrance, settle, transition, and hold timing;
- sound roles for voice, interface effects, music, and silence;
- cover and closing treatment;
- export formats and quality checks.
Apply it consistently
Keep reusable motion and design values in one place when the video project supports shared components. Use the real mark and UI assets. If reconstructing UI for a frame-based renderer, trace each visible surface to app or design source and animate from video time so renders are repeatable.
Do not force every genre into one template: a component loop, tutorial, and brand film may use different shot grammar while sharing the same visual and sound language. Update the system when the product changes, then check existing videos for visible drift.
Before delivery, compare exports side by side. Look for changed colors, inconsistent type, mismatched interaction timing, uneven audio level, and different treatment of the same component. Preserve the user's chosen format and publishing destination.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

