Make Product Photos
Use when the marketer says: studio photos of my product without a shoot, product photos...
Install
npx skills add gooseworks-ai/goose-skills --skill make-product-photos -g -a claude-code -y- Repository
- gooseworks-ai/goose-skills1.3k
- Category
- Marketing
- Updated
- 9d ago
- License
- MIT
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Use when the marketer says: studio photos of my product without a shoot, product photos for my store page, packshots on white, lifestyle or on-model shots, photos for the new colourway, fresh product imagery for ads, photos for our launch page, our packaging changed, redo the photos, I have no photographer. Delivers store-ready product photos generated from the brand's real product photos: a shot list built from the page slots (hero, alt angle, scale, detail, in use, lifestyle, on-model), only real photos of this product as references, matched to the brand's photography, every shot checked against the real product for shape, parts, logo, text, colour, finish, scale and honest representation, with a keep / maybe / reject verdict and a page order. The human picks the keepers. Never uploads to a store, never shows a size, part, feature or result the product lacks. Not for ads with text, infographics or screenshots, make-static-ads; not for marketplace listing sets (not covered yet).
make-product-photos
The engine composes, generates, judges and retries. This playbook is the e-commerce creative director around it: it decides which pictures the page needs, curates which real photos the engine sees, turns each shot into a precise prompt, holds every scene to what the product physically is, checks each output against the real product, and keeps the catalogue looking like one shoot.
What you get
- A shot list from the surface (store page, ads, social, email, launch page), each shot with its slot, composition, light, scene and ratio, agreed before anything is made.
- A house-style card derived from the brand's existing photos (when they can be seen), confirmed once and saved.
- The photo set as the page it fills: each photo with its use, the engine's status and score, this playbook's verdict (keep / maybe / reject + named reason), and who checked it (by eye, or engine only with a checklist for you).
- "What we could not make and why", and the credits actually charged.
Before you start
Hard rules:
