nexu-io/open-design / skills/ecommerce-image-workflow
ecommerce-image-workflow
VerifiedReference-product ecommerce image workflow for generating a compact set of product-faithful main, feature, and lifestyle images from real product reference photos. V1 requires uploaded product imagery and intentionally defers brief-only concept generation and platform-specific batch exports.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 9.5 KB |
| example.html | other | 11.7 KB |
| references/checklist.md | markdown | 3.1 KB |
references/checklist.md
View on GitHub# Ecommerce Image Workflow Checklist
Run this before handoff. P0 items must pass for the output to be usable.
## P0 - must pass
- [ ] **Reference image exists.** The workflow used at least one real uploaded
product image. If no image was available, the run stopped and asked the user
to upload one.
- [ ] **Reference-product mode only.** The output is not a brief-only concept
product. Any brief-only request was deferred.
- [ ] **One product.** The run targets one product, not a SKU family or mixed catalog.
- [ ] **Product fidelity lock appears in every prompt.** Each generated slot
prompt preserves shape, silhouette, color, material, logo/label placement,
visible construction details, and proportions.
- [ ] **No redesign.** Prompts do not add, remove, relocate, recolor, or restyle
product features. Product edit requests that change the product itself are
out of scope for this V1 workflow and should be deferred to a follow-up
workflow.
- [ ] **Three-slot scope.** The set is limited to main, feature, and lifestyle
unless the user explicitly requested fewer.
- [ ] **Media dispatcher only.** Generation used
`"$OD_NODE_BIN" "$OD_BIN" media generate`; no provider API or custom model
command was called directly.
- [ ] **Reference image is passed to generation.** Each media command includes
`--image <project-relative product reference image>` when the model supports
reference images. If not supported, the workflow stops instead of pretending
product fidelity is guaranteed.
- [ ] **No fabricated claims.** The feature image does not invent
certifications, measurements, materials, ingredients, performance numbers,
awards, or compliance promises.
- [ ] **No tiny rendered text dependency.** Prompts avoid relying on small
in-image text for selling points; they leave clean label space when copy will
be added later.
- [ ] **Manifest exists.** `image-manifest.json` records workflow name, mode,
product name/label, reference images, slot ids, output filenames, aspects,
and prompt summaries.
- [ ] **Gallery exists.** `ecommerce-gallery.html` shows the reference image
first and the generated main, feature, and lifestyle slots.
## P1 - should pass
- [ ] **Slot roles are visually distinct.** Main is a clean packshot, feature is
detail/benefit focused, lifestyle is contextual.
- [ ] **Backgrounds fit ecommerce use.** Main image uses white/off-white/light
grey; feature and lifestyle avoid noisy backgrounds that hide product details.
- [ ] **Scale is plausible.** Product size and proportions remain credible across all slots.
- [ ] **Human interaction is controlled.** Hands/models do not hide the product
or alter its construction.
- [ ] **File names are predictable.** Outputs use `<product-slug>-main.png`,
`<product-slug>-feature.png`, and `<product-slug>-lifestyle.png` or similarly
readable names.
## P2 - nice to have
- [ ] **Marketplace note included.** Handoff states that platform-specific
crop/background/text rules remain a follow-up or human review step.
- [ ] **Variation path is clear.** Handoff suggests the next useful variant,
such as a different lifestyle scene or a second feature focus.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |