← ClaudeAtlas

media-forgemf-marketplace-cardslisted

Use when the user needs marketplace listing images — Amazon-style main image, secondary product images, A+ content modules. Covers the four scopes and how to chain secondaries off an approved main.
produtoramaxvision/maxvision-utilities · ★ 0 · AI & Automation · score 59
Install: claude install-skill produtoramaxvision/maxvision-utilities
# media-forge:mf-marketplace-cards Listing imagery has rules that ordinary product photography does not — a main image with a white background and no props, secondaries that answer objections in order, A+ modules that are laid out rather than shot. Higgsfield keeps the marketplace references and prompt templates on its side and returns `nano_banana_2` prompts; this covers choosing the scope and chaining the set. ## Intent A listing is a sequence, not a gallery. The main image earns the click, the secondaries answer the objections that stop the purchase, the A+ modules close the ones that survive. Generating them independently produces a set that looks assembled by different people — which is exactly how it reads to a buyer. That is why `mainJobId` exists: approve the main image, then chain the rest off it so the product is the same object at the same angle throughout. ## The four scopes | Scope | Produces | Use | |---|---|---| | `main` | The primary listing image | Start here, always | | `product-images` | Secondaries — angles, details, in-use | After the main is approved | | `aplus` | A+ / enhanced-content modules | Brand-registered listings | | `full-set` | All three at once | Only when the product is well understood | `full-set` is convenient and worse: it decides the main image and everything downstream in one pass, so a main you would have rejected propagates through the set. Prefer `main` → approve → chain. ## Chaining ``` 1. media_higgsfield_marketplace_cards