The default, which covers most cases: if the client approves 30 of 50 ads, launch those 30. Don't
rework the other 20. The next creative refresh starts fresh from Run 2 with everything you learned this round.
? When parking is worth it
- The idea landed but the image didn't. The client liked the angle, but the photo or render missed.
- One placement version is wrong. For example, the Stories crop cuts off the logo while the Feed version was approved.
- One word, price or logo is wrong. The rest of the ad is fine.
- You were promised a set number of ads. Rejections pushed you under a count you committed to.
If none of these apply, let the ad go. A new idea at the next refresh usually does better than a repaired one.
1 Park it now 2 minutes
Parking means saving what the client said while it's fresh, so the next refresh can use it. No new ads are made yet.
- Save the client's review. If you sent the ads with Client Package,
the finalized review already lists each ad as Approved or Rejected with a reason. Save that summary email
(or the Netlify responses page) in the client's Claude Project.
- Keep the Creative Package file where it is.
<Client>-Creative-Package.md in
brand/ is what the replace round works from. Don't hand-edit it.
- File the rejected images as benchmarks. Copy them into
brand/benchmarks/rejected/
and ads the client loved into brand/benchmarks/approved/. Run 3 checks every future render
against these folders. This helps even if you never run the replace round.
2 At the refresh: pick one path
| Path | Use when | What you run |
|---|
| Fresh round (usual) | Most rejections were about the idea, or it's been a while | Run 2 → Run 3 as normal. Your benchmarks and saved review notes shape the new slate. |
| Replace round | You want to keep this round's copy or artwork and fix only specific ads | /creative-strategy replace → Run 3 on the round-2 package |
↻ Running the replace round
- In the client's Claude Project, attach
<Client>-Creative-Package.md and type
/creative-strategy replace.
- It asks which ads were rejected and what the client said. Answer in plain words.
A filename, the headline on the ad, "the two testimonial ones" or "the Stories version of the door ad" all work.
You don't need ID numbers, and pasting the saved review summary is fine too.
Confirm the table. It lists each rejected ad, what it matched it to, and what it plans to do:
Replace: the idea was wrong, so it writes a new one.
Revise: the idea was right but the render was weak, so it rebuilds the ad.
Correct: one word, price, logo or crop was wrong, so it fixes only that.
A fix to one placement touches only that version. Approved ads are listed as preserved and never regenerated.
Change any row, then say go.
- Take the round-2 package to Codex and run
$meta-ad-creative-generator. It builds only
the rows that changed and saves them as new revisions. Approved originals stay byte-for-byte the same, checked by hash.
- Send the new ads for review with Client Package as a new package, so this
round's responses stay separate from the first round's.
! Watch out for
- Hand-editing the image or the package. The approved originals and copy stop being traceable. Use the replace round or build fresh.
- Calling a message change a "correct". If the words say something different, it's a replace. A correct is only for a wrong detail.
- Replacing everything. If most ads need replacing, a fresh round is faster and usually better.
← Back to the Creative Skill Package