Generate a prompt pack
Use the generator when you have product facts, offer details, visual context, and a claim boundary.
Open generator
Guide
Strong UGC and product ad prompts give the model more than a vibe. These examples show how weak ad requests become Tool D-ready inputs with hook options, scene beats, camera notes, on-screen text, continuity, and a usable handoff.
Fast path
Use the generator when you have product facts, offer details, visual context, and a claim boundary.
Open generatorUse the AI Video Ad Stack Builder when the blocker may be source prep, destination, automation, or tracking.
Open stack modeUse the prompt checker when the ad request is still vague, overloaded, or relying on style words.
Open prompt checkerShort answer
A strong AI UGC video prompt gives the model a buyer situation, visible product action, offer, proof point, creator setting, and a few continuity anchors. Weak prompts usually ask for a vibe; strong prompts explain what the viewer should see, believe, and do next.
Prompt shape
Casual, premium, native, and high-converting are weak by themselves. The prompt becomes useful when the product, viewer situation, proof point, visual context, and offer are all concrete enough to become scenes.
Product:
[What is being sold, with visible product details]
Audience:
[Who this is for and what situation they are in]
Offer:
[The promise, trial, bundle, discount, or CTA]
Proof points:
[Specific facts that can appear visually or as support text]
Visual context:
[Creator setup, product setting, lighting, props, and continuity anchors]
Format:
[UGC script, product demo, founder story, or offer launch]
Platform:
[TikTok, Instagram Reels, YouTube Shorts, or general short-form]| Ad format | Useful input detail | Avoid |
|---|---|---|
| UGC proof ad | Creator situation, product use moment, phone or desk context, and one proof point. | Asking for casual or authentic tone without a visible product action. |
| Product demo | Product shape, package details, buyer situation, and a proof beat that can be shown. | Relying on premium, cinematic, or glossy as the main instruction. |
| Founder story | Founder problem, product insight, before-after moment, and tactile product detail. | Writing an inspirational monologue with no visible product proof. |
| Offer launch | Specific offer, audience urgency, package or app proof, and readable CTA support text. | Saying high converting without naming the trial, discount, bundle, or next action. |
Before and after
Each example starts with a weak request, then rewrites it into a Tool D-ready input and an expected output shape. The goal is not perfect copy. The goal is a prompt pack that can be inspected, revised, and moved into production one scene at a time.
These examples are synthetic teaching examples, not real customer campaigns. Treat any proof, testimonial, or offer language as draft structure until you replace it with verified product facts and approved claims.
Format: UGC script
Weak request: Make a TikTok ad for my focus timer app. It should feel casual, relatable, and not too salesy.
Tool D-ready input:
Product:
A pocket-sized focus timer app that turns one task into a clean 25-minute work sprint.
Audience:
Solo creators who keep losing momentum between planning, filming, and editing.
Offer:
Start a free sprint and finish one creative task before opening another app.
Proof points:
Simple timer, task label, end-of-sprint recap, no account required.
Visual context:
Creator desk, phone tripod, half-finished notes, realistic apartment setup.Expected output shape:
Hook options:
1. I stopped opening five apps before I started editing.
2. If your "quick task" keeps turning into a scroll break, try this.
3. This is the tiny sprint I use before I film anything.
Scene plan:
1. Native problem: creator looks at half-finished notes, phone on tripod, and too many open tabs.
2. Product use: close-up of the app starting a 25-minute sprint labeled "edit intro clip".
3. Proof beat: creator finishes the clip, checks the recap, and clears the desk.
4. Soft CTA: phone stays visible while the creator says to start one free sprint before opening another app.
Continuity:
Keep the phone screen readable, desk setup realistic, creator wardrobe casual, and task label consistent.Why it works: The staged version gives Tool D a buyer situation, visible app proof, and UGC-native context instead of asking for generic casual energy.
Format: Product demo
Weak request: Write a premium launch ad for a citrus drink. Make it energetic and cinematic for Instagram.
Tool D-ready input:
Product:
A sparkling citrus drink in recyclable slim cans with visible condensation.
Audience:
Busy city commuters who want a citrus drink for a desk or commute routine.
Offer:
12-can starter bundle, ships in 2 business days.
Proof points:
Real lemon, yuzu, green tea extract, 0g added sugar, recyclable slim cans.
Visual context:
Afternoon desk, commute bag, laptop, citrus ingredients, condensation, clean product close-ups.Expected output shape:
Hook options:
1. Your afternoon drink should fit the commute, not fight it.
2. Show the citrus desk moment before the can becomes the hero.
3. The product is small, but the page facts make the ad specific.
Scene plan:
1. Desk moment: commuter's laptop, packed calendar, cold coffee nearby, and commute bag set the buyer context.
2. Product reveal: close-up of the recyclable slim can with condensation, lemon, and yuzu nearby.
3. Proof beat: restrained support text names real lemon, yuzu, green tea extract, 0g added sugar, and recyclable slim can.
4. CTA payoff: starter bundle stays visible while the exact note ships in 2 business days appears as support text.
Continuity:
Keep the recyclable slim can readable, preserve the citrus ingredients, keep support text short, and avoid claims outside the source facts.Why it works: The revised input makes the product shape, offer, proof, and visual continuity explicit enough that the ad can become scenes instead of mood copy.
Format: Founder story
Weak request: Make a founder-led Shorts ad for a desk lamp. It should feel thoughtful and inspiring.
Tool D-ready input:
Product:
A compact matte-white desk lamp with adjustable warm light and a brass dimmer dial.
Audience:
Writers and students who want a calmer workspace without lighting the whole room.
Offer:
Switch to a softer focus setup with a launch-week bundle.
Proof points:
Three warmth levels, small footprint, dimmable dial.
Visual context:
Small desk, notebook, laptop, evening window, warm practical lighting.Expected output shape:
Hook options:
1. I built this lamp because late-night work should not feel like a hospital room.
2. The smallest desk change made my writing sessions feel calmer.
3. If your room light is too harsh for focus, this is the setup I wanted.
Scene plan:
1. Founder problem: founder sits under harsh room light with notebook and laptop open.
2. Product insight: hand adjusts the brass dial and shifts the desk into warmer focus light.
3. Proof beat: close-up shows the small footprint, matte finish, and three warmth levels.
4. Invitation: founder keeps the lamp visible and frames the launch-week bundle as a softer focus setup.
Continuity:
Preserve the matte-white lamp, brass dial, warm amber light, same desk, and founder-led tone.Why it works: The stronger version turns the founder story into a visible before-after lighting problem, not a vague inspirational monologue.
Format: Offer launch
Weak request: Create an ad for a meal kit discount. Make it fast, high converting, and good for Reels.
Tool D-ready input:
Product:
A weeknight meal kit with pre-chopped vegetables, measured sauces, and 15-minute recipe cards.
Audience:
Busy parents who want dinner to feel planned without doing another grocery run.
Offer:
Get the first three dinners for 30 percent off this week.
Proof points:
Pre-chopped ingredients, no subscription required, recipe cards stay under 15 minutes.
Visual context:
Kitchen counter, school bags by the door, quick pan, plated family dinner.Expected output shape:
Hook options:
1. Dinner can be planned before the backpacks hit the floor.
2. Three weeknight dinners without one more grocery run.
3. The 15-minute dinner kit for the nights that usually become takeout.
Scene plan:
1. Problem setup: parent enters kitchen as school bags land near the door.
2. Product proof: meal kit opens to pre-chopped vegetables, measured sauce, and a 15-minute card.
3. Result beat: quick pan-to-plate sequence shows dinner finished without messy prep.
4. Offer CTA: plated meal stays visible while the 30 percent first-three-dinners offer appears.
Continuity:
Keep the same kitchen, same meal kit packaging, same parent, clear ingredients, and readable offer text.Why it works: The ad gets a concrete household situation, visible proof, and a specific offer, so the scenes can support conversion without becoming pushy.
Revision passes
If the first request is weak, do not compensate by adding more cinematic words. Rewrite the commercial structure so Tool D can produce better hooks and scenes.
The generator needs to know who is watching and what problem is visible before the product appears.
Name the app screen, package detail, product action, before-after moment, or offer text that should show up in the scenes.
A UGC script, product demo, founder story, and offer launch need different hooks and proof beats. Choose the format before style.
Carry forward the product shape, screen state, wardrobe, location, or hero prop that would break trust if it drifted.
Common mistakes
A creator-native ad can still be structured. The stronger examples above keep the hook casual while making the product action, proof beat, and CTA visible.
Viral is not a production instruction. Replace it with the viewer situation, proof point, product action, and CTA.
Creator-native does not mean product-optional. Give the scenes a visible use moment or proof beat early enough to matter.
A weak CTA makes the final scene generic. Include the trial, bundle, discount, waitlist, or next action before generating the pack.
Continuity should protect trust-critical details, not paste the whole brief into every shot.
FAQ
These answers summarize the revision pattern behind the examples above.
A strong AI UGC video prompt names the product, viewer situation, offer, proof point, creator context, and continuity anchors. Tone words help only after those visible details are clear.
Rewrite a weak UGC prompt by replacing vague style goals with a buyer situation, visible product proof, a chosen format, and the details that must stay consistent across scenes.
A Tool D-ready UGC input should include product details, audience, offer, proof points, visual context, format, and platform so the generator can produce hooks, scenes, camera notes, text, and continuity.
Related paths
Once the ad examples make sense, move into the generator, the workflow guide, or the image-to-video branch depending on what still needs control.
Use Tool D when you have one product, offer, UGC, or founder-story concept and need hooks, scenes, camera, text, and continuity.
Open AI Video Ad Stack BuilderUse the Tool D workflow guide when you want the full order behind product facts, hooks, scene beats, and model-ready handoff prompts.
Read AI video ad workflowUse Image to Video Prompt Generator after an ad scene produces a stable product still, phone screen, or first frame.
Open AI Video Ad Stack BuilderUse the Kling workflow when the shared ad plan needs more direct per-scene Kling prompt wording.
Open Kling ad promptsUse the Veo workflow when the shared ad plan needs continuous scene sequencing, cleaner transitions, and selective continuity carry-through.
Open Veo ad promptsUse the Seedance workflow when the shared ad plan needs readable short-form rhythm, beat timing, and compact continuity guardrails.
Open Seedance ad prompts