style-library — Claude Code skill for video styles
The style-library Claude Code skill selects, adapts, or defines a visual style for a motionforge video before scene work begins. It activates for a named look, topic, or reference.
MIT ★ 128 updated 2026-11-03
/plugin marketplace add aykutucesai/motionforge
/plugin install motionforge@motionforgeWhat style-library does
The skill helps choose from a catalogue of 100 styles across 20 categories, adjust one for a project, or write a new style. Each style has a STYLE.md covering palette, type, texture, framing, motion, sound, and checks.
For a project, copy the style file and record changes under ## Overrides; leave the library version untouched. A new style starts from styles/_template/STYLE.md and gets checked with a test scene. 3D styles need the project to render engines/hyperframes/three. Fonts must have a free licence and cover the video's language.
The skill sets rules for colour, text placement, and motion. Purple gradient backgrounds are ruled out, and motion randomness must be deterministic.
What it helps with
- choose a video look from its topic or reference
- adapt a style's palette and fonts to a brand
- define a new visual style for motionforge
- check a test scene against the selected style
Example prompts for the agent
- Choose a motionforge style for a product video.
- Adapt
creator-reels-darkto our brand palette. - Create a new video style from this reference.
How to install style-library
1Plugin marketplace
/plugin marketplace add aykutucesai/motionforge/plugin install motionforge@motionforgeThis installs the whole motionforge plugin with all its skills
2Skills CLI (Vercel)
npx skills add aykutucesai/motionforge --skill style-library -a claude-code3Manually: put the files in place
~/.claude/skills/style-library/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/style-library/
1Skills CLI (Vercel)
npx skills add aykutucesai/motionforge --skill style-library -a codex2Manually: put the files in place
.agents/skills/style-library/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add aykutucesai/motionforge --skill style-library -a cursor2Manually: put the files in place
.cursor/skills/style-library/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install aykutucesai/motionforge skills/style-library2Manually: put the files in place
.github/skills/style-library/SKILL.md1Skills CLI (Vercel)
npx skills add aykutucesai/motionforge --skill style-library -a gemini-cli2Platform CLI
gemini skills install https://github.com/aykutucesai/motionforge --path skills/style-libraryManually: put the files in place
.devin/skills/style-library/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about style-library
How do I install style-library in Claude Code?
Add the marketplace with /plugin marketplace add aykutucesai/motionforge, then install the plugin with /plugin install motionforge@motionforge.
What does style-library do?
It helps select a motionforge video style, tailor it to a project, or create one. Each style is described in a STYLE.md file.
Which engine do 3D styles require?
The project must render engines/hyperframes/three. The catalogue lists the engine for each style.
Source text
SKILL.md · MIT
--- name: style-library description: Pick, customise or create the visual style of a motionforge video from a library of 100 styles in 20 categories (creators, e-commerce, real estate, sports, documentary, education, tech, finance, food, fitness, travel, events, news, business, gaming, kids, fashion, automotive, art direction, nonprofit). Use when a video needs a look (palette, type, texture, framing, motion, edit rhythm, sound) before scenes are built, when the user names a style, a vertical or a reference, or wants their own reusable style. Every style is one STYLE.md in the same 9-section format. license: MIT --- # Style library A style is a written contract for how a video looks, moves and sounds. Scenes are built *from* the style, and reviews are judged *against* it. Each style lives in `styles/<slug>/STYLE.md` and uses the same nine sections (see [`styles/_template/STYLE.md`](styles/_template/STYLE.md)): 1. **Essence** — the look in one sentence and three adjectives 2. **Use it for / avoid it for** 3. **Palette** — named tokens with hex values and their jobs 4. **Type** — families (free licences only), sizes, case, tracking 5. **Surfaces and texture** — backgrounds, materials, grain, lines 6. **Framing and layout** — where things sit in 9:16 (and how it adapts to 1:1 / 16:9) 7. **Motion** — entrances, exits, easing, timing numbers, transitions, camera, edit grammar (shot length, cut types, where cuts land) 8. **Sound** — music bed, effects, how they sit under the voice 9. **Build recipe and checks** — engine, templates, signature scenes, steps, style-specific QA The catalogue — 100 styles grouped into 20 categories, one line each, with best use and engine — is [`styles/README.md`](styles/README.md). The header table of every style names its category. ## Step 1 — Pick 1. Read the brief: topic, platform, audience, length, whether a person appears on camera, whether a brand kit exists (`brand.json` from the brand-kit skill). 2. Open [`styles/README.md`](styles/README.md) and shortlist 2–3 styles whose *Best for* matches the content type. Start from the category that matches the account or the client, then check *Best for*: * creator / personal account → *Creators & personal brands* (`creator-reels-dark`, `talking-head-pop`, `podcast-clip-studio`, `vlog-film-diary`, `kinetic-captions`, …) * shop, product, ad → *E-commerce & products* (`product-hero-turntable`, `flash-sale`, `ugc-testimonial`, `before-after-split`, …) * listings, neighbourhoods, maps → *Real estate & maps* (`map-flyover-pins`, `floorplan-draw-on`, `neighborhood-guide`, …) * football and other sports → *Football & sports* (`matchday-graphics`, `tactics-board`, `player-stat-card`, …) * documentary, history, investigations → *Documentary & storytelling* (`archival-newsreel`, `true-crime-board`, `history-map-campaign`, …) * how it works, lessons, quizzes → *Education & explainers*; software, repos, AI → *Tech, SaaS & AI*; numbers → *Finance & money* or `data-story` * no category fits → *Art direction & design looks* (`swiss-poster`, `riso-print`, `neon-noir`, `collage-zine`, …) carry any topic Prefer styles whose engine the project can render (3D styles need `engines/hyperframes/three`). 3. Present the shortlist to the user in their language: name, one-line look, why it fits. If the user gave a reference image or video, describe what you see in it in terms of the nine sections and pick the closest style (or create one, step 3). Do not copy a specific film, show, artist or brand; take the craft (palette logic, timing, texture), never protected characters or logos. 4. Record the choice in the project brief: `style: <slug>` plus any overrides. ## Step 2 — Customise (most projects) Never edit the library copy for one project. Override in the project instead: 1. Copy `styles/<slug>/STYLE.md` to `<project>/style/STYLE.md`. 2. Map brand tokens onto the palette roles (brand primary → accent, brand dark → background, …). Keep the *structure* of the palette: one accent stays one accent. 3. Swap fonts only for families with a free licence (SIL OFL, Apache-2.0). Check that the font covers the video's language (Turkish İ ş ğ, Polish ł, Vietnamese, CJK, Devanagari …): load both `latin` and `latin-ext` files (see `engines/hyperframes/base.css`). 4. Write every override at the top of the copy under `## Overrides` (what changed and why). 5. For HyperFrames, put the palette into CSS custom properties (`--mf-bg`, `--mf-accent`, …) in a `brand.css` loaded after `base.css`; for Remotion, into the `BrandTheme`. ## Step 3 — Create a new style 1. Copy `styles/_template/STYLE.md` to `styles/<new-slug>/STYLE.md` (or into the project). 2. Fill all nine sections with concrete numbers: hex values, px sizes at 1080×1920, seconds, easing names. "Smooth" or "modern" is not a spec; "0.35 s, back.out(1.6), 40 px rise" is. 3. Make one test scene (`engines/hyperframes/scripts/new-scene.sh style-test`) with a title, a card and a caption in the new style; render 3 stills and check them against section 9. 4. If the style was inspired by someone else's work, name the inspiration in a `## Credits` line and make sure nothing protected was copied (characters, logos, artwork, exact layouts). 5. Add a row to `styles/README.md`. ## House rules (apply to every style unless the user overrides them) * No purple gradient backgrounds and no drawn grid / graph-paper backgrounds. Use a flat or softly lit field with grain, a blurred real photo, or a real scene. * One accent colour per frame does the pointing; everything else supports it. * Real logos and real screenshots when a real product is named (from the brand kit or the user); never invented UI for a real product. * Static grain only; deterministic motion only (seeded randomness). * Text stays inside the safe band (y 240–1680 at 1080×1920) and clear of the right-hand button rail. ## Checks before handing over a style choice - [ ] The palette has a background, a text colour, one accent and at most two supports. - [ ] Every font is free to use commercially and covers the video's language. - [ ] Section 7 has timing numbers; section 9 names an engine and at least one template. - [ ] A still from the test scene reads at 360 px wide (phone size).
© motionforge contributors · MIT · aykutucesai/motionforge