product-visuals
Skill5 starsChanged 36 days agoMITView on GitHub
Use when planning, briefing, reviewing, or selecting product photos, product video, hero images, or ad creative for an online store — e.g. "write a shot list for our photographer", "do we need video for this product", "how should the model pose", "which product image should we use", "brief for the product shoot", "why does this image underperform".
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Innei/SKILLtheir own version, first seen Apr 20, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Innei/SKILL★ 92same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository18 other files it gives its agents.
- checkout-uxSkill
- digital-product-pricingSkill
- discountsSkill
- event-pricingSkill
- increase-aovSkill
- increase-conversionSkill
- increase-repeat-purchasesSkill
- post-purchaseSkill
- price-researchSkill
- pricingSkill
- product-copySkill
- product-pageSkill
- promotionsSkill
- raise-pricesSkill
- referralsSkill
- reviewsSkill
- store-auditSkill
- subscription-pricingSkill
The file
Files
Product visuals
Produce a photo/video brief in which each shot is tied to a finding — most with a measured effect, a few marked † as practitioner tips. Format, gaze, the viewer's sense of touching the product, and composition (shine, spacing, side, props) move sales and willingness to pay more than lighting taste does.
When to use
- Writing a shot list or creative brief; choosing video vs stills or between candidate images
- Reviewing why a product image or ad creative underperforms
When not to use
- Page layout, CTAs, variants, price position →
product-page - Description text →
product-copy
Inputs
Collect, or state your assumption:
- The product; can it be picked up and held? Is it premium?
- One main function (energy drink) or many?
- Worn, and by whom (womenswear vs menswear)?
- Where the visuals run (product page, ads, social); audience reading direction
Classify the product first. Hedonic = bought for enjoyment, pleasure, or the experience (chocolate, fashion, decor, travel, spa, perfume). Utilitarian = bought to do a job, judged on function and value (detergent, appliances, insect repellent, tools, accounting software). If it's mixed, decide by what the buyer is optimizing for at the moment of purchase.
Procedure
- Format. Hedonic → video, GIF, or slideshow is required (willingness to pay 79% higher). Utilitarian → stills are enough. Premium hedonic → add a slow-motion action shot (+22% sales) †. Video should feel personal and human, not corporate. †
- Gaze. Hedonic → model looks away from the camera (sun hat: +30% sales). Informational or negative-emotion messages → model looks at the camera.
- Touch. A first-person hand touching, holding, or using the product (+16% purchase likelihood).
- Side. Graspable product toward the right of the frame, angled for a right hand. If it can't be held, add a graspable object beside it (handedness doesn't change with reading direction — don't flip this). Future-oriented products right, vintage left; flip that for right-to-left readers.
- Shine. Light or polish for a visible reflection; a digital reflection is fine only if it stays representative of the real finish (a matte product shown glossy misleads buyers). Never brief "no reflections" (+23% attractiveness, +32% purchase likelihood).
- Spacing. Clear empty space between products in multi-product shots and grids (liking +11.4%, sales nearly doubled). In ads, wide margins with related products clustered in the center. †
- Multiples. Product bought for one specific function (an energy drink for energy, a stain remover) → several copies together (+10.7% perceived effectiveness) †. Not a rule for treats or decor.
- Props. Complementary items around the focal product, varied in shape and color; the props' own sales are unaffected.
- Context. Womenswear → a fitting setting, not white background. Menswear → irrelevant.
- Saturation. High to look bigger, low to look smaller. Pretest candidates with a poll where cheap. †
Output
| # | Shot | Direction | Rule | Effect |
| 1 | Hero video, 8–12 s | Truffle broken in slow motion | Hedonic → video; premium → slow-mo | WTP +79% |
| 2 | Hand shot | First-person hand lifting a truffle, box on the right | Touch; graspable right | +16% |
Then list what not to do for this product (e.g. no direct gaze, no matte finish).
Common mistakes
- Making video "secondary" for a hedonic product — it is the highest-effect item.
- Briefing "avoid reflections" — shine raises attractiveness and purchase intent.
- Centering a graspable product — it belongs toward the right.
- A single can for a single-function product — show several.
Quick reference
| Element | Rule |
| Format | Hedonic → video; utilitarian → stills |
| Premium hedonic | Slow-motion action shot |
| Gaze | Away for hedonic; at camera for info or negative emotion |
| Hand | First-person hand touching |
| Position | Graspable product right (never flipped); future-right/past-left flips for RTL |
| Finish | Visible shine |
| Layout | Space apart; wide ad margins |
| Single-function | Multiple copies |
| Props | Complementary, varied |
| Womenswear | Contextual background |
| Size cue | High saturation = bigger |
† No primary citation on file for this rule — a practitioner tip, not a measured finding.
Evidence and effect sizes: see reference.md.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

