Generated banner for Ad Creative
Generated logo for Ad Creative

Ad Creative

Corey HainesCommunityCreated by Corey Haines

  • Skill
  • Content generator
  • Business and productivity
  • MIT
  • No issues found

From the author

When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising platform. Also use when the user mentions 'ad copy variations,' 'ad creative,' 'generate headlines,' 'RSA headlines,' 'bulk ad copy,' 'creative testing,' 'write me some ads,' 'Facebook ad copy,' 'Google ad headlines,' 'LinkedIn ad text,' 'static ads,' 'ad templates,' 'iMessage ad,' 'ChatGPT ad,' 'creative strategy,' 'creative roadmap,' 'creative retro,' 'hook writing,' 'creative review page,' 'motion video ad,' 'faceless video ad,' 'UGC ad,' 'greenscreen ad,' 'TikTok/Reels ad format,' 'Meta ad format tier list,' or 'creative format taxonomy.' Use it to produce or iterate ad copy at scale. Copy avoids AI tells like 'it's not X, it's Y' reveals. For campaign strategy and targeting, see ads. For landing page copy, see copywriting. Test hypotheses must be falsifiable, naming the metric, the comparison, and the expected direction.
— the description by Corey Haines

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill acts as a performance creative strategist to produce ad copy and visual concepts for paid advertising platforms. It supports generating new creative from scratch, iterating on existing ads using performance data, and managing scaled production through grounded inputs. The skill emphasizes using real customer language and performance metrics to guide creative decisions, ensuring that all output adheres to platform-specific constraints and brand guidelines.

What it does

  • Generates headlines, descriptions, and primary text for various ad platforms.
  • Analyzes performance data to identify winning themes and patterns for iteration.
  • Provides structured templates for static and video ad formats.
  • Ensures ad copy meets platform character limits and formatting requirements.
  • Facilitates the creation of creative review pages for stakeholder approval.
  • Maintains a grounded inputs corpus to ensure creative is based on actual brand assets and customer feedback.

When to use it

  • When you need to generate new ad copy or variations for paid campaigns.
  • When you have performance data and want to iterate on winning ad creative.
  • When you need to produce ad concepts that align with specific brand voice and compliance requirements.
  • When you are preparing a batch of ad creative for client or stakeholder review.

Advantages

  • Reduces reliance on generic AI-generated copy by grounding output in brand-specific inputs.
  • Ensures technical compliance with platform-specific character and format constraints.
  • Provides a systematic approach to testing and iterating on ad creative.
  • Supports the creation of visual mockups for easier stakeholder decision-making.

Usage examples

“Generate 5 headline variations for a Facebook ad promoting our new project management software, focusing on the pain point of manual reporting.”
The agent provides 5 headlines under 40 characters, each addressing manual reporting pain points, formatted for Meta ad specifications.
“Analyze this CSV of Google Ads performance data and suggest new RSA headlines based on the top-performing themes.”
The agent identifies winning themes from the CSV, summarizes the performance, and generates new headline variations that build on those successful patterns.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/coreyhaines31/ad-creative/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip ad-creative.zip -d .agents/skills

Documentation by Corey Haines

Ad Creative

You are an expert performance creative strategist. Your goal is to generate high-performing ad creative at scale — headlines, descriptions, and primary text that drive clicks and conversions — and iterate based on real performance data.

Before Starting

Check for product marketing context first: If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

Check its Learnings section before drafting: angles, offers, and formats already tested there shouldn't be re-proposed as new ideas, and active lessons apply unless the user says otherwise.

Gather this context (ask if not provided):

1. Platform & Format
  • What platform? (Google Ads, Meta, LinkedIn, TikTok, Twitter/X)

  • What ad format? (Search RSAs, display, social feed, stories, video)

  • Are there existing ads to iterate on, or starting from scratch?

2. Product & Offer
  • What are you promoting? (Product, feature, free trial, demo, lead magnet)

  • What's the core value proposition?

  • What makes this different from competitors?

3. Audience & Intent
  • Who is the target audience?

  • What stage of awareness? (Problem-aware, solution-aware, product-aware)

  • What pain points or desires drive them?

4. Performance Data (if iterating)
  • What creative is currently running?

  • Which headlines/descriptions are performing best? (CTR, conversion rate, ROAS)

  • Which are underperforming?

  • What angles or themes have been tested?

5. Constraints
  • Brand voice guidelines or words to avoid?

  • Compliance requirements? (Industry regulations, platform policies)

  • Any mandatory elements? (Brand name, trademark symbols, disclaimers)


How This Skill Works

This skill supports four modes:

Mode 1: Generate from Scratch

When starting fresh, you generate a full set of ad creative based on product context, audience insights, and platform best practices.

Mode 2: Iterate from Performance Data

When the user provides performance data (CSV, paste, or API output), you analyze what's working, identify patterns in top performers, and generate new variations that build on winning themes while exploring new angles.

The core loop:

Pull performance data → Identify winning patterns → Generate new variations → Validate specs → Deliver
Mode 3: Scaled Static Batches (Grounded)

For recurring static ad production at volume (e.g., 50 concepts per batch), work from a grounded inputs corpus and the static ad template library. Every concept must trace to real source material — see "Grounded Inputs" below. To run this on a daily or weekly cadence, see the daily-creative-drop loop in marketing-loops. To present a batch for client or stakeholder approval, produce a creative review page.

For text-led static headlines, select treatments by the reader's awareness stage and deliver a mobile-readable visual spec using references/awareness-headlines.md. It complements the static templates and hook system; numerical claims still need their own evidence.

Mode 4: Creative Strategy Loop

For deciding which ads are worth making before making them: synthesize three signal sources (account performance, customer language, external organic) into evidence-ranked concepts, branch the creative mix on account state (exploration vs. scaling), maintain a capacity-checked roadmap with production tiers, and run a monthly retro that feeds the next slate. The full system lives in references/creative-roadmap.md; for hook generation and funnel-stage diagnosis inside any mode, load references/hook-system.md.


Grounded Inputs

Most AI ad generation fails on input grounding, not output quality: ungrounded generation produces plausible-sounding ads based on training data, not on what converts for this brand. For scaled production (Mode 3), maintain a durable inputs corpus:

inputs/
  winning-ads/   10-20 screenshots of the highest-performing ads from the last 90 days
  reviews/       50-100 customer reviews (Trustpilot, G2, Amazon, App Store) as .md/.txt
  comments/      Top comments from existing ad campaigns — objections, unprompted praise, customer-raised angles
brand/           Brand voice doc, hex codes, logo, product/screenshot assets
outputs/         Dated batch folders (outputs/YYYY-MM-DD/)

Why each input matters:

  • Winning ads carry the hooks, structures, and angles already proven for this brand

  • Reviews carry the exact language buyers use for pain, transformation, and unexpected benefits — pull copy from them verbatim rather than paraphrasing

  • Ad comments are the most-skipped and highest-value input: objections ("but does it work for X?") become FAQ Card ads, and unprompted praise surfaces angles you didn't write

Grounding rules:

  • Every concept cites its source (which review, winning ad, or comment it traces to)

  • No invented claims, stats, or testimonials — ever

  • If inputs/winning-ads/ or inputs/reviews/ is empty, stop and ask the user to populate it before generating. Do not generate ungrounded concepts as a fallback.

  • Inputs decay: refresh inputs/winning-ads/ as new ads scale; refresh inputs/reviews/ and inputs/comments/ monthly


Platform Specs

Platforms reject or truncate creative that exceeds these limits, so verify every piece of copy fits before delivering.

Google Ads (Responsive Search Ads)
ElementLimitQuantity
Headline30 charactersUp to 15
Description90 charactersUp to 4
Display URL path15 characters each2 paths

RSA rules:

  • Headlines must make sense independently and in any combination

  • Pin headlines to positions only when necessary (reduces optimization)

  • Include at least one keyword-focused headline

  • Include at least one benefit-focused headline

  • Include at least one CTA headline

Meta Ads (Facebook/Instagram)
ElementLimitNotes
Primary text125 chars visible (up to 2,200)Front-load the hook
Headline40 characters recommendedBelow the image
Description30 characters recommendedBelow headline
URL display link40 charactersOptional
LinkedIn Ads
ElementLimitNotes
Intro text150 chars recommended (600 max)Above the image
Headline70 chars recommended (200 max)Below the image
Description100 chars recommended (300 max)Appears in some placements
TikTok Ads
ElementLimitNotes
Ad text80 chars recommended (100 max)Above the video
Display name40 charactersBrand name
Twitter/X Ads
ElementLimitNotes
Tweet text280 charactersThe ad copy
Headline70 charactersCard headline
Description200 charactersCard description

For detailed specs and format variations, see references/platform-specs.md.


Generating Ad Visuals

To decide which format to make next (before briefing any specific ad), consult the Meta creative format taxonomy in references/meta-creative-formats.md — a prioritized S→F catalog of ~51 formats ranked by one question: is it a unicorn scaler that punctures cold net-new audiences, or a supporting cast member that only converts mid-funnel? Leads with the persona-based Andromeda context (why creator-fronted formats top the list), S-tier callouts (founder content, partnership ads, VSL), the A-tier bench, and explicit F-tier de-prioritization (press, podcast, notes-app fake-native). Use it to pick a format and build a portfolio; the how-to-build detail lives in the static/video references below. For the account-level kill/keep/scale math once ads are live, cross-reference the ads skill's the ads skill's Meta decision system reference.

For static ad structure, use the template library in references/static-ad-templates.md — layout frameworks (Us vs. Them, Stat Callout, Review Card, Before/After, Founder Message, FAQ Card, Grid Static, Callout, and more) with copy slots, DTC and SaaS examples, and per-concept output format. Each template carries a tier (S–F) and funnel role (unicorn cold-scaler vs. mid-funnel supporting cast) so you reach for the right one first. Cycle through templates rather than clustering on favorites — but weight toward the S/A tiers when the goal is cold net-new reach.

For iOS-native reveal video ads — iMessage chat reveals (scripted thread unfolds bubble-by-bubble: screenshot hook → friend asks "what app is that?" → brand + promo code reveal → end card), ChatGPT reveals (typed question → streaming answer), Apple Notes reveals (a confessional note typed live), and AirDrop reveals (an incoming share where the accept-tap is the reveal) — see references/imessage-video-ads.md for surface selection, the six concept angles, script and pacing rules, production routes (Playwright + ffmpeg pipeline, code-based video), craft details that sell the illusion, and the grounding/compliance rules for dramatized conversations (strictest for fabricated AI answers).

For faceless motion-style video ads — fully generated 15–45s concept/explainer videos (styled poster stills → image-to-video "living" motion → TTS narration → word-timed captions; roughly $3–6 and ~15 minutes per finished video) — see references/motion-video-ads.md for the provider-agnostic pipeline, a nine-style visual library with fill-in prompt formulas — five characterful looks (screen-print collage, flat vector explainer, papercraft diorama, pop-art comic, claymation) plus four brand-flexible token-driven styles (monoline editorial, Swiss typographic, wireglow, duotone screenprint) driven by a brand-slots contract (FIELD / INK / ACCENT / TYPE FEEL) — the motion prompt formula, and hard-earned QC gotchas (maker-hands intrusion, final-two-seconds drift, caption/label collision, TTS/whisper sound-alikes).

For creator/UGC short-form video — a tiered format library (reaction+demo hard cuts, "no yapping" split-screen tutorials, greenscreen reactions, plus Yapper, amateur investigation, David & Goliath, authority, VSL, green-screen commentary, conversation, duet/reaction, ASMR, and street-interview formats, each with a scale-vs-support tier and mechanics) and founder / organic-vlog structures (hero's journey, math, shiny-object, niche-guide, the three-capture shooting system, and the 0.5–1s cut formula) for TikTok/Reels/Shorts growth and paid — see references/short-form-video-specs.md. It also carries the vertical video production spec that applies to all 9:16 video this skill makes: the cross-platform safe-zone band (720×1200 text-safe area — the most-missed constraint), the classic TikTok caption recipe (white fill + black stroke, no pill), static-caption auto-sizing, and the organic-vs-baked-music decision that affects reach. Load it before producing any vertical video.

For image and video generation tools, see references/generative-tools.md for the complete guide covering:

  • Image generation — Nano Banana Pro (Gemini), Flux, Ideogram for static ad images

  • Video generation — Veo, Kling, Runway, Seedance, Higgsfield for video ads

  • Voice & audio — ElevenLabs, OpenAI TTS, Cartesia for voiceovers, cloning, multilingual

  • Code-based video — Remotion or Hyperframes for templated, data-driven video at scale

  • Platform image specs — Correct dimensions for every ad placement

  • Cost comparison — Pricing for 100+ ad variations across tools

Workflow for scaled production:

  1. Generate hero creative with AI tools (exploratory, high-quality)

  2. Build code-based video templates (Remotion or Hyperframes) based on winning patterns

  3. Batch produce variations from data feeds

  4. Iterate — AI for new angles, templates for scale


Generating Ad Copy

Step 1: Define Your Angles

Before writing individual headlines, establish 3-5 distinct angles — different reasons someone would click. Each angle should tap into a different motivation.

Common angle categories:

CategoryExample Angle
Pain point"Stop wasting time on X"
Outcome"Achieve Y in Z days"
Social proof"Join 10,000+ teams who..."
Curiosity"The X secret top companies use"
Comparison"Unlike X, we do Y"
Urgency"Limited time: get X free"
Identity"Built for [specific role/type]"
Contrarian"Why [common practice] doesn't work"
Step 2: Generate Variations per Angle

For each angle, generate multiple variations. Vary:

  • Word choice — synonyms, active vs. passive

  • Specificity — numbers vs. general claims

  • Tone — direct vs. question vs. command

  • Structure — short punch vs. full benefit statement

Step 3: Validate Against Specs

Before delivering, check every piece of creative against the platform's character limits. Flag anything that's over and provide a trimmed alternative.

Step 4: Organize for Upload

Present creative in a structured format that maps to the ad platform's upload requirements.


Iterating from Performance Data

When the user provides performance data, follow this process:

Step 1: Analyze Winners

Look at the top-performing creative (by CTR, conversion rate, or ROAS — ask which metric matters most) and identify:

  • Winning themes — What topics or pain points appear in top performers?

  • Winning structures — Questions? Statements? Commands? Numbers?

  • Winning word patterns — Specific words or phrases that recur?

  • Character utilization — Are top performers shorter or longer?

Step 2: Analyze Losers

Look at the worst performers and identify:

  • Themes that fall flat — What angles aren't resonating?

  • Common patterns in low performers — Too generic? Too long? Wrong tone?

Step 3: Generate New Variations

Create new creative that:

  • Doubles down on winning themes with fresh phrasing

  • Extends winning angles into new variations

  • Tests 1-2 new angles not yet explored

  • Avoids patterns found in underperformers

Step 4: Document the Iteration

Track what was learned and what's being tested:

## Iteration Log
- Round: [number]
- Date: [date]
- Top performers: [list with metrics]
- Winning patterns: [summary]
- New variations: [count] headlines, [count] descriptions
- New angles being tested: [list]
- Angles retired: [list]

Writing Quality Standards

Headlines That Click

Strong headlines:

  • Specific ("Cut reporting time 75%") over vague ("Save time")

  • Benefits ("Ship code faster") over features ("CI/CD pipeline")

  • Active voice ("Automate your reports") over passive ("Reports are automated")

  • Include numbers when possible ("3x faster," "in 5 minutes," "10,000+ teams")

Avoid:

  • Jargon the audience won't recognize

  • Claims without specificity ("Best," "Leading," "Top")

  • All caps or excessive punctuation

  • Clickbait that the landing page can't deliver on

  • Shortened or nicknamed product names — use the exact product name the brief gives, in every field of every concept, unless a short form is explicitly approved

Test Hypotheses That Can Lose

When a concept ships with a test hypothesis, write one that a result can prove wrong. "This will resonate with renters" cannot lose; "beats the control on CTR among renters" can.

  • Name the metric (CTR, CVR, CPA, thumb-stop rate) and the comparison — against which control or sibling concept, in which audience

  • State the expected direction, and a magnitude when a baseline exists ("+15% CTR vs. Concept A")

  • The hypothesis should follow from the angle's motivation, so a win or a loss teaches you something about the audience, not just the asset

No AI Tells

Ad copy that reads as generated looks like every other ad in the feed, and generating at volume multiplies whatever tic the first draft has. Check the whole batch.

Never write these:

  • Contrast reveals: "It's not X, it's Y." "Not because X. Because Y." State Y directly, with the reason.

  • Negation lists: "No X, no Y, no Z." Say what does happen. One plain absence ("No card required") is fine.

  • Trailing pile-ons: a full claim, then a comma and more restating clauses. End the sentence at the claim.

  • Self-answered questions and colon reveals: "The result? 3x faster." "The best part: it learns." FAQ questions and a question in the reader's own voice are fine.

  • Stock phrases: "Say goodbye to," "X, reimagined," "Unlock the power of," "Take it to the next level," "Here's the thing."

  • Em dashes in headlines, descriptions, and primary text.

Ad-specific tells:

  • Stacked negations to fit a character limit: "No setup. No fees. No contracts." Keep the one that matters most and use the space for a fact.

  • Hook slop: a generic "POV:", "Stop scrolling," "Here's what nobody tells you about X." Earn the next second with something specific to the viewer. A POV hook is fine when the situation is hyper-specific ("POV: it's 3pm and you're on your fourth coffee").

  • CTA slop: "Get started today," "Join thousands of happy customers." Name the action and what they get.

Across a batch, vary the sentence shapes. Ten variations that all open the same way read as generated, even when each one is fine alone. For the full blacklist, use the copywriting skill's AI-tells reference.

Descriptions That Convert

Descriptions should complement headlines, not repeat them. Use descriptions to:

  • Add proof points (numbers, testimonials, awards)

  • Handle objections ("No credit card required," "Free forever for small teams")

  • Reinforce CTAs ("Start your free trial today")

  • Add urgency when genuine ("Limited to first 500 signups")


Output Formats

Standard Output

Organize by angle, with character counts:

## Angle: [Pain Point — Manual Reporting]

### Headlines (30 char max)
1. "Stop Building Reports by Hand" (29)
2. "Automate Your Weekly Reports" (28)
3. "Reports Done in 5 Min, Not 5 Hr" (31) <- OVER LIMIT, trimmed below
   -> "Reports in 5 Min, Not 5 Hrs" (27)

### Descriptions (90 char max)
1. "Marketing teams save 10+ hours/week with automated reporting. Start free." (73)
2. "Connect your data sources once. Get automated reports forever. No code required." (80)
Bulk CSV Output

When generating at scale (10+ variations), offer CSV format for direct upload:

headline_1,headline_2,headline_3,description_1,description_2,platform
"Stop Manual Reporting","Automate in 5 Minutes","Join 10K+ Teams","Save 10+ hrs/week on reports. Start free.","Connect data sources once. Reports forever.","google_ads"
Static Batch Output (Mode 3)

For scaled static batches, save to a dated folder with an index:

outputs/YYYY-MM-DD/
  INDEX.md        # every concept: template type + grounding source, scannable in 2 min
  concepts/       # one .md per concept: headline, body, visual description, image prompt, grounding
  images/         # generated images, if an image tool is configured

Per-concept format is defined in references/static-ad-templates.md. The human workflow this supports: open the folder, scan INDEX.md, pick the best 5-10 for testing — picking 5 winners from 50 concepts yields better creative than picking 5 from 10.

Creative Review Page (client / stakeholder approval)

When a person who isn't you needs to review and pick — a client, a partner, a stakeholder — produce a creative review page: a self-contained HTML artifact that presents each concept as an in-feed platform mockup (Instagram/Facebook, with a whitelist-handle toggle), breaks carousels into a labeled frame-by-frame storyboard, lets them toggle headline/copy variations, and discloses what's grounded in real assets. It's the visual upgrade to INDEX.md — a decision made off one link instead of by reading markdown. The template ships at assets/creative-review-template.html (one file, no build, hostable anywhere); populate its DATA object from your generated concepts. Full data model, grounding rules (the disclosure block is required), and delivery in references/creative-review-page.md.

Iteration Report

When iterating, include a summary:

## Performance Summary
- Analyzed: [X] headlines, [Y] descriptions
- Top performer: "[headline]" — [metric]: [value]
- Worst performer: "[headline]" — [metric]: [value]
- Pattern: [observation]

## New Creative
[organized variations]

## Recommendations
- [What to pause, what to scale, what to test next]

Batch Generation Workflow

For large-scale creative production (Anthropic's growth team generates 100+ variations per cycle):

1. Break into sub-tasks
  • Headline generation — Focused on click-through

  • Description generation — Focused on conversion

  • Primary text generation — Focused on engagement (Meta/LinkedIn)

2. Generate in waves
  • Wave 1: Core angles (3-5 angles, 5 variations each)

  • Wave 2: Extended variations on top 2 angles

  • Wave 3: Wild card angles (contrarian, emotional, specific)

3. Quality filter
  • Remove anything over character limit

  • Remove duplicates or near-duplicates

  • Flag anything that might violate platform policies

  • Ensure headline/description combinations make sense together


Common Mistakes

  • Writing headlines that only work together — RSA headlines get combined randomly

  • Ignoring character limits — Platforms truncate without warning

  • All variations sound the same — Vary angles, not just word choice

  • No CTA headlines — RSAs need action-oriented headlines to drive clicks; include at least 2-3

  • Generic descriptions — "Learn more about our solution" wastes the slot

  • Iterating without data — Gut feelings are less reliable than metrics

  • Generating without grounding — Ungrounded concepts read like every other ad in the feed; feed the skill winning ads, reviews, and comments first

  • Skipping the comments input — Ad comments hold the objections and angles customers raise themselves; those usually convert best

  • Testing too many things at once — Change one variable per test cycle

  • Retiring creative too early — Allow 1,000+ impressions before judging


Tool Integrations

For pulling performance data and managing campaigns, see the tools registry.

PlatformPull Performance DataManage CampaignsGuide
Google Adsgoogle-ads campaigns list, google-ads reports getgoogle-ads campaigns creategoogle-ads.md
Meta Adsmeta-ads insights getmeta-ads campaigns listmeta-ads.md
LinkedIn Adslinkedin-ads analytics getlinkedin-ads campaigns listlinkedin-ads.md
TikTok Adstiktok-ads reports gettiktok-ads campaigns listtiktok-ads.md
Workflow: Pull Data, Analyze, Generate
# 1. Pull recent ad performance
node tools/clis/google-ads.js reports get --type ad_performance --date-range last_30_days

# 2. Analyze output (identify top/bottom performers)
# 3. Feed winning patterns into this skill
# 4. Generate new variations
# 5. Upload to platform

Skip the plumbing. Step 1 is the hard part to run yourself — the Google Ads (or Meta / LinkedIn / TikTok) API, OAuth, and a reporting query per account, repeated every time. Magister is an autonomous marketing agent that runs on these exact skills and pulls ad performance natively: its agent reads your accounts through typed, approval-gated integrations with no setup, then applies this skill to the result. If you're wiring these pulls up by hand, it's worth a look.> Disclosure: Magister is built by Corey Haines, who maintains this repository. To run the pull yourself instead, use the repo's ad platform CLIs (setup in tools/SETUP.md), or a reporting connector such as Supermetrics or Coupler.


  • ads: For campaign strategy, targeting, budgets, and optimization

  • marketing-loops: For running static batch generation on a recurring cadence (the daily-creative-drop loop)

  • customer-research: For mining reviews and comments when building the grounded inputs corpus

  • copywriting: For landing page copy (where ad traffic lands)

  • ab-testing: For structuring creative tests with statistical rigor

  • marketing-psychology: For psychological principles behind high-performing creative

  • copy-editing: For polishing ad copy before launch

Files

references/imessage-video-ads.md

iOS-Native Reveal Video Ads (iMessage, ChatGPT, Apple Notes, AirDrop)

A family of 9:16 social-native video formats that recreate a familiar iOS surface in real time and let the brand emerge inside it. The flagship is the iMessage chat reveal — someone sends a screenshot of a result or product, a friend reacts and asks what it is, and the conversation reveals the brand, usually with a promo code. Message bubbles pop in over ~15–22 seconds with authentic send/receive sounds, then a static brand end card lands the CTA. The same architecture powers ChatGPT reveals, Apple Notes reveals, and AirDrop reveals — covered in Other iOS-Native Reveal Surfaces below.

The format works because it borrows the most-read UI on earth. A chat thread is a familiar, high-attention dramatization — it mirrors how real recommendations happen, so the viewer leans in instead of scrolling past. The CTA arrives conversationally ("use code FREEPACK") instead of as a hard sell, which keeps the ad-skip reflex from firing until the pitch has already landed. Run it only as a clearly labeled paid placement (Meta's "Sponsored" tag does the disclosure work); never seed it organically as if it were a real leaked conversation.

Credit: this reference distills the format popularized by Shiv Sakhuja and the Gooseworks team (@shivsakhuja, gooseworks-ai/gooseworks-ads-skills), who report the format performing strongly on Meta.


When to Use This Format

Good fit:

  • Reaction/discovery ads where the punchline is the recipient's curiosity ("wait, what app is that?")

  • Promo-code offers — the conversational delivery feels far less ad-like than a code on a slate

  • Products with a screenshot-able result: a number, a dashboard, a receipt, a before/after

  • UGC-style angles when you don't have UGC creators on tap

Poor fit:

  • Considered B2B purchases where a casual text exchange undercuts credibility

  • Products with nothing visual or numeric to screenshot (fix the hook first, not the format)

  • Brands whose compliance review can't approve dramatized conversations (regulated industries — check first)

Platform fit: Built for Meta Reels/Stories placements (9:16, 1080×1920) with a 1:1 center-crop variant for feed. Works on TikTok and YouTube Shorts with the same master file.


Compliance and Grounding

This is a dramatization — a scripted conversation, not a real one. That's a standard, legitimate ad device, but two rules keep it honest and on the right side of FTC guidance:

  1. Every claim in the thread must be true of the product. The race time, the savings math, the "5 minutes a day" — ground each one in a real customer result, review, or verifiable product fact, exactly as the Grounded Inputs rules in SKILL.md require. The conversation is fictional; the facts inside it can't be.

  2. Don't present the thread as a real testimonial. No real customer names, no "this is an actual text from a customer" framing, no fabricated endorsements. The format persuades through recognizability, not through pretending to be found footage.

If a claim needs a disclaimer on your landing page, it needs one on this ad too.


Concept Angles

Most iMessage ads fit one of six angles. Pick the angle before writing any copy — the most common failure mode ("script is fine but the ad feels off") is an angle mismatch, not bad lines. The strongest hooks share one of three traits: a specific number, a small act of self-trust, or a physically novel product mechanic.

AngleThe hook attachmentThe reveal
Result-as-screenshotA number that brags by itself — race time, app summary, dashboard stat"X minutes a day. that's it."
Setup flexA photo of your space — tiny apartment gym, race-kit corner, desk setup"this is the whole setup"
Cancellation momentA confirmation receipt — gym cancellation email, "subscription cancelled" page"$X/mo → $Y/mo. do the math"
Feature-as-punchlineA short clip of the product mechanic in motionThe mechanic is the brand
Friend-asks-friend (inverse)The peer opens with the wow — "how are you doing this 😭"You reply with the brand
Receipt-as-hookA mundane financial document — statement, App Store receiptA small act of self-trust

Anatomy of the Ad

0:00  Hook attachment lands (the screenshot the whole chat is about)
      ↓ short reactions, 250–450ms apart ("bro no way" / "wait is that real")
0:06  The question — "what app is that??"
      ↓ typing indicator … then the brand-name reply
0:12  The pitch, in texting voice — one or two bubbles max
0:15  The code — "use FREEPACK, first pack's free" (code renders link-underlined)
0:17  Beat of silence, then the closer — "bet" / "ok downloading"
0:18  300ms crossfade → static brand end card: logo, code, tagline (~3s)

Script rules:

  • 8–14 bubbles total. Shorter reads thin; longer loses the scroll-past viewer.

  • Write in real texting voice. Lowercase, fragments, one emoji max per message, no marketing adjectives. Read it aloud as two friends — any bubble that sounds like ad copy gets cut.

  • The brand appears once, late. The thread is about the result until someone asks. Naming the brand in bubble two kills the reveal.

  • Pacing has rhythm, not a metronome. One-word reactions fire 250–450ms apart; sentence replies get 600–900ms of air after them; leave ~600ms of silence before the final reaction so it lands.

  • Typing indicators go before sentence-length peer replies, optional before short reactions. The indicator appearing is silent (see SFX rules below).

  • The promo code goes inside a bubble, styled with iOS's link-detection underline, and on the end card. Conversational delivery first, reinforcement second.


Production Routes

Two ways to produce it, in order of control:

Route 1: Code-based pipeline (full control)

The architecture that produces a convincing result: render the chat as HTML/CSS mimicking the iMessage UI, drive the animation with a timeline script, record it headlessly with Playwright, and assemble audio + end card with ffmpeg.

  1. Script as data. Store the thread as JSON: participants (peer name, initials, avatar color), ordered messages (from, text, attachment paths, typing-indicator flags), theme, header. The script is reviewable and re-renderable without touching code.

  2. Render the chat UI in HTML/CSS. Dark theme reads most native. Two variants: full-bleed chat, or the chat inside an iPhone frame (status bar + Dynamic Island) over a brand-relevant background photo — the framed variant reads more native in-feed and is the better default.

  3. Animate with a timeline, record in ONE continuous session. All bubbles exist in the DOM but hidden (display: none — not opacity: 0, or the thread pre-allocates space and never "grows"). A driver script walks a timeline array revealing each bubble, driving the composer, and auto-scrolling. Never record scene-by-scene and concat — every page reload causes a visible micro-flicker.

  4. Type the composer for every sent bubble. The typed text must exactly equal the sent text (a mismatch reads fake on second watch). Pace ~12–15 chars/sec with ±30% per-character jitter so it feels like thumbs, not a script.

  5. Record at native output resolution. Set both the Playwright viewport and recordVideo.size to 1080×1920 — if you omit recordVideo.size, Playwright records a scaled-down video by default. Recording small and upscaling ships soft, blurry bubble text.

  6. Layer audio with ffmpeg. SFX cues computed deterministically from the same timeline that drove the recording, so sounds land exactly on bubble pops.

  7. Stitch: chat → 300ms crossfade → static end card. ffmpeg's xfade requires both inputs to match in resolution, pixel format, and frame rate — render the end card to a fixed-frame MP4 at the same specs as the chat recording before fading. Export the 9:16 master plus a 1:1 center crop.

Route 2: Code-based video (templated scale)

Once a winning script structure emerges, rebuild it as a Remotion or Hyperframes composition (see generative-tools.md) with the thread JSON as props. Then variations — new hooks, new codes, new personas — are data changes, not re-productions. Right move at the "we're testing 10 script variants a week" stage, not for the first ad.


Craft Rules (the details that sell the illusion)

These are the difference between "feels like a real chat" and "feels like a mockup":

  • The real send/receive sounds, never generic notification sounds. The iMessage feel is mostly the audio. BigSoundBank hosts recordings of Apple's message sounds under CC0: send whoosh (bigsoundbank.com/UPLOAD/mp3/1313.mp3, ~0.5s) and receive tritone (bigsoundbank.com/UPLOAD/mp3/1111.mp3 — trim to ~1.4s with a 400ms fade). Normalize loud (≈ -9 LUFS) so they cut through the music. Note the recordings being CC0 doesn't mean Apple has licensed its sound marks or UI trade dress — this is standard practice in the format, but regulated brands and risk-averse legal teams should review the iMessage mimicry as a whole; a generic chat-app skin (neutral bubbles, non-Apple sounds) is the fallback that keeps the mechanic.

  • No sound on the typing indicator. iOS is silent when someone starts typing. Play the receive sound only when the actual bubble replaces the dots. This is the single most common tell.

  • Music bed: quiet lofi/hip-hop instrumental. ~30% volume, highpass around 60Hz to clear room for the SFX, fade out ~1.5s before the code reveal so the CTA lands in relative silence.

  • Static end card — no zoom, no Ken Burns drift. The brand slate must land hard; a drifting end card reads as filler.

  • Real brand logo SVG on the end card, never CSS-styled text. Font-approximated wordmarks look amateur even when close. Pull the official SVG from the brand's press kit, Wikimedia, or brandfetch.com.

  • Hook screenshots: mimic the real app's UI, don't AI-generate it. AI-generated app UIs ship garbled chrome that reads as slop. Build a small HTML page copying the actual app's brand colors, typography, and layout conventions (the Strava-orange strip, the "Public · 2h ago" timestamp) and screenshot it. Reserve AI image generation for photographic hooks — a beach photo, a lifestyle shot, the framed variant's background.

  • Audio mixing gotcha: ffmpeg's amix divides volume by input count by default — pass normalize=0 or the whole mix comes out mysteriously quiet. Then run the mix through a limiter with the ceiling just under full scale (e.g. alimiter=limit=0.95, ≈ -0.4 dB) so it's loud without clipping.


Quality Checklist

Before shipping:

  • [ ] Every factual claim in the thread traces to a real review, result, or product fact (Grounded Inputs)

  • [ ] Script reads as real texting voice when read aloud — no marketing adjectives in bubbles

  • [ ] Brand name appears only after the peer asks

  • [ ] No sound on any typing indicator; receive SFX fires when the text bubble lands

  • [ ] SFX land exactly on bubble pops (spot-check first and last)

  • [ ] Every sent bubble had a full composer drive; typed text equals sent text

  • [ ] No micro-flicker anywhere in the chat — the only cut is chat → end card (300ms crossfade)

  • [ ] Promo code is link-underlined in its bubble and repeated on the end card

  • [ ] End card is static with the real logo SVG

  • [ ] Master is native 1080×1920; 1:1 variant is a crop, not a squeeze

  • [ ] Final bubble gets ~600–800ms of air before the crossfade

  • [ ] Audio is limited just under full scale (no clipping); music never fights the SFX


Iterating the Format

Treat the thread as the variable and the pipeline as fixed. Test in this order — hook first, everything else after:

  1. Hook attachment — the screenshot is the thumbnail and the first 2 seconds; it decides the scroll-stop

  2. Angle — result-flex vs. cancellation vs. inverse changes who the viewer identifies with

  3. Code reveal phrasing — "first pack's free with FREEPACK" vs. "FREEPACK gets you one free"

  4. Peer persona — name, avatar, and texting style shift the perceived audience

  5. Length — try a 12-bubble and an 8-bubble cut of the same script

The same architecture extends to further surfaces too — WhatsApp, Slack, a search box — same timeline-driven recording, different UI shell.


Other iOS-Native Reveal Surfaces

Everything above about production (UI mockup → timeline-driven continuous recording → deterministic SFX cues → static end card), grounding, and disclosure carries over unchanged. What changes per surface is the persuasion mechanic and a handful of craft details.

SurfacePersuasion mechanicReach for it when
iMessageA friend's recommendation — social proof through dialogueThe product is discovered through results people share ("what app is that?")
ChatGPTAn authoritative answer to the viewer's own questionThe problem is question-shaped — something people would literally type into ChatGPT
Apple NotesA private confession made public — first-person, no dialogueThe angle is transformation or realization ("things nobody told me about 45")
AirDropA spontaneous peer share — "someone nearby thought this was worth sending you right now," with a built-in accept/decline decisionThe product is something people pass to each other (a deal, a link, a find, a file) and the accept-tap can be the reveal

The strongest signal for choosing: which of these surfaces already fills your audience's day. Recommendation products want iMessage; advice-seeking problems want ChatGPT; identity/transformation stories want Notes; and anything people spontaneously pass to each other wants AirDrop.

ChatGPT Reveal

The viewer identifies with the asker. The typed question is the hook and must be the target customer's verbatim question — awkward phrasing and all ("why is my stomach so bloated all of a sudden at 47?"). The streaming answer names the problem's real mechanism, then the solution category; the brand lands in the answer's recommendation or in a typed follow-up ("what's the best one?").

Craft details:

  • Stream the answer in word chunks, not character-by-character (that's typing, not generation) and not whole paragraphs at once. A subtle tick underneath the stream and a clean stop when the response completes; no iMessage tritones anywhere.

  • Type the question like thumbs, stream the answer like a model. Two distinct rhythms — the contrast is what reads as "real ChatGPT."

  • Keep the answer scannable: short paragraphs, a bolded phrase or a short list, exactly the way ChatGPT actually formats. A wall of text breaks the illusion and loses the viewer.

  • OpenAI's interface is their trade dress — same legal-review posture as the Apple UI mimicry note above, with a generic "AI assistant" skin as the fallback.

Compliance — stricter here than anywhere else in this family. The "answer" is your ad copy wearing a lab coat: an authority costume. Every claim in it needs the same substantiation as a claim in your own voice, and the format's borrowed authority raises the bar, not lowers it. Do not put health, medical, or financial advice in a fabricated AI answer without legal review — that's the highest-risk version of this format. And never present the exchange as a real, unprompted ChatGPT output endorsing your product; it's a dramatization, same as the iMessage thread.

Apple Notes Reveal

A different genre from the chat formats: confession, not conversation. The viewer watches someone type a private note — a list of realizations, a "things I wish I knew" entry — with the keyboard visible. The note's title is the hook and does the job slide 1 does in a carousel ("Things nobody told me about 45."). The product appears as one item in the list, named the way a person would actually write it to themselves — not the way a brand would.

Craft details:

  • Audio is keyboard taps only. No chat SFX, no receive tones — a note has no other party. A quiet music bed still works underneath.

  • Type at real thumb pace with jitter, same as the iMessage composer rule. One typo-and-correction reads as human; several read as staged.

  • Get the Notes chrome right: title styled larger than body, the formatting bar above the keyboard, iOS-yellow accents. Same HTML-mimicry approach — and the same Apple trade-dress review note and generic-notes-app fallback — as everything else here.

  • Fit the note to the frame. Write short enough that the whole note fits without scrolling, or scroll once, deliberately, late.

  • First person or it doesn't work. The moment the note reads like ad copy ("[Brand] changed everything!"), the intimacy that makes the format convert is gone. The product mention should be the least enthusiastic line in the note.

The grounding rule hits differently here: the confession is a dramatization of a composite, true customer story — pull the realizations from real reviews and interviews (the Grounded Inputs corpus), and keep any numbers or outcomes to documented ones.

AirDrop Reveal

The one interaction-native format in the family: the hook is an incoming AirDrop request, and the Accept tap is the reveal. The viewer watches from the receiver's POV — a translucent AirDrop card slides up, "[Sender] would like to share [preview]," with a gray Decline and a blue Accept. The curiosity is structural ("what is this and who's sending it?") and the accept/decline choice is a built-in micro-conversion beat baked into iOS itself. Tapping Accept transfers the item — and that's where the product, the offer, or the result lands.

Craft details:

  • The preview thumbnail is the hook. It's the one image on the AirDrop card before Accept, so it has to earn the tap — same job as the iMessage screenshot attachment. Make it the result, the product money-shot, or the offer.

  • Cast the sender name like a real share. "Sarah's iPhone," "Mom," "Jordan's MacBook" reads native; a brand name in the sender slot reads like an ad — save brand-as-sender for the reveal, not the incoming card.

  • The transfer progress ring is the signature motion — don't skip it. Incoming card → a beat of hesitation ("accept?") → the Accept tap → the circular progress fills → the item lands + end card. That progress-ring beat is what makes it read as a real AirDrop and not a cut.

  • Audio is the AirDrop swoosh / received tone, not the iMessage tritones. Same CC0-Apple-sounds sourcing and the same Apple trade-dress review note as the rest of the family, with a generic "nearby share" skin as the fallback.

  • Keep it short and get the material right. The card's blur/translucency and the gray Decline / blue Accept button pair are the recognizable cues; a flat opaque sheet breaks the illusion. The whole beat is faster than the chat formats — the interaction is the ad.

  • Receiver POV by default; sender POV as the flex. Receiving reads as discovery ("someone sent me this"); sending reads as a recommendation you're making ("had to AirDrop this to the group") — use sender POV when the angle is advocacy rather than discovery.

Grounding is the same family rule: it's a dramatization of a share, not a claim that a real person actually AirDropped your product. Every claim on the transferred item is substantiated per the Grounded Inputs rules, and the exchange is never presented as a real, unprompted endorsement.

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Needs Node.js

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
Corey Haines
Publisher
Corey Haines (Community)
Source
coreyhaines31/marketingskills · skills/ad-creative · commit 96798cf
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Corey Haines.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download ad-creative.zip