Communitygithub.com

cinematic-storytelling

Builds the story arc, beat sheet, emotion, carry between beats, and payoff for a video. Complements beyond-video; does not replace it.

What is cinematic-storytelling?

cinematic-storytelling is a Claude Code agent skill that builds the story arc, beat sheet, emotion, carry between beats, and payoff for a video. Complements beyond-video; does not replace it.

Works with~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/achmdfzn/motionforge-atelier/tree/HEAD/.claude/skills/cinematic-storytelling

Ask in your favorite AI

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

Documentation

CINEMATIC STORYTELLING

Mission

Design a story experience that is clear, emotional, and has a payoff. This skill complements beyond-video; it does not replace it.

Workflow

  1. Extract the communication goal, audience, platform, duration, main message, and CTA.
  2. Write a one-sentence premise, the audience promise, and an honest curiosity gap.
  3. Choose a structure: problem–tension–reveal–resolution, journey, contrast, countdown, mystery–reveal, or explainer arc.
  4. Build a beat sheet with each beat's function, new information, emotion, visuals, and duration.
  5. Remove decorative beats that do not change understanding, emotion, or situation.
  6. Make sure the payoff fulfills the hook's promise; no clickbait.
  7. Connect the resolution to a specific closing logo + CTA.

One transformation, one payoff, one returning token

Before writing a beat sheet, state the story in three sentences: the setup (how things are), the transformation (what changes), and the payoff (what it means). If those three sentences cannot be written, the video is not ready for a storyboard.

Pick one token — an object, shape, color, or gesture — that appears early and returns at the end changed. The returning token is what makes the ending feel earned, and it is usually the best bridge into the bespoke closing logo + CTA.

When a video uses more than one visual medium or style, the medium changes only when the story changes state (before → after, problem → solution, past → present). A sequence of style samples with no story reason is a showreel, not a film.

Carry: every beat grows out of the one before

Short vertical videos most often fail because they feel like a slideshow: beats take turns on screen, each one replacing the last. Two different things cause it, and both must be checked separately:

  1. Flat rhythm — every beat has a similar duration and energy. Fix: vary the tempo. Place deliberate still moments, tight bursts of motion, then holds. A pause is part of the rhythm, not emptiness.
  2. No carry — the rhythm already varies, but every beat still starts from zero. Fix: connect beats through something carried into the next one:
    • Object: an element from beat A becomes part of beat B (a headline that lands becomes a button, a card that grows becomes a page).
    • Cause and effect: an action at the end of beat A triggers the start of beat B.
    • Camera: the camera follows what matters most, then moves to the next subject without cutting.
    • Scale: a continuous zoom links the detail and the big picture.

Hard cuts are still allowed, but only when they mean something: a before/after contrast, a change of point of view, or a surprise. Not as the default way to change topic.

Build meaning into the visual, rather than attaching it as a label. If viewers need a caption or an arrow to understand a shot's idea, the idea has not made it into the picture yet.

Idea reference: the general "carry" principle and the slideshow diagnosis were inspired by feitangyuan/onetake. That repo is licensed PolyForm Noncommercial; none of its text, structure, code, or distinctive terms are used here, only general ideas rewritten in our own words.

Output format

  • One-sentence premise + audience promise (what the viewer gets) + an honest curiosity gap.
  • Beat sheet (table): beat | function | new information | emotion | visual | duration (frames, half-open).
  • Pacing map: emotional intensity per beat (low/medium/high) and where pauses/silence go.
  • Emotional arc: starting emotion → turning point → ending emotion, one sentence each.
  • Payoff: the answer to the hook's promise, with its frame.
  • CTA rationale: one action, and why it is the natural continuation of the payoff.
  • Verification list: factual claims + their sources, or a "not yet verified" label.

QA checklist

  • One main message; beats that do not change understanding, emotion, or situation are removed.
  • The payoff fulfills the hook's promise specifically — not a new promise.
  • No exposition dump; information is spread across beats, not one block of narration.
  • Honest curiosity gap; no clickbait or unanswered questions.
  • Total beat duration = composition durationInFrames; no dangling beats.
  • The resolution connects to that video's specific closing logo + CTA.
  • Every transition between beats has a carry (object, cause and effect, camera, or scale), or a hard cut with a written reason.
  • Beat durations and energy vary; there is at least one deliberate still moment.
  • Each shot's idea reads without an explanatory caption.
  • The story fits in three sentences (setup, transformation, payoff) and has one returning token.
  • Any change of medium/style coincides with a change in the story's state.

Mini example

Problem–tension–reveal–resolution structure, 12 seconds / 720 frames: problem (0–120, frustration with generic prompts), tension (120–300, the folder opens), reveal (300–480, 17 skills flow out), resolution (480–720, directed result + closing folder → wordmark). Emotion: frustration → curiosity → relief.

Failure modes

  • Weak payoff → strengthen the hook's promise or cut middle beats that do not lead to the payoff.
  • Too many messages → pick one main message; others become visual subtext, not narration.
  • Flat arc → add a turning point (before/after contrast) in the middle of the video.
  • "Feels like a slideshow" even though the rhythm varies → the problem is carry, not rhythm; find what each beat can hand to the next.
  • Hard cut at every beat change → replace some of them with carry; keep cuts for moments that really are contrasts.
  • Viewers miss the idea even though the visuals look good → the idea is not in the picture yet; adding labels usually makes it worse, redesign the visual.

Carry example for the 720-frame teaser in examples/teaser-skill-pack/: the "generic ❌" card (S01-B02) is sucked into the opening folder (S02-B01); the skill chips flowing out of the folder (S02-B02) arrange themselves into pipeline nodes (S03-B01); those nodes shrink back into the folder, which becomes the wordmark (S04-B01). No beat starts from an empty screen.

Standard

One video has one main message. Avoid exposition dumps. Never invent facts/quotes/testimonials; flag claims that need verification. For 1080×1920, prioritize the phone screen and safe area. Compute timing at 60 FPS and make sure the total frames match the composition.

Individual skills in this repo

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

Related Skills