Product Ad Production

Product Ad Production

Produce an advertisement that makes the right person recognize a relevant situation, understand what the product changes, believe the proof, and know what to do next. Visual polish is not a substitute for product comprehension or claim support.

This skill is provider-neutral. Select image, video, capture, voice, music, editing, and composition tools only after the advertising problem is defined. Do not let a generation model's favorite visual language determine the concept.

Evidence language used here

• Documented fact means a requirement or principle stated by a regulator, standards body, or platform source.
• Research finding means an empirical result with a stated source and scope. It is evidence, not a guarantee for a new campaign.
• Practitioner heuristic means a production rule worth testing, not a universal truth.

Platform behavior and ad products change. Platform facts in this skill were verified 2026-07-09. Re-check the exact placement specification, policy, interface preview, and destination requirements immediately before export and trafficking.

Start with a decision-grade brief

Do not write a script from a slogan and a product URL. Diagnose the commercial problem first.

Minimum input record

Capture or infer each field, marking assumptions explicitly:

| Field | Required decision | |---|---| | Business outcome | Awareness, consideration, lead, trial, purchase, upsell, retention, or launch learning | | Primary success measure | One decision metric; supporting and guardrail metrics are separate | | Audience | Purchase situation and constraints, not demographics alone | | Job to be done | Progress sought, present struggle, emotional/social stakes, and competing solutions | | Awareness state | Unaware, problem-aware, solution-aware, product-aware, or returning customer | | Product truth | What the product is, how it works, prerequisites, limitations, price/offer, and current availability | | Proposition | One useful change the ad will make credible | | Evidence | Approved substantiation, demonstrations, customer data, certifications, testimonials, and provenance | | Objection | The most consequential reason a qualified viewer may not act | | Placement | Platform, ad product, buying objective, duration, aspect ratio, UI overlays, and sound context | | Destination | Exact landing page or store state; product, offer, naming, and price must agree with the ad | | Brand system | Correct product/packaging, marks, type, colors, sonic assets, and prohibited treatments | | Rights and policy | Talent, location, music, stock, creator, user content, AI/replica consent, category restrictions | | Production constraints | Deadline, budget, available real product, UI build, languages, render and review path |

Return one of three diagnoses:

• Ready: proposition, evidence, destination, and rights can support production.
• Conditional: production can proceed with named assumptions or conservative wording pending approval.
• Blocked: a material claim, offer, product state, destination, or permission is missing. Do not invent it.

Audience through the job, not the persona costume

Jobs to Be Done theory treats products as choices people make to achieve functional, emotional, and social progress, not merely as bundles of attributes [S1]. Translate the job into an ad-specific record:

When [situation/trigger], this person is trying to [progress],
but [friction/anxiety/current alternative].
They will believe a better option when they see [proof],
and the smallest credible next action is [CTA].

Separate buyer, user, approver, and beneficiary when they differ. For B2B, map the operational user, economic buyer, security/legal reviewer, and implementation owner. An ad normally speaks to one primary role and acknowledges one decisive objection; it should not average all roles into vague corporate language.

Build a claim system before a visual system

Documented fact—United States: advertising must be truthful and non-deceptive, advertisers must possess evidence for claims, and ads cannot be unfair [S2][S3]. The FTC evaluates the ad's overall or “net” impression, including words, images, sounds, omissions, and format; a small disclosure does not neutralize a misleading main message [S4]. Other jurisdictions and regulated categories may impose additional rules. Obtain qualified legal review when stakes warrant it.

Claim ledger

Create the ledger before scripting. Every spoken, written, visual, sonic, comparative, and implied claim gets an ID.

| Field | Record | |---|---| | Claim ID | Stable identifier used in script, shot list, and approvals | | Exact expression | Wording or visual implication the viewer receives | | Type | Existence/feature, performance, quantified, comparative, superiority, price/offer, testimonial, environmental, health/safety, or illustrative | | Audience interpretation | Reasonable takeaway, including likely implied meaning | | Evidence | Document, dataset, test report, product record, or approved customer source | | Scope | Model/SKU, population, conditions, geography, dates, and exclusions | | Qualification | Material information needed beside the claim | | Demonstration link | Shot IDs that prove or illustrate it | | Owner and approval | Product/legal/brand approver and status | | Expiry trigger | Product revision, offer end, evidence age, or policy change |

Evidence discipline

1. Prefer direct, current evidence for the exact advertised product and conditions.
2. Match the claim's strength to the evidence. A measured customer outcome is not automatically a causal product effect; a laboratory result is not automatically typical consumer performance.
3. Preserve denominators, sample, comparison baseline, time period, and material conditions for quantified claims.
4. Use “up to,” “from,” or “as much as” only when accurate and not misleading about expected results.
5. Treat the depiction itself as a claim. An impossible cleanup, instant software response, enlarged product, synthetic testimonialist, or hidden edit can create a false impression without a false sentence.
6. If a scene is conceptual rather than evidentiary, make its illustrative role unambiguous. Do not style an animation like a measurement readout unless it reflects measured data.
7. Keep required qualifications proximate, legible, understandable, and present long enough to read. Rewrite the main claim when the qualification would need to contradict it.
8. Never fabricate awards, press marks, certifications, reviews, ratings, customers, interfaces, prices, scarcity, before/after states, or competitor behavior.

Testimonials, creators, and reviews

Documented fact—United States: endorsements must reflect the endorser's honest experience; material connections should be clearly disclosed, and atypical results may require disclosure of generally expected results [S3][S5]. The FTC advises placing a social disclosure with the endorsement itself, making it hard to miss, and including it in the video rather than relying only on a description [S5]. The U.S. Consumer Reviews and Testimonials Rule prohibits specified fake or false reviews and testimonials, including certain AI-generated fakes [S6].

Maintain a testimonial packet: original statement, permission, identity, actual-use confirmation, compensation/material connection, editing approval, validity date, and support for any product claim repeated by the endorser. An actor may portray a dramatized user only when the ad cannot reasonably be read as that actor's genuine testimonial. Label dramatizations where needed.

Choose a product-centered concept

Compress the strategy into:

For [audience in situation], [product] changes [friction] into [outcome]
because [credible mechanism/proof]. After viewing, do [one action].

Generate multiple concepts that differ in mechanism, not merely art direction. Useful concept families include:

• Observable transformation: a credible before/use/after with controlled continuity.
• Mechanism reveal: show the feature causing the benefit.
• Stress or boundary test: demonstrate a supported limit under disclosed conditions.
• Routine compression: contrast the old sequence with the product-enabled sequence without manipulating elapsed time.
• Objection reversal: surface the barrier, then prove the answer.
• Evidence story: build around a verified user or business result with scope visible.
• Product-as-interface: let the real workflow, handling, sound, or result carry the message.
• Identity or ritual: associate product use with an emotional/social job while keeping the product causally legible.

Score each concept from 0–3 on audience relevance, claim support, product centrality, demonstration clarity, brand distinctiveness, placement fit, variant potential, feasibility, and rights/policy risk. Reject any concept whose appeal depends on a behavior the product cannot perform.

Research finding—platform-specific: Google's data-backed ABCD guidance recommends earning attention, branding early and throughout, creating a focused human connection, and giving clear direction; for consideration it specifically recommends making the product prominent and showing how it works [S7]. Google's reference guide also says its evidence is correlational and not a one-size-fits-all guarantee [S8]. Use this as informed prior evidence, then test it for the brand and placement.

Product legibility contract

The viewer should be able to answer, at the appropriate moment:

1. What is being advertised?
2. What does it do or change?
3. How do I know?
4. Is this the exact product/plan/offer I will reach?
5. What should I do next?

Design explicit recognition events:

• an early product or brand cue appropriate to the objective;
• at least one unobstructed, correctly shaped product/package/UI view;
• a readable name or a distinctive asset that the intended audience can actually link to the brand;
• product interaction at a scale that makes the mechanism understandable;
• a late memory/choice cue and destination-consistent CTA.

Do not assume that a tiny logo, generic color, or beauty silhouette identifies an unfamiliar product. The Ehrenberg-Bass Institute describes a strong distinctive asset as both famous and unique to the brand; an unmeasured visual element should not be treated as a brand-name substitute [S9].

Practitioner heuristic: perform a “blurred-thumbnail test” for silhouette/color recognition, a one-second freeze-frame test for product/category recognition, and a five-second recall check with people who did not see the brief. These are diagnostic screens, not campaign-effectiveness measures.

Design demonstrations as evidence

A demonstration is a small experiment presented to viewers. Define it before shooting or generating:

| Element | Question | |---|---| | Claim | What exact viewer conclusion may this demo support? | | Unit | Which real SKU, version, plan, build, and accessories are used? | | Conditions | What environment, starting state, preparation, network, lighting, load, or operator skill matters? | | Comparator/control | Is the baseline fair, current, and equivalently prepared? | | Procedure | What actions happen, in what order, and how are they timed or measured? | | Capture | Which uninterrupted wide proof shot and which detail inserts are needed? | | Repetitions | Is one event enough, or must variability/typicality be shown? | | Qualification | Which material conditions must appear with the result? | | Failure rule | What result stops the advertised claim or requires revised language? |

For physical products, capture a continuity master that shows setup, product, hands, comparator, timer or measuring device, and outcome without a claim-altering cut. Detail shots can improve comprehension but cannot replace the proof master.

For software and apps:

• use the approved production build or a clearly marked prototype;
• preserve real labels, steps, latency, permissions, data states, and prerequisites;
• use synthetic data that cannot expose private or confidential information;
• do not remove required steps merely to make the workflow seem instant;
• distinguish a UI concept animation from an actual screen recording;
• verify the landing experience matches the plan, feature, and availability shown.

For comparisons, match conditions and show the basis of comparison. Avoid degrading a competitor, choosing an obsolete baseline without disclosure, changing camera treatment to favor one outcome, or saying “better” without defining the dimension.

Practitioner heuristic: if the proof cannot survive a locked-off wide shot, it is not yet a demonstration; it is an illustration. Illustration can still be useful, but label and script it accordingly.

Turn the proposition into time

There is no mandatory hook-problem-solution template. Build beats around the viewer's decision and the placement's interruption pattern.

Possible beat functions:

• Pattern entry: a relevant action, consequence, contradiction, question, or result—not unrelated spectacle.
• Situation recognition: make the viewer recognize their job and friction.
• Product identification: name and show the product without delaying until attention is already spent.
• Mechanism or use: reveal how the feature changes the situation.
• Proof: demonstrate, quantify with scope, or present an authentic experience.
• Objection handling: answer the barrier that would otherwise block action.
• Consequence: show the useful or emotional result without overclaiming causality.
• Choice and action: reinforce product, offer if applicable, and one next step.

Beat sheet

For every beat, record:

time range | beat purpose | viewer question answered | visual action
product/brand cue | dialogue/VO | on-screen text | claim IDs
audio event | transition logic | source asset | disclosure/qualification
placement risks | cutdown dependency

Script rules

• Write for the spoken duration and leave comprehension room; do not fill every frame with words.
• Let image, speech, text, and sound contribute different information. Do not make four channels compete.
• Keep the primary proposition expressible in one sentence.
• Use product language the audience uses, but retain exact terms where plan/version differences matter.
• Bind every number and superlative to a claim ID.
• Make qualifications syntactically understandable, not a legal-text dump.
• Ensure the CTA follows sufficient context. “Shop now” before the viewer knows what or why is not direction.
• Avoid fake urgency, clickbait that the body cannot repay, and first-person claims spoken by synthetic talent as if personally experienced.

Shot architecture

Specify shots by advertising function, not by decorative camera vocabulary:

| Shot role | Acceptance criterion | |---|---| | Product identity | Exact product is recognizable; logo/label is not malformed or obscured | | Situation | Friction is clear without stereotyping or humiliating the user | | Operation | Contact points, sequence, orientation, and causality are readable | | Proof master | Claim-relevant action remains continuous and conditions are visible | | Detail | Reveals a mechanism or result the master cannot show | | Human consequence | Performance and result match the intended audience/job | | Offer/CTA | Product, offer, destination, terms, and next action agree |

AI-generated shots require additional continuity controls: approved pack/reference images, geometry and label verification, state tracking across shots, hand/product interaction review, and a ban on hallucinated ports, controls, accessories, ingredients, results, or interface elements. When accuracy is essential, use real product capture, composited pack shots, deterministic 3D, or real UI rather than asking a generative model

…

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: calesthio
• Source: calesthio/generative-media-skills
• License: MIT
• Homepage: https://github.com/calesthio/OpenMontage

Install and usage instructions live in the source repository linked above.