One Consistent Look Across a Catalogue
Lock ratio, margin, shadow and background before a bulk run, then audit the output as a grid so inconsistency is actually visible.
What it is for
A working order for bulk product image processing: define the recipe against your worst items, lock the four settings that make a catalogue look like a set, then audit the output by shape group and as a grid. It prevents the two classic outcomes of a big batch - a folder where no two images match, and a re-run that breaks the files that were already correct.
The skill
Use when one look has to cover a whole catalogue. Build the recipe on the hardest item, never the easiest. Pick the widest product, the tallest one, one with a hole through it, and a pale one that fights a white background. A recipe that survives those four survives the other two hundred. Fix these before you process anything: - One canvas ratio per destination, written down. - One margin rule, expressed as "the product fills about this much of the frame", so a ring and a wardrobe end up looking like a set. - One shadow direction and strength for every item. - One background, defined by an exact colour value, not by eye. Run the batch, then audit like this: - Sort the output by product shape, not by filename, and open one from each shape group. - Look for the three failures batches really produce: a product cropped by the canvas, a missing shadow where the cutout failed, and one image at a different scale from its neighbours. - Put ten finished images in a grid and look at the grid, not the files. Inconsistency is only visible next to its siblings. Never overwrite originals. Export to a new folder, leave the source untouched, and keep filenames tied to the product code so a bad image can be traced back to the product in one step. Fix what the batch got wrong by hand and re-export those files alone. Re-running the whole batch to repair four images is how you lose the twelve that were already right.
How to install it
1. Open the tool and start a new conversation, project or template. 2. Paste the text below wherever the tool keeps standing instructions — usually called system prompt, instructions, or persona. 3. Save it so it applies to every run rather than a single message.