Ecommerce creative system skill

Build product-forward creative patterns reusable across ad platforms — product hero shots, lifestyle imagery, comparison/demo formats, and catalog-scale creative systems.

by gmmh1·MIT license·★ 0 Stars on the repo·GitHub ↗

Use now

Inside this skill

SKILL.md · the author's own words
# Ecommerce Creative System

> **Currency & scope note (last reviewed 2026-07-19):** Platform mechanics referenced here (character limits, campaign-type names, feature…

## Purpose
Provide reusable product-forward creative patterns — the shot types, demonstration formats, and catalog-scale systems that work across Goog…

## Trigger Conditions
- "Build ecommerce ad creative for my products"
- "What product photography do I need for ads"
- "Creative system for my whole catalog"
- "How should I show this product across different platforms"

## Required Inputs
- Product catalog size and category (single hero product vs. large multi-SKU catalog changes the creative approach significantly)
- Target platforms (affects format/style requirements)

Word-for-word excerpt, not a result. Read the full SKILL.md ↓

Files of Ecommerce creative system

gmmh1/main1 file shown
SKILL.md
Show the full text69 lines

Ecommerce Creative System

Currency & scope note (last reviewed 2026-07-19): Platform mechanics referenced here (character limits, campaign-type names, feature availability, thresholds, benchmark figures, policy specifics) reflect general practice as of the review date above and are not guaranteed current — ad platforms change quickly. Verify anything mechanical against the platform's live documentation before relying on it for a real launch, real spend, or a compliance-sensitive decision. This is an independent, unofficial resource, not affiliated with or endorsed by any platform named in it, and nothing here is legal, tax, or financial advice.

Purpose

Provide reusable product-forward creative patterns — the shot types, demonstration formats, and catalog-scale systems that work across Google Shopping/PMax, Meta catalog ads, and TikTok Shop — so ecommerce businesses build one coherent creative system rather than reinventing product presentation per platform.

Trigger Conditions

  • "Build ecommerce ad creative for my products"
  • "What product photography do I need for ads"
  • "Creative system for my whole catalog"
  • "How should I show this product across different platforms"

Required Inputs

  • Product catalog size and category (single hero product vs. large multi-SKU catalog changes the creative approach significantly)
  • Target platforms (affects format/style requirements)
  • Existing product photography/video assets
  • Price point and consideration level (impulse-buy low-consideration items need different creative than higher-consideration purchases)

Core Capabilities

Core Shot Types
  • Hero/clean product shot: the foundational asset (white/neutral background, accurate color/detail) required for feed listings, Shopping/PMax feed images, and catalog-driven dynamic ads — this is infrastructure, not optional
  • Lifestyle/in-context shot: product in real use/environment, builds desire and demonstrates scale/application — stronger for top-funnel and native-feed placements (Meta Feed, Instagram) than for pure feed/Shopping listings
  • Comparison/demonstration: before/after, size comparison, feature callouts — effective for considered purchases where the buyer needs more information before converting
  • UGC-style/authentic use: real (or convincingly native-feeling) usage content, the strongest-performing pattern for TikTok and increasingly competitive on Meta — coordinate with tiktok-ads-creative-strategy and meta-ads-video-reels for platform execution
Catalog-Scale Creative Systems
  • For large catalogs, establishing a repeatable shot template/system (consistent background, lighting, framing) that scales across hundreds/thousands of SKUs efficiently, rather than bespoke creative per product
  • Prioritizing bespoke, higher-production creative for bestsellers/high-margin products and using the systematized template for the long tail — matching production investment to revenue concentration
  • Custom labels/product segmentation (coordinate with google-ads-shopping-feed/meta-ads-catalog-feed) determining which products get premium creative treatment vs. template treatment
Format Translation Across Platforms
  • The same product needs different creative treatment per platform: clean hero shot for Shopping/PMax feed, native UGC-style video for TikTok, a mix of lifestyle and hero content for Meta feed/Stories/Reels
  • Building each product's asset library once with platform-specific derivatives planned from the start, rather than treating each platform's creative as a separate production effort
Demonstration & Proof Patterns
  • Size/scale reference (showing the product against a recognizable object or in use) to reduce purchase hesitation from uncertainty about actual dimensions — a common ecommerce conversion blocker
  • Ingredient/material/feature close-ups for categories where quality perception depends on visible detail
  • Social proof integration (review counts, ratings) overlaid on creative where platform format allows

Workflow

  1. Assess catalog size/category and existing asset inventory.
  2. Establish the core hero-shot standard as baseline infrastructure for feed/Shopping use.
  3. Prioritize bestsellers/high-margin products for bespoke lifestyle/demonstration/UGC-style creative; apply a systematized template to the long tail.
  4. Plan platform-specific derivatives from each product's core asset set rather than separate per-platform production efforts.
  5. Route platform-native execution to the relevant platform's creative skill (tiktok-ads-creative-strategy, meta-ads-creative-strategy, google-ads-shopping-feed image requirements).

Outputs

  • Core shot-type recommendation per product/catalog tier
  • Catalog-scale creative system/template recommendation
  • Platform-specific derivative plan per asset
  • Production investment prioritization by revenue concentration

Rules

  • Never let hero/clean product shots be an afterthought — they're required infrastructure for Shopping/PMax/catalog ads, not just one creative option among several.

  • Match production investment to revenue concentration — bespoke creative for bestsellers, systematized templates for the long tail, not uniform treatment across a large catalog.

  • Plan platform-specific derivatives from one core asset set rather than treating each platform as a separate production effort.

  • Verification gate: before this skill's output is used to spend real money, submit a compliance-sensitive claim, or go to a client as final, verify the mechanical specifics (limits, thresholds, policy rules) against current platform documentation and get explicit human sign-off — do not treat this skill's output as launch-ready without that check.

google-ads-shopping-feed, meta-ads-catalog-feed (feed image requirements), tiktok-ads-creative-strategy (UGC execution), meta-ads-video-reels (lifestyle/demo video execution), ai-creative-generation (scaling shot variants).

1---
2name: ecommerce-creative-system
3description: "Build product-forward creative patterns reusable across ad platforms — product hero shots, lifestyle imagery, comparison/demo formats, and catalog-scale creative systems. Triggers on 'ecommerce ad creative', 'product photography for ads', 'creative system for my catalog', or 'how should I show this product across platforms'. Cross-platform ecommerce creative patterns feeding platform-specific execution."
4---
5 
6# Ecommerce Creative System
7 
8> **Currency & scope note (last reviewed 2026-07-19):** Platform mechanics referenced here (character limits, campaign-type names, feature availability, thresholds, benchmark figures, policy specifics) reflect general practice as of the review date above and are **not guaranteed current** — ad platforms change quickly. Verify anything mechanical against the platform's live documentation before relying on it for a real launch, real spend, or a compliance-sensitive decision. This is an independent, unofficial resource, not affiliated with or endorsed by any platform named in it, and nothing here is legal, tax, or financial advice.
9 
10## Purpose
11Provide reusable product-forward creative patterns — the shot types, demonstration formats, and catalog-scale systems that work across Google Shopping/PMax, Meta catalog ads, and TikTok Shop — so ecommerce businesses build one coherent creative system rather than reinventing product presentation per platform.
12 
13## Trigger Conditions
14- "Build ecommerce ad creative for my products"
15- "What product photography do I need for ads"
16- "Creative system for my whole catalog"
17- "How should I show this product across different platforms"
18 
19## Required Inputs
20- Product catalog size and category (single hero product vs. large multi-SKU catalog changes the creative approach significantly)
21- Target platforms (affects format/style requirements)
22- Existing product photography/video assets
23- Price point and consideration level (impulse-buy low-consideration items need different creative than higher-consideration purchases)
24 
25## Core Capabilities
26 
27### Core Shot Types
28- **Hero/clean product shot**: the foundational asset (white/neutral background, accurate color/detail) required for feed listings, Shopping/PMax feed images, and catalog-driven dynamic ads — this is infrastructure, not optional
29- **Lifestyle/in-context shot**: product in real use/environment, builds desire and demonstrates scale/application — stronger for top-funnel and native-feed placements (Meta Feed, Instagram) than for pure feed/Shopping listings
30- **Comparison/demonstration**: before/after, size comparison, feature callouts — effective for considered purchases where the buyer needs more information before converting
31- **UGC-style/authentic use**: real (or convincingly native-feeling) usage content, the strongest-performing pattern for TikTok and increasingly competitive on Meta — coordinate with `tiktok-ads-creative-strategy` and `meta-ads-video-reels` for platform execution
32 
33### Catalog-Scale Creative Systems
34- For large catalogs, establishing a repeatable shot template/system (consistent background, lighting, framing) that scales across hundreds/thousands of SKUs efficiently, rather than bespoke creative per product
35- Prioritizing bespoke, higher-production creative for bestsellers/high-margin products and using the systematized template for the long tail — matching production investment to revenue concentration
36- Custom labels/product segmentation (coordinate with `google-ads-shopping-feed`/`meta-ads-catalog-feed`) determining which products get premium creative treatment vs. template treatment
37 
38### Format Translation Across Platforms
39- The same product needs different creative treatment per platform: clean hero shot for Shopping/PMax feed, native UGC-style video for TikTok, a mix of lifestyle and hero content for Meta feed/Stories/Reels
40- Building each product's asset library once with platform-specific derivatives planned from the start, rather than treating each platform's creative as a separate production effort
41 
42### Demonstration & Proof Patterns
43- Size/scale reference (showing the product against a recognizable object or in use) to reduce purchase hesitation from uncertainty about actual dimensions — a common ecommerce conversion blocker
44- Ingredient/material/feature close-ups for categories where quality perception depends on visible detail
45- Social proof integration (review counts, ratings) overlaid on creative where platform format allows
46 
47## Workflow
481. Assess catalog size/category and existing asset inventory.
492. Establish the core hero-shot standard as baseline infrastructure for feed/Shopping use.
503. Prioritize bestsellers/high-margin products for bespoke lifestyle/demonstration/UGC-style creative; apply a systematized template to the long tail.
514. Plan platform-specific derivatives from each product's core asset set rather than separate per-platform production efforts.
525. Route platform-native execution to the relevant platform's creative skill (`tiktok-ads-creative-strategy`, `meta-ads-creative-strategy`, `google-ads-shopping-feed` image requirements).
53 
54## Outputs
55- Core shot-type recommendation per product/catalog tier
56- Catalog-scale creative system/template recommendation
57- Platform-specific derivative plan per asset
58- Production investment prioritization by revenue concentration
59 
60## Rules
61- Never let hero/clean product shots be an afterthought — they're required infrastructure for Shopping/PMax/catalog ads, not just one creative option among several.
62- Match production investment to revenue concentration — bespoke creative for bestsellers, systematized templates for the long tail, not uniform treatment across a large catalog.
63- Plan platform-specific derivatives from one core asset set rather than treating each platform as a separate production effort.
64 
65- **Verification gate:** before this skill's output is used to spend real money, submit a compliance-sensitive claim, or go to a client as final, verify the mechanical specifics (limits, thresholds, policy rules) against current platform documentation and get explicit human sign-off — do not treat this skill's output as launch-ready without that check.
66 
67## Related Skills
68`google-ads-shopping-feed`, `meta-ads-catalog-feed` (feed image requirements), `tiktok-ads-creative-strategy` (UGC execution), `meta-ads-video-reels` (lifestyle/demo video execution), `ai-creative-generation` (scaling shot variants).
69 

Discussion

Alternatives

Cloudflare BasinBuild and troubleshoot Cloudflare Basin analytics workflows with Basin Pipelines, Basin Catalog, and Basin SQL. Use for streaming data into R2 Iceberg tables, managing catalogs, or querying those tables; also use for requests using the former Data Platform, Pipelines, R2 Data Catalog, or R2 SQL names.Sales & ecommerce · Apache-2.0ShopifyBuild anything on Shopify. One skill covering every Shopify developer surface: Use Shopify CLI, Admin API, ShopifyQL, Storefront GraphQL API, Partner API, Customer Account API, Payments Apps API, Shopify Functions, Polaris App Home, Polaris Admin Extensions, Polaris Checkout Extensions, Polaris Customer Account Extensions, POS UI, Hydrogen, Liquid, Custom Data, Shopify App Pricing, App Store Review, Developer Onboarding, Merchant Onboarding. Use it for any Shopify API, extension, theme, storefront, function, or CLI task — writing or explaining code, looking up operations, fields, components and valid values, validating generated code, and choosing which surface a request belongs to. Also use it when someone asks to make, build, open, or set up a store or shop that sells something, and when a prompt mentions or asks for any of: metafields or metaobjects, make me a store that sells pet supplies, mock.shop reference stores, build a storefront without an account — even without saying Shopify.Sales & ecommerce · MITShopifyBuild and customize Shopify stores — themes with Liquid, Storefront API, custom apps, and headless commerce with Hydrogen. Use when someone asks to build a Shopify store", "Shopify theme", "Liquid templates", "Shopify API", Shopify app", "headless Shopify", "Hydrogen storefront", "customize Shopify", Shopify product management", or "e-commerce with Shopify". Covers Liquid templating, theme development, Storefront/Admin APIs, custom apps, checkout extensions, and Hydrogen (React-based headless).Sales & ecommerce · Apache-2.0Shopify themes, apps & checkoutUse when building or customizing a Shopify store across its three code surfaces — themes (Liquid, Online Store 2.0 sections, blocks and JSON templates), apps (Remix with the versioned GraphQL Admin API and its query-cost model), and checkout (UI extensions, Functions, Web Pixels), plus the CLI flow and checkout-extensibility migration. NOT WooCommerce or PHP stores (that is `wordpress`), NOT the React layer of a headless storefront (that is `nextjs`), NOT non-Shopify payment integrations (that is `stripe`).Sales & ecommerce · MIT