Itsmahnor/digikon-ai-video-director / skills/creative-direction
creative-direction
Verifiedcreative-direction
A film that is only correct looks generic. Decide what it is about visually, then hold every scene to that decision.
Inputs
Brief, audience, platform, approved facts, the supplied assets, and (at the storyboard) the treatment with its art direction.
Procedure (treatment)
- Viewer response. Say what the viewer should think, feel or do by the end, in the audience's words (
audience_response). "Learn about the product" is not a response; "feel relief and start the trial" is. - One concept. One idea the whole film is built on (
concept). Add avisual_metaphoronly when it clarifies the message (a tangle that untangles). Otherwise set it to null. Never add novelty for its own sake. - Art direction. Choose a palette that suits the audience and the product, not a default dark navy: six colours, with legible text on the background and on panels. Choose type weight, scale and case, one composition rule (where the headline sits, how much space), and a motion language (feel, easing, one sentence). One typeface file exists, so weight, scale and case are what can vary.
- Arc. Write what the opening, the development and the conclusion each do. The opening must show something concrete from the first frame. The conclusion holds still on one action.
- Beats follow the arc. Each beat has a different job.
Procedure (storyboard)
- Give every scene a
visual_purpose: what its picture does that no other scene's does. No two scenes may share one. - Give every scene a
visual: a structured spec of one block from references/visual-blocks.md. Pick the block by what the scene must communicate, not by habit. A neighbouring scene must use a different block, and no block may carry more than a third of a film. - Use
kinetic_typefor a sentence that is the idea. Use a plainend_cardonly to close. Do not make a text-only scene the default; use one only when words alone are the best choice, and say why invisual_purpose. - Choose the scene's camera move, reveal and backdrop to serve its purpose, and the shot's
camera_motionto match the visual's camera. Vary them across the film; keep them inside the art direction's motion language. - Scene text belongs in
overlay. Sample content in a visual (messages, rows, labels) is illustrative and must not state results, prices or numbers. - Keep colour, type and motion consistent across scenes (the design system), while the pictures differ.
- Layout limits. The renderer fits the picture to the real frame: it measures text with the font, wraps long labels onto more lines, picks a column, row or grid for steps, widens or moves a sidebar, and shows steps in pages inside the approved duration when one page cannot hold them. It never cuts a word and never draws text below the legible floor (about 3.4% of the short side of the frame). So write the wording you want, keep each label as short as it can be (under about 28 characters), and do not stack more steps or rows than the picture can carry. If a render is refused for layout, the reason names the area in pixels, the sizes tried and what did not fit: shorten that wording, split the scene, or choose another block. Do not ask for smaller text.
- A transition is chosen to do a job. A match_cut is only honest when the last picture of one scene and the first picture of the next share a shape, a position and a background; the assembler measures that, and a join that does not match is reported as missing rather than passed off as a match cut. Use the match-cut recipe for it, never the hard-cut recipe.
Never
- Open on a logo or a title card, or end without one clear action.
- Use the same block in two neighbouring scenes, or give two scenes the same visual purpose.
- Show a product screen as real, a chart as measured data, or a typeset name as a logo. The renderer labels them as concept illustrations; do not claim otherwise.
- Put a % or currency sign in drawn text unless an approved claim supports it.
- Ask for a block or motion that the reference does not list.
Failure conditions
A scene that needs live footage, a real product capture or a real logo that was not supplied: say so in unresolved; do not draw it as real.
Evals
See evals/cases.md.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |