Communitygithub.com

prepro-deck-builder

Build a complete pre-production deck (.pptx, opens in any presentation app) from one or more scripts. The house format is built into the builder, so no template or reference deck is needed. Use whenever someone shares a script (text, PDF or spreadsheet) and asks for a pre-pro deck, pre-production deck, production book, storyboard deck or shooting deck, even if they only say "build the prepro" or "run it through." One full section per script. Never returns a partial deck.

What is prepro-deck-builder?

prepro-deck-builder is a Claude Code agent skill that build a complete pre-production deck (.pptx, opens in any presentation app) from one or more scripts. The house format is built into the builder, so no template or reference deck is needed. Use whenever someone shares a script (text, PDF or spreadsheet) and asks for a pre-pro deck, pre-production deck, production book, storyboard deck or shooting deck, even if they only say "build the prepro" or "run it through." One full section per script. Never returns a partial deck.

Works with~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/thinkalim/ai-video-preproduction-skills/tree/HEAD/skills/prepro-deck-builder

Ask in your favorite AI

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

Documentation

Pre-Production Deck Builder

Script in. Finished pre-pro deck out. The format is fixed. The copy is the craft.

1. Intake

Ask once, only for what is missing:

  • Script or scripts. Ignore scratch or test tabs. Ask if a tab is unclear.
  • Brand name, exactly as the client writes it.
  • Deliverables with counts (example: 30s Hero Video (x3), 15s Cutdown (x3)). Never invent counts.
  • Shoot days and locations, if known. Which scripts share a day.
  • Product list with SKUs or product IDs, if the script names products.
  • Look. The default is the client's own brand (see below). If nothing is available yet, offer:
    • sky: sky-blue gradient dividers, Avenir. A neutral placeholder until brand colors are set.
    • ink: black and charcoal dividers, Helvetica. Editorial, premium, tech.
    • sage: soft green dividers, Georgia. Calm, natural, wellness and home.
    • custom: they upload a brand book, logo, screenshots or a website. Pull two divider colors, text color and font. Show the picks as hex codes and confirm before building. If a brand font is not installed on the viewer's machine, name a close system font and say so. If they don't choose and no brand is available, use sky.

Brand first. Sky blue is only the stand-in. Before building, look for the client's colors: a brand book, logo or screenshots the user shares, or the brand's website. Pull two divider colors, the text color and the font, show them as hex codes and confirm. Use sky blue only when there is no brand to pull from yet, and say in the hand-off that it is a placeholder to swap for brand colors. Write sky blue in the spec as "theme": {"base": "gold", "a": "56B4E9", "b": "1F7DC4"}. Never use the yellow gold palette.

2. Deck structure

Cover                 brand name, in the brand color
Overview              what the campaign is, who it speaks to, then Deliverables
Creative Approach     the insight, how each spot pulls one thread, where every spot lands
Cinematography        shared, only if one camera approach covers every spot
-- per script --
Divider               spot name; optional subtitle (theme line or "Day 1")
Cinematography        for this spot, unless shared
Location              placeholder for location selects
Production Design     for this spot
Casting               placeholder for casting selects
Wardrobe              for this spot
Storyboards           3 frames per slide
--
Thank You

Scenes number by script: script 1 = 101, 102... script 2 = 201... Never break script order. Scripts that share a shoot day may share one Cinematography, Production Design and Wardrobe section. Say so on the divider ("Scripts 1 & 3 / Day 1").

3. Writing each slide

Voice: a director writing for the crew. Short, considered paragraphs of two to four full sentences in the language of production: lensing, coverage, light, blocking, texture, set dressing, pacing. Every paragraph tells the crew something they can shoot, build or buy, and why it matters to the story. Sentences connect and build. Never stack fragments or write lines that read like taglines. No filler, no em dashes, no "elevate," "seamless," "immersive."

Overview (80 to 120 words before Deliverables). One short paragraph on what the campaign is and the world it lives in, a second on who it speaks to and what it should move them to do. Then the Deliverables block, one line per format.

Creative Approach (100 to 150 words). Open with the insight as a full thought, not a slogan. Then a sentence or two per spot on the thread it pulls and how it plays on screen. Close on where every spot lands (end card, URL, tagline).

Cinematography (3 short paragraphs, 40 to 55 words each). How the camera moves and why. Shot sizes and when to go wide. What the inserts must show and how readable they are. Light. Tie motion to emotion: when it moves, when it holds.

Production Design. Fixed shape:

  • Header line: SPOT NAME · SHORT TAGLINE in caps.
  • Two sentences of mood: how the space should feel, and why.
  • The Sets: each set in one or two sentences. Lived-in details (shoes by the door, drawings on the fridge).
  • Palette: 3 or 4 colors, plus where brand color appears in small, real places.
  • Essential Props: grouped, 2 to 4 lines. Hero product first, with colorway and SKU. Long lists go in the notes, not on the slide.

Wardrobe. Fixed shape:

  • Two sentences of mood for the location or spot.
  • One line per character: Name (Sex, Age): what they wear, and one detail that tells the story. Kids get exact ages. Adults get a range (Late 30s, Mid 20s).
  • Palette: line.
  • No logos unless the client's.

Storyboards. Each frame has:

  • VISUAL: slugline when the scene changes (INT. KITCHEN - DAY). Character names in caps on first appearance with age. Then 2 to 3 full sentences of direction: the action, the framing and any camera move. Use INSERT: for screen and product close-ups, CUT TO: for hard cuts, NOTE: for a must-get. Name the product with its SKU.
  • VOICEOVER | TEXT: VO: lines verbatim from the script. TEXT: for on-screen copy. SFX: and MUSIC: when the script calls for them. ALT: for a backup line.
  • Last frame is the end card. Add product family or colorway shots as extra scenes after it.
  • Preserve script VO and brand names exactly. Flag contradictions. Never fix them silently.

4. Fit

Boxes do not auto-shrink. Cut words, never font size.

  • Production Design: header, mood, 2 short blocks, 2 to 4 prop lines.
  • Wardrobe: mood, 1 line per character, palette.
  • Cinematography: 3 paragraphs, about 40 to 55 words each.
  • Storyboard visual: about 45 to 55 words. VO and text: about 25.

5. Legal flags

Before building, check the script for stats, superlatives, prices, offers, health or money claims, testimonials and third-party brands. Keep the line as written, add an ALT: safer version, and list each flag in the hand-off. Required disclaimers go in TEXT: with an asterisk. This is a first pass, not legal advice.

6. Build

Write a spec JSON, then run:

python scripts/build_deck.py spec.json outputs/<Brand>_PrePro_v1.pptx

Spec shape:

{
  "brand": "Brand Name",
  "theme": {"base": "gold", "a": "56B4E9", "b": "1F7DC4"},
  "cover_sub": "optional",
  "overview": ["line", "", "Deliverables:", "30s Hero Video (x1)"],
  "creative_approach": ["line", "", "line"],
  "shared_cinematography": ["optional; omit to write per spot"],
  "scripts": [{
    "title": "Spot Name", "subtitle": "optional", "base": 101,
    "cinematography": ["line"],
    "production_design": ["SPOT  ·  TAGLINE", "mood", "", "The Sets", "line", "", "Palette", "line", "", "Essential Props", "line"],
    "wardrobe": ["mood", "", "Name (Sex, Age): line", "", "Palette: line"],
    "location_placeholder": true, "casting_placeholder": true,
    "frames": [{"vis": "INT. ROOM - DAY\nAction.", "vo": "VO: line", "title": "ON-SCREEN TEXT"}]
  }]
}

theme is the brand's colors as a dict, sky blue as above when no brand is set yet, or the word ink or sage. It sets divider gradient colors (a, b), body text (ink), labels (grey), placeholders (ph), divider title color (title) and font. Any key left out falls back to the base style.

A full worked example is in references/example_spec.json.

"" is a blank line. Section heads (Deliverables:, The Sets, Palette, Essential Props) and caps header lines bold automatically. In Wardrobe, text before the first colon bolds.

7. Images (last step, only after the deck is approved)

Do not raise images until the user signs off on the deck. Then offer two paths in one line:

A. Their own images. They upload storyboard frames, scout photos, headshots or product shots. Name or map each to a key, put them in one folder, and rebuild: python scripts/build_deck.py spec.json out.pptx --images <folder> Images are cropped to fill each slot. Empty slots stay as placeholders.

B. AI prompt pack. Run python scripts/make_prompts.py spec.json <Brand>_Image_Prompts.md. Write image_style into the spec first: one line on look, light, palette and aspect, taken from the Cinematography and Production Design copy. Hand over the file. They paste prompts into any image tool, save each image with the key as its name, upload them, and you rebuild with --images.

Image keys:

  • Storyboard frame: the scene number (101, 102, 201).
  • Content slides: <script key>-design-1, -design-2, -wardrobe-1, -wardrobe-2, -cine-1, -cine-2.
  • Location and casting: -location-1 to -3, -casting-1 to -3.
  • Script key defaults to s1, s2... by script order. Set "key" on a script to override.

Never generate images of real, named people or trademarked characters. Casting slots are for the user's own talent photos.

Review pass (always, before presenting)

Every answer runs twice. The user never sees the first draft.

  1. Draft the full answer.
  2. Review it the way a demanding creative director and producer would, against the checklist below and every rule in this skill. Read the copy as if hearing it in a client meeting. Mark every miss.
  3. Fix every miss, then present only the revised version.
  4. End with one line: Review pass: <what changed>, or Review pass: no changes needed.

This applies to every step that produces something: research, options, copy, specs and files. For a file, build it, open or render it, check it, then fix and rebuild before handing it over.

Checklist

  • The deck uses the client's brand colors, or sky blue named as a placeholder in the hand-off. Never yellow.
  • Every script has its full section. Scene numbers in order. VO and brand names match the script exactly.
  • Copy reads as considered paragraphs in production language. No catchphrase fragments.
  • Render the deck and look at every slide. Nothing runs off a box. No placeholder text.
  • Legal flags listed. No names the user didn't give. No em dashes.

8. Check, then hand off

  • Every script has its full section. Scene numbers in order. Nothing runs off a slide (render with soffice and pdftoppm if available).
  • No placeholder text, no names the user didn't give, no em dashes.
  • Hand off in 3 lines: slide count, scripts and storyboard slides, then legal flags and open questions.
  • Images, casting and location selects drop in by hand. Say so.
  • Never add crew, talent or contact names without asking.

Individual skills in this repo

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

Related Skills