← ClaudeAtlas

product-photo-consistencylisted

Keep a whole catalogue of product images visually consistent using brand assets, verbatim look clauses and locked seeds. Use whenever the user has many products to shoot, a catalogue that looks inconsistent, or wants images that read as one brand rather than many attempts.
apimageorg/apimage-skills · ★ 0 · AI & Automation · score 72
Install: claude install-skill apimageorg/apimage-skills
# Catalogue Consistency A category page is judged as a grid, not as individual images. Forty technically-good photos with forty different lighting setups, distances and grades looks amateur — and customers read that as a signal about the products. Consistency is cheap to achieve and it's mostly a matter of deciding things once and then not re-deciding them. ## The four things to fix | Element | How | Cost | |---|---|---| | **Product references** | `create_brand_asset(type="product")` | free | | **Backgrounds and scenes** | `create_brand_asset(type="background")` | free | | **The look** — light, grade, lens | `create_brand_asset(type="preset")` | free | | **The rendering character** | A locked `seed` per family | free | Every one of them is free. The only cost is the discipline of saving things at the moment you approve them rather than reconstructing them later. ## Seeds give a look, assets give a subject The distinction people get wrong, and it matters here as much as in video. ``` seed=8812 "product A on marble, soft light" → consistent treatment seed=8812 "product B on marble, soft light" → same treatment, product B ``` A locked seed produces a consistent *visual treatment* — grade, light quality, rendering character. It does **not** guarantee the product is accurate. That's what `reference_images` and product brand assets do. You want both. See `seed-locked-iteration` and `product-photo-from-reference`. ## Write the look clause once, copy it verbatim The