Skip to content
Primores AI wiki

Ad-Template Foundry — Deconstruct Ads into a Reusable Template Library

Ad-Template Foundry

TL;DR: Submit a static ad (yours or a competitor’s) and the foundry abstracts it into a brand-agnostic template filed in a growing catalog: a layout skeleton, named swappable slots, base-image generation rules, a “when to pick” note, and a status. For layout-style statics it also emits a working parametrized compositor (Python/PIL) that renders the template across aspect ratios. The deliverable is the reusable template + the library, not one-off creative — and it’s dedupe-aware: similar ads compress into one parametrized template (one run folded 10 source ads into 4 templates), never one entry per ad.

What It Does

The foundry is the build half of marketing/static-ad-template-system. It runs the deconstruction front-end from seo/ai-template-casting-workflow and the structural-not-surface discipline, then persists the result:

  • Abstracts to structure, not skin. Captures composition, focal hierarchy, slot structure, and gen-rules — strips the source brand entirely (glossary/creative-formula-vs-creative-skin).
  • Catalogues it. Adds a brand-neutral entry to catalog.md with slots, when-to-pick, gen-rules, and a status (experimental → live → retired).
  • Emits a compositor for layout-style templates: a drawing runtime + a content-JSON contract so the layout renders deterministically (not a fresh prompt each time).
  • Dedupes. Recognizes when a new ad is a re-skin of an existing template and folds it in as a parameterization rather than forking a near-duplicate entry.

What Makes It Different

  • It’s distinct from ad-alchemy. ad-alchemy casts one competitor ad onto your product as one-shot image-gen prompts + copy. The foundry persists the abstract template into a reusable, catalogued, status-tracked library — the deliverable is the library, not a single creative.
  • Compress, don’t fork. The dedupe discipline is the whole point: a per-ad library is just a screenshot folder.
  • Static ads only (video out of scope for now).

When to Use

  • “Templatize this ad” / “turn this ad into a template”
  • “Add this to our template library” / “build a catalog of ad formats”
  • Reverse-engineering an ad’s structure for reuse (not creative for one specific product)

Chains With

Feeds tools/ad-template-apply (which fills the templates this builds) and the template-system methodology. Templates can graduate into the durable wiki only once they reach status: live from a real results read.

Key Takeaways

  • Input a static ad → output a brand-agnostic, catalogued template (+ a compositor for layout-style statics).
  • Dedupe-aware: similar ads compress into one parametrized template (10 ads → 4 templates in the first run).
  • The deliverable is the reusable library, which is what separates it from ad-alchemy’s one-shot casting.
  • Templates ship experimental; promotion to live is gated on real performance.

Sources

  • Primores internal skill (18-ad-template-foundry: SKILL.md, catalog format, compositor toolkit). Built June 2026; current catalog templates status: experimental.

By Andrej Ruckij