digitalsamba/claude-code-video-toolkit / .claude/skills/video-design
video-design
VerifiedVisual design for videos - colour by act, type scale, chart and layout rules for 16:9 and 9:16 scenes, a design.md handoff that any design skill can fill, and a contact-sheet critique of the render. Use when designing or refining how a video looks (title cards, data scenes, slides, a whole video's palette), when a scene looks generic or busy, when choosing colours for a video, or when /design or /scene-review asks for visual work. Works on its own with a brand, or takes direction from a design source such as taste-skill, Anthropic's frontend-design, or the user's own design skill.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 9.4 KB |
| critique.md | markdown | 4.4 KB |
| handoff.md | markdown | 3.8 KB |
| idents.md | markdown | 5.4 KB |
| palettes.md | markdown | 3.4 KB |
| sources.md | markdown | 6.7 KB |
handoff.md
View on GitHub# design.md: the handoff
`design.md` sits in the project root. Whatever gave the direction (a design skill, a brand guide, the
user in conversation) is written down here in one shape, so the build, the critique and the next
session all read the same decisions. Changing source means rewriting this file, not the code.
Keep it short: a page. The values in it are what the scenes use; a scene that needs a colour or a size
that isn't here is a sign the file is missing a decision.
## Format
```markdown
# Design: <project>
Source: <design source and what it dealt, e.g. "taste-skill, direction colour-chapters, palette
orange-sky-lime (seed 1125998202), palette redrawn for brand"; or "ours: brand + bone + black">
Brand: <brands/<name>>
## Acts
| Act | Scenes | Says | Field |
| --- | --- | --- | --- |
| 1 Who | intro | <one line> | identity |
| 2 The work | cards, outcomes, notes, escalations | <one line> | record |
| 3 Getting better | better, models, cost | <one line> | lab |
| 4 Close | close | <one line> | identity |
## Fields
| Field | Ground | Ink | Data accent | Other data | Secondary ink |
| --- | --- | --- | --- | --- | --- |
| identity | #ea580c | #111111 | ink | — | ink 80% |
| record | #f4f1ea | #111111 | #ea580c | #d9d4c7 | ink 75% |
| lab | #161615 | #f4f1ea | #ea580c | #3b3a37 | ink 75% |
## Type
Family: <Inter>, weights <800 / 400>
Steps (1080p): display <220> · figure <112> · title <72> · label <36> · note <28>
Display tracking <-0.04em>, leading <0.95>
## Ground
<flat> or <the subject's shape, e.g. "week grid: 7 columns and hour rows, ink 16%, type scenes only; meetings
land as outlined event cards in the hook and empty on the question">
## Layout
Title edge: x = <120>
<anything else decided once: margins, where sources go>
## Rules turned off
- <rule> — <why, in one line> (or "none")
```
## How a source maps onto it
A design skill made for pages deals things a video doesn't have (a hero, a nav, buttons) and things it
does (a palette, a type system, an idea). Take the second kind and map it:
| A page skill deals | design.md gets |
| --- | --- |
| ground, ink, accent | the main field's ground and ink; the accent becomes the **data accent** |
| section fields / chapter colours | one field **per act** (not per scene); keep two or three, ordered by lightness |
| type system (face, weights, sizes) | family and weights as dealt; sizes mapped onto the five video steps |
| the idea ("X becomes Y") | the acts' "Says" column and the intro's composition |
| hero, sections, nav, buttons, scroll scenes | nothing: video has scenes, `motion-craft.md` handles motion |
| imagery rules | keep: real pictures and the product's own UI beat drawings and stock |
When the source's palette fights the brand or the subject, keep its **proportions** (one ground, one
ink, one accent) and take the colours from the brand, and say so under Source.
## Worked example: Lugh's work (2026-11)
The first version used one colour per scene (orange, sky, lime, black, in turn). The critique found the
colours meant nothing (sky held both "the work" and "testing models"), orange and sky flickered at the
cut, and 45% ink over each ground made olive and steel-blue bars. Rewritten by act:
- Acts: who Lugh is (intro) · the work (cards, outcomes, notes, escalations) · how it got better (the
model switch, testing models, cost) · close. The notes and escalations scenes moved ahead of "how it
got better" so the second act stays together.
- Fields: identity = Digital Samba orange, record = bone, lab = near-black: mid, light, dark, so every
act change is a clear cut, and there are three in two minutes.
- Data accent: orange on bone and black; ink on orange. Other bars one neutral step per field.
- Type: five steps; the close broken by hand onto two lines; the intro's four tiles became one track.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| canvas-designanthropics/skillsCreate beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| docxanthropics/skillsUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| pdfanthropics/skillsUse this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| pptxanthropics/skillsUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |