BintzGavin/helios / skills/design/cinematic-product-promo-plan
cinematic-product-promo-plan
VerifiedEnd-to-end production plan template for feeling-first cinematic product promos: brief interrogation, 45s beat structure (cold open through brand), hero-element metaphor, storyboard fidelity ladder, visual system (palette, type, camera, texture), motion mix and easing vocabulary, audio and captions, tooling (animatic through HTML or AE), deliverables matrix, accessibility, review milestones, and compromises to accept or refuse. Use when planning, pitching, storyboarding, or producing polished brand films for any SaaS or consumer product—not category-specific; pair with skills/design/animated-video-philosophy for broader motion principles.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.2 KB |
| production-plan.md | markdown | 15.3 KB |
production-plan.md
View on GitHubA Cinematic Product Promo: Production Plan
A complete production plan, from blank page to shipped file. The structure below assumes a **feeling-first** piece: you are selling an emotional promise more than a feature list. Swap nouns, metaphors, and contexts to fit the product; keep the phases, beats, and technical discipline.
Phase 0 — Interrogating the Brief
Before any phase that produces artifacts, I sit with the brief. The headline is almost always beautiful and treacherous — every category claims the same virtues ("seamless," "effortless," "intelligent," "for everyone"). So my first job is to translate the abstraction into something I can actually animate.
I'd want to know:
What does the central claim mean **for this product**, specifically? (Examples: real-time sync vs. one-time setup vs. zero learning curve vs. guaranteed delivery — the metaphor changes entirely depending on the answer.)
Who is the protagonist? A specific person with a specific need (role, moment, stake) is animatable. Broad personas ("modern professionals," "teams everywhere") are not.
What is the **opposite** of the promise that we are quietly contrasting against? The promise only lands next to its shadow. The piece needs a faint sense of the old way, the slow way, or the anxious way — without naming competitors.
Where does this play? A 60s YouTube pre-roll permits a slow build. A 15s Instagram Reel demands the payoff in the first two seconds.
Brand assets? Logo, type, palette, motion guidelines. If they don't exist, we're inventing them — and that's a separate conversation.
I'd ship one paragraph back to the stakeholder before moving on: "Here's what I think we're making. Confirm or correct before I spend a day on it."
Phase 1 — Conceptualization & Storyboarding
The story, in one sentence
State the spine in plain language: what moves, what transforms, or what crosses a gap — and arrives intact — for the person who needs it.
That's the spine. Everything serves it. *(Concrete example — only an example: "A thought leaves one person and arrives, intact and instant, in another — across distance, devices, and the small frictions of life.")*
The arc
I'd structure 45 seconds (a useful default — long enough to breathe, short enough to land in many placements) like this:
Beat Time Function
Cold open 0–4s A single moment of human intent. Something matters; the protagonist leans toward action.
Spark 4–8s The intent becomes the product moment. Establish the protagonist of the **visual language** (your hero element, UI, or symbol).
Journey 8–28s The promise **travels** or **unfolds**. This is the body: distance, environments, states, or scale changes.
Arrival 28–36s It lands. A second context, a second person, or a resolution. The payoff feels easy.
The web 36–42s Pull back. One relationship becomes many — the system at scale.
Brand 42–45s Logo. Tagline. Hold. End.
Key scenes & visual metaphors
Pick **one** central thread the viewer can follow — a glow, a token, a ribbon of data, a single UI surface, a physical metaphor. It can be a cliché on paper; clichés work when execution is precise. The craft is in **how** it moves, not in avoiding familiar grammar.
Specific scenes (rename to match your product):
The intent. Human beat before chrome. Face, hands, workspace, ritual — whatever sells the stakes in two seconds. No product chrome until the viewer cares.
The activation. Push into the product. The interface (or hero object) **assembles around the intent** — the story is that the product follows the person, not the reverse. Gestures over busy UI if the brief is about ease.
The journey. Where you spend the most time. The hero element crosses stylized space, states, or abstractions (cities, topology, weather, time of day, org charts as landscape — whatever maps to the promise). The world is **stylized**, not stock-footage literal. The thread never goes dead; hue and atmosphere can drift to signal passage.
The arrival. The hero element lands in a **new** context. Show relief, delight, or closure with **absence of friction** — skip the labored steps you'd normally see if the point is effortlessness.
The system view. Pull back to multiplicity: many nodes, many threads, a lattice or field. This is "the product at scale." Hold ~2s.
The mark. Logo resolves from the system view — a final motion into the wordmark. Tagline beneath. Hold ~2.5s. End on still.
What I'd deliberately not include
No feature callouts as on-screen slogans. The moment a label sells a spec, the spell often breaks. Save facts for captions, post copy, and the landing page.
No competitor reference, even implied. Contrast should be **felt** in pacing and relief, not named.
No human dialogue between characters unless the brief truly requires it. Voiceover: sparingly.
No emoji. No emoji-as-visual-language. Ever.
Storyboard fidelity
I'd produce the storyboard at three escalating fidelities:
Thumbnail sketches (paper, 90 minutes): six panels per beat, just to feel the rhythm.
Animatic (After Effects or, in this environment, an HTML page with timed black-and-white blocks): the full 45 seconds with placeholder shapes and stopwatch timing. This is where pacing gets locked. It is faster to fix pacing in the animatic than at any later stage.
Style frame (one or two only): fully designed stills of the most important moments — usually the journey midpoint and the system pullback. These resolve the visual language for the rest of the team.
Phase 2 — Visual Style & Aesthetic Guidelines
Guiding principles
Before any swatch or font, three rules:
Restraint signals quality. Three colors, two typefaces, one accent gesture repeated. Less surface area = more polish per square inch.
The frame must be alive without being busy. Quiet motion in every shot — drifting gradients, breathing scale — but never more than one loud thing at a time.
Every visual choice is in service of **the brief's core feeling**. If an element introduces friction (a hard edge where a soft one would do, literal UI where a gestural read would suffice, a color collision), it loses.
Color
A palette that can **breathe** across the journey:
Foundation: an off-white near-paper (oklch(98% 0.005 80)) and a deep ink that isn't pure black (oklch(18% 0.01 260)). Warm whites, cool blacks — a tension that keeps the frame from feeling sterile.
Accent: a single signature hue tied to the hero element and the connective thread (example: soft luminous cyan-green oklch(78% 0.12 180) if the story is about light and signal — change the hue if your metaphor is warmth, urgency, nature, etc.). It should feel like **light or energy**, not default corporate teal, unless that's truly the brand.
Atmospheric tints: let background hue drift across the journey — e.g. dusk-warm at origin, dawn-cool at arrival. Same lightness band, hue can rotate ~60° over ~20s. Felt, not explained.
No gradients as decoration. Gradients exist only as atmosphere — sky, depth, fog — never as cheap button fills or text treatments unless the brand demands it.
Typography
Two faces:
A humanist sans for primary type. Inter is overused; consider Söhne, Untitled Sans, or General Sans. Geometric enough to feel modern, humanist enough to feel warm — unless the brand is intentionally cold/industrial.
A monospace for accents only — timestamps, punctuation in the tagline, tiny engineering flairs. Sparingly.
Type appears in **three contexts** max: copy that belongs to the protagonist's moment, the closing tagline, and at most one mid-piece phrase. No third-act stat slabs. No bullet points. No.
Camera language
Yes, 2D work still has a camera: frame, scale, crop, and parallax.
Establishing shots are wide and patient. Think 35mm, shallow-feel even though there's no real lens.
Action shots push in. Following the hero element often uses a slight damping lag — the frame can't quite keep up, which sells speed and weight.
The arrival uses a hard cut, not a mushy transition. Travel vs. stillness is the punctuation.
The system pullback is a continuous zoom out, slow and inevitable, scored to a swelling note — the climax of the visual language.
Texture and depth
Subtle film grain across the entire piece. A 4–6% noise overlay that you'd never notice but would miss instantly if removed. It's what separates "rendered" from "filmic."
Soft, large-radius shadows on every floating element. No drop-shadows under 20px blur. We are not making a UI mockup; we are making cinema.
Depth-of-field implied via blur. When the camera is on the hero element, the world behind softens. Cheap, high impact.
What I'd refuse
Glassmorphism when it's trend-sludge.
Gradient mesh blobs with no narrative job.
3D devices floating in a void as the **subject** — the device is a vessel for the moment, not a substitute for one.
Particle systems with no narrative purpose. Particles serve the story, or they're noise.
Generic "tech" iconography (chains, networks, globe wireframes) **unless** that grammar is truly your chosen metaphor. Prefer a single readable thread over infographic soup.
Phase 3 — Animation & Motion Design Approach
Philosophy
The video is not a spec demo. It is a short film that happens to contain a product. Product moments exist — they should be subordinate to the larger choreography of the hero element (or the idea) moving through the piece.
The mix (tune the labels, keep the ratio idea):
~25% kinetic product UI or interface moments — only where contact with the real product earns trust.
~50% motion graphics — journey, environments, pullback.
~15% kinetic typography — tagline and at most one mid-piece phrase if the narrative needs it. Not before.
~10% held beats — silence and near-stillness that let the loud passages land.
The easing vocabulary
Commit to a small set of named curves and reuse them by **category** of motion:
outQuint for arrivals — anything coming to rest on screen. Gentle, confident deceleration.
outBack (~8% overshoot) for the hero element docking, logo settling — anything delivered with weight.
inOutSine for camera moves. Breath-like, not flashy.
spring (e.g. damping 18, stiffness 220) for the hero element when it changes direction — organic, alive.
linear only for mechanical drift (atmospheric BG) or constant flight velocity for the hero element in motion. Almost nothing else.
Same easing class for same story beat every time — the viewer learns the language before they can name it.
Specific scene choices (map times to your animatic)
The intent (0–4s). Feels still; isn't. Drifting light, 0.5% scale breath on a hand or object, stray detail crossing frame. "Still" that lives.
The activation (~4–8s). Choreograph copy or controls so they feel **exhaled**, not typed: e.g. word-by-word fades with ~60ms stagger and tiny upward drift — not character-by-character typewriter unless that's the concept. Commit action is **gestural**: gather into one hero form, lift, leave.
The journey (~8–28s). Long span → **sub-shots** (~5s each) with matched cuts on hero position/speed so the eye never hunts.
The arrival (~28–36s). Hard cut from velocity to calm. Dock with outBack. Warm bloom on the payoff surface. Reply or mirror beat can be shorter and warmer than activation.
The system view (~36–42s). Pullback starts a hair early (inOutSine). New threads appear on a **slightly irregular** stagger (e.g. 80/100/90/130/100 ms — musical, not metronome, not chaos).
The mark (~42–45s). Final motion into logo geometry at a locked time (example: 43.0s). Tagline ~400ms later, word-by-word. ~1.6s hold: only grain moves. End.
Phase 4 — Audio & Music
Audio is at least half the experience. On social, most people start muted — design **both** the scored and muted-first experience.
Music
Custom score or a carefully licensed track (e.g. Musicbed, Marmoset, Artlist). Example brief:
Tempo: ~85 BPM — calm with pulse.
Instrumentation: sustained pad, small recurring motif (e.g. three-note felt piano), soft pulse (heartbeat, not full kit). No vocals. No EDM build-drop unless the brand is that brand.
Arc: sparse cold open; motif enters with the hero element; pad swells through journey; pullback is the peak; logo lands on a long tone into the hold.
Mix: always leave headroom for sound design.
Sound design
Sparingly. The piece shouldn't sound like a slot machine.
Soft lift-off when the hero element launches.
Journey air as **breath**, not wind-tunnel.
Arrival chime slightly lower than send — a subliminal call-and-response interval.
Tactile UI cues very quiet, low-passed so they read as material, not beeps.
Silence: e.g. one second before the system pullback, and across the final logo hold.
Voiceover
Default: push back. If required: one line, late, warm, doesn't repeat the frame. Cast like a person, not a category.
Captions
Non-negotiable for social. Open captions on vertical masters; SRT for web/YouTube; describe meaningful SFX in the accessibility lane. Humanist sans, bottom third, subtle scrim.
Phase 5 — Technical Workflow & Considerations
Tools, by stage
Conceptualization: paper, then a shared document.
Animatic: Figma timed frames or an HTML page with blocks + temp audio — HTML scrubs, which saves weeks.
Production: After Effects + Lottie/Rive for exact UI, **or** deterministic-time HTML/React (e.g. `<Stage>` / `<Sprite>` patterns) when iteration and engineering handoff matter more. Both are valid.
Audio: DAW + stems for mix control.
Final render: ProRes master from deterministic capture (e.g. 60fps HTML pipeline) or AE; ladder down per platform.
Captions: hand-authored SRT; burn for open-caption variants.
Deliverables matrix
A single piece becomes many files:
Cut Aspect Length Use
Master 16:9 45s Website, YouTube
Vertical 9:16 45s Reels, TikTok, Shorts
Square 1:1 45s LinkedIn, fallback Instagram feed
Cutdown 16:9 15s Pre-roll, paid social
Cutdown 9:16 15s Story ads
Open-caption 9:16 45s Muted autoplay
Loopable 1:1 6s Banner, hero loop
Vertical and square are **re-framed compositions**, not center crops — non-negotiable for quality.
Compromises I'd accept
60fps master / 30fps social if file size demands it.
8-bit delivery; archive 10-bit if needed.
Amplify subtle motion on small screens (e.g. 0.5% → 1.5% breath on vertical) — same idea, readable amplitude.
Let data pick primary length (e.g. 15s vs 45s per channel) without gutting story past the point of recognition.
Compromises I'd refuse
Bitrate that banding-kills the hero element or the "light" read.
Removing held beats to shave time — you get a different film.
Late feature slugs in picture — keep facts in copy and captions.
Accessibility, beyond captions
`prefers-reduced-motion` hero variant when this lives on web.
Flash / WCAG contrast checks on the hero element and captions.
Alt text for posters and social cards.
Phase 6 — Review, Iterate, Ship
Three review milestones, no more:
Animatic review — pacing and story only.
Style frame review — look lock at ~95% for key shots.
First full render — creator watches 30+ times first; stakeholder pass is **whole-piece** reaction before shot-level notes.
Ship around the pass where more polish adds noise, not value.
Closing thought
A promo about an **effortless** promise should feel effortless to watch — which is the product of invisible discipline. The outcome: someone scrolling on a phone slows down, feels a small true thing, and remembers your name when the need actually hits.
That's the whole job. First scene to build: usually the **journey midpoint** — if the long middle works, everything else is calibration.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |