Claude Code: build a 30-second product ad from real footage

AI-assisted ads: begin with a supported promise

A 30-second ad need not list every feature. It should help a specific audience understand a supported benefit and the next action. Claude Code can organize assets, write composition code and coordinate rendering; it does not verify product efficacy, image rights or ad performance.

The exercise uses a fictional shop with real footage of a bottle and an office-worker audience. No real brand, specifications or sales improvement are attributed to the illustrative product. BHKD authored these practice prompts.

1. Write a one-page brief before editing

Define audience, use context, one substantiated benefit, tone, CTA, aspect ratio and permitted assets. List details that must not be invented: price, discount codes, testimonials, warranty and performance claims. Leave unsupported benefits blank or request confirmation.

Brief prompt: Use the product description and input assets to prepare a 30-second ad brief for [audience]. Separate supplied facts from missing information. Use only supported benefits; do not infer efficacy from images. Propose one message and one CTA. Do not edit yet; provide the brief for approval.

2. Inventory footage and identify missing shots

A compact shot set can include a full product view, detail, usage and a closing shot with CTA space. Capture enough duration for editing and maintain consistent light and color. Do not invent leakproof or temperature-retention demonstrations without appropriate testing; attractive imagery is not evidence.

Asset prompt: Inventory readable input media, describe inspected shots and quality limits using available tools. Match shots to the approved brief and flag gaps. Do not replace the product with AI imagery or download stock without permission. Report unreadable files rather than guessing from filenames.

3. Give each part of the 30-second timeline a purpose

Suggested structure: 0-4 seconds for context or a question, 4-12 for the product, 12-23 for a supported benefit and 23-30 for the CTA. This is an exercise framework, not a performance guarantee. Allow time for necessary qualifications instead of extra transitions.

Storyboard prompt: Create a 30-second table of timing, source shots, on-screen copy, narration and purpose. Use actual files and grounded timecodes, not invented footage. Keep copy concise and avoid best or guaranteed-result claims without evidence. Wait for approval before rendering.

4. A sample prompt for a bottle introduction

An example opening is A small place for a daily water-drinking habit, if appropriate for the shop. This introduces a habit and a product without promising health benefits or inventing specifications. For a real item, use product-owner-approved copy.

Draft prompt: Use the approved brief and storyboard for a 30-second 1080×1920 video. Use only authorized input photos, footage, logos and music. Preserve product shape, color and details without adding specifications. Use Vietnamese-capable type, brand colors and restrained transitions. CTA: See product information at the link in the description. First render a ten-second opening and report tools, versions and issues; do not publish a final version yet.

5. Recompose vertical and horizontal versions

Changing 9:16 to 16:9 is not stretching or center cropping. Check product, hands, copy and logo in each layout. Preview key scenes before full rendering to avoid finishing an unusable composition.

Multi-format prompt: Recompose the approved vertical edit at 1920×1080. Do not stretch images or crop key product details. Reflow text and CTA; provide opening, benefit and closing frames for approval. If footage cannot support the layout, state the limitation and suggest extra filming instead of inventing details.

6. Review the product, message and export

Watch both final formats: verify product color and proportions, readable copy, supported specifications, narration/caption agreement and correct CTA destination. Check asset permissions. A successful render does not establish factual accuracy or compliance with every platform policy.

Delivery prompt: Export each MP4, editable project and asset list. Report files actually inspected, duration and dimensions, plus items needing human review. Preserve sources and approvals; do not publish or launch ads automatically. Clearly report missing files or failed renders rather than marking completion.

Practice worksheet: what to shoot before opening Claude Code?

Use this worksheet to align filming and editing. After inspection, add filename, usable duration, reviewer and missing-asset notes. Do not film every shot if the message does not require it; prioritize evidence for what you intend to say.

Missing-shot prompt: Compare the approved brief, shot list and actual footage. Suggest additional filming only for specific gaps, specifying angle, action, copy space and product-representation risks. Do not replace efficacy demonstrations with generated imagery.

Three hook approaches without changing the entire video

These examples serve the fictional exercise. Choose an approach suited to positioning and adapt it to the brand’s real voice. Do not turn it into claims about savings, health or hours of temperature retention without support.

Variant prompt: Produce two drafts differing only in the first 0-4-second hook. Keep the remainder, CTA and export settings consistent. Name them A and B and log the difference. Check scene relevance and avoid new promises. Do not declare a winner before appropriate comparative data exists.

Review on a phone and assign responsibility

A video that looks good on an editing monitor may be hard to read on a phone. Watch the full export at actual size, review vertical and horizontal versions separately and test muted comprehension. This is content review, not a substitute for checking the intended channel’s advertising policies.

Where staffing allows, assign visual review, product-fact approval and release approval. Small shops may combine roles, but should record review date and file version. Mark approved only once material issues are resolved.

A complete 30-second storyboard: assign each shot a task

This expands the fictional bottle exercise. Times are proposed output positions, not source timecodes discovered in user footage. In practice, map each row to actual files and source ranges; report missing shots rather than inventing paths or source timings.

Storyboard application prompt: Check this 30-second plan against readable assets. Add actual source file, in/out timecodes and selection reason. Do not loop footage in a way that misrepresents an action. If assets are insufficient, propose a shorter cut or extra filming. After approval, render a restrained draft to review pacing first.

Revision prompt: change only the specified parts

Each feedback round should identify file version, output timecode, observable issue and desired result. Separate required fixes from preferences to explore. Keep the approved baseline; changing a phrase should not accidentally alter all product colors or music.

Copyable prompt: Revise [filename] using the approved feedback below. For each item, record timecode, proposed change and invariants. Change only specified items; preserve the current message, product, logo and other assets. Export before/after segments, save a new version and log changes. If instructions conflict or lack necessary information, ask a specific question before editing that part.

After publishing: test one change at a time

One possible test uses two versions differing only in the opening. Keep the rest consistent and record audience, placement, timing and goal to understand comparison limits. With limited data, do not declare a winner after a few views.

Track goal-relevant available metrics such as qualified views, product-page visits or attributed orders. Visual polish is not profit. Business lesson: AI can accelerate repetitive production, but customer understanding, accurate messaging and validation remain central.

Suggested actions