Communitygithub.com

film-storyboard

Write the story of a product film as beats (what the viewer sees, the words on screen, the voice, the sound, why the beat exists, and where each claim is proven) and send it to the owner as a one-page storyboard with frames for review, with 2–4 directions when the story is open. Stage 2 of product-film, and the review format reused for the voiceover. Use when planning a launch/promo film's story, shot list, or script, or when the owner says "give me a storyboard", "give me directions", "I'll review and decide".

What is film-storyboard?

film-storyboard is a Claude Code agent skill that write the story of a product film as beats (what the viewer sees, the words on screen, the voice, the sound, why the beat exists, and where each claim is proven) and send it to the owner as a one-page storyboard with frames for review, with 2–4 directions when the story is open. Stage 2 of product-film, and the review format reused for the voiceover. Use when planning a launch/promo film's story, shot list, or script, or when the owner says "give me a storyboard", "give me directions", "I'll review and decide".

Works with✓Claude Code~Codex CLI~Cursor
npx skills add https://github.com/aqeelshamz/product-film-skills/tree/HEAD/film-storyboard

Ask in your favorite AI

Open a new chat with this agent skill pre-loaded.

Documentation

Film storyboard

The storyboard is where most of the owner's corrections should happen, because changing a sentence costs a minute and changing a rendered shot costs an hour. Send it before you build, and send it again (with real frames) before you record a voice.

What makes a good product-film story

Check each beat against these. Every one came from a rejected draft (see product-film/references/lessons.md).

  1. The viewer's pain, in their day. Name the habit or annoyance the way the viewer would say it. Test the line: after hearing it, what would a stranger think we sell? "Same numbers every day" made people think of analytics software, so it failed.
  2. Roles can't be misread. Show real tools by name and logo. Check every pair of adjacent lines: "Ask the AI you already pay for. It's called Nimbet." makes the product sound like the AI. Attach the name to what the product does.
  3. Specific, not abstract. "Your AI" as a label was unclear; Claude Desktop's real window was clear. A real Stripe dashboard beats a box labelled "Revenue".
  4. Range needs room. If the promise is "whatever YOU need", show 8+ kinds of people (full-screen card each), then a wall of many items mixing work, life and fun (games, pets, stickers). Fewer than ~6 "feels stuck". This needs 45–65 s; 20 s is too short.
  5. Real only. Every item, capability and claim works in the product today. Fill the claim field with where it's proven (a file, a doc, a test). If the story needs something the product can't do, raise it with the owner: build it or cut it.
  6. Understand each shot before you write about it. Write the why for every beat. If you can't say what a shot is for, ask the owner. (A pet line was written over a shot that actually showed people's own custom widgets.)
  7. Every line readable. On-screen text: ~0.3 s per word + 1 s, never under 1.5 s fully visible.
  8. End on the action, with the name and the URL, and the nominative-use line if any brand appeared.

Steps

  1. Read the approved brief, reference/NOTES.md, the live product and site, and the lessons file.
  2. Draft beats in storyboard.json (format in the script's header):
    { "title": "…", "subtitle": "draft 1 · 16:9 · 60 s", "directions": ["A · …", "B · …"],
      "beats": [{ "t": "0.0–4.0", "still": "review/sketches/01.png", "picture": "…", "onscreen": "…",
                  "vo": {"A · …": "…", "B · …": "…"}, "sfx": "…", "why": "…", "claim": "…" }] }
    
    Before the film exists, still can be a quick sketch or a frame from the reference with a note; after, always a REAL rendered frame (node scripts/render.mjs --at …).
  3. Directions. When the angle is open, write 2–4 directions that differ in idea, not wording (e.g. "Tips the viewer can use", "The daily annoyance", "What your AI already knows about you"). For each: one-line idea, the risk, and who it suits. Put your pick first.
  4. Build the page:
    python3 ~/.claude/skills/film-storyboard/scripts/storyboard.py storyboard.json review/storyboard.html
    
    It opens with each direction's voiceover as one paragraph (the eyes-closed read), then every beat with its frame.
  5. Self-check before sending: read only the transcript paragraph. Does it make sense with eyes closed? Any line that could be misread? Any "your X, your Y" list, triad, or repeated word? Any claim with no proof?
  6. Review gate. Send the page (SendUserFile, display render) and ask: which direction, and which beats to change. Add the stage-2 questions from product-film/references/question-bank.md (opening, how roles are shown, persona format, characters, UI realism). Wait for a clear yes. Commit storyboard.json.

After approval

Keep storyboard.json as the source of truth: shot timing in the film and phrase placement in the voiceover both come from it. When the owner changes a beat later, change it here first and regenerate the page.

Individual skills in this repo

This repo contains 4 individual skills — each has its own dedicated page.

film-build

Build a product film in code as a deterministic seek(t) web page (real product UI, real OS chrome, kinetic text, typed prompts, a cursor, morphs and camera moves), review it as stills and drafts, render it at 60 fps with motion blur, and adapt it to 9:16 without changing 16:9. Ships a project kit (init.sh, film engine, render/sync/probe/sheet/regression tools). Stage 3 and 6 of product-film. Use when building, fixing or rendering the picture of a launch/promo film, or making its vertical version.

film-sound

Add sound to a finished product-film picture with real recorded sound effects (CC0 packs such as Kenney's) placed only on real on-screen events, decide with the owner whether there's a music bed, mix to -14 LUFS and mux into the renders without re-rendering. Stage 4 of product-film. Use when a film's picture is approved and needs sound effects or music, or when the owner says the sounds feel fake, synthetic or "AI slop".

film-voiceover

Write, review, test and record the voiceover for a product film after its picture is approved, as a script on a storyboard of the film's real frames, with directions to choose from, an eyes-closed coherence check, a pronunciation test for the product name, TTS recording per section (Fish Audio), phrase placement on the film's timeline, mixing and muxing. Stage 5 of product-film. Use when a launch/promo film needs narration, or the owner says the voiceover sounds like AI, doesn't match the frames, or mispronounces the name.

product-film

Make a product launch / promo / explainer film that sells and does not look or sound AI-made, through review gates the owner signs off one at a time. Study a reference video for its grammar (never copy it), then storyboard, build the film in code, add sound, write and record the voiceover, and deliver 16:9 and 9:16. Use when someone wants a launch video, promo, product film, explainer, ad, "a video like this one" for their product, or says the last video looked like "AI slop" or "vibe coded". Entry point for the film-* skills (film-reference-study, film-storyboard, film-build, film-sound, film-voiceover).

Related Skills