Agent skill · Workflow & Productivity

ecommerce-image-workflow

Reference-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.

nexu95,528★ · +2,037/wk · 5 repos on radarProfile →
claude-codecodexcursorApache-2.0
Install
npx skills add nexu-io/open-design --skill ecommerce-image-workflow --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 3
SKILL.md size: 9 KB
Bundled scripts: none
Path: skills/ecommerce-image-workflow/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 83,577 · +1,339 this week
Language: TypeScript
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Ecommerce Image Workflow Create a compact ecommerce image set from real product reference imagery. This V1 skill is intentionally narrow: it supports **reference-product mode only**. If the user only describes a product and does not provide a product photo, ask for one and stop. Do not create a brief-only concept product in this version. ## Resource map ```text ecommerce-image-workflow/ |-- SKILL.md |-- example.html `-- references/ `-- checklist.md ``` ## What this skill produces By default, generate three ecommerce-ready image assets for one product: 1. **Main image** - clean product-first packshot on white or soft neutral background. 2. **Feature image** - one selling point shown clearly with controlled callout space, without relying on tiny unreadable in-image text. 3. **Lifestyle image** - product shown in a plausible use context while keeping the product faithful to the reference. Also create: - `image-manifest.json` describing reference inputs, slots, prompts, outputs, aspect ratios, and fidelity notes. - `ecommerce-gallery.html` as a small preview gallery linking the generated files and summarizing the image roles. ## Input contract Required: - At least one uploaded produc

What's inside
Steps it walks through
  1. Resource map
  2. What this skill produces
  3. Input contract
  4. Workflow
  5. Step 0 - Confirm reference-product mode
  6. Step 1 - Extract product identity anchors
  7. Step 2 - Build a three-slot shot plan
  8. Step 3 - Compose prompts with a fidelity lock
  9. Step 4 - Dispatch through the media contract
  10. Step 5 - Write image-manifest.json
  11. Step 6 - Write ecommerce-gallery.html
  12. Step 7 - Hand off
  13. Hard rules
Ships with 2 files
  • example.html
  • references/checklist.md
Commands it runs
POSIX bash. Do not call provider APIs directly.
if [ "$ec" -ne 0 ]; then echo "$out" >&2; exit "$ec"; fi
python3 -c "import sys,json; d=json.load(sys.stdin); print(d.get('taskId',''))" 2>/dev/null)
python3 -c "import sys,json; d=json.load(sys.stdin); print(d.get('nextSince',0))" 2>/dev/null)
while [ -n "$task_id" ]; do
if [ "$ec" -eq 0 ]; then
elif [ "$ec" -ne 2 ]; then
echo "$out" >&2
exit "$ec"
fi
More from open-design
All skills →
About this skill
What does the ecommerce-image-workflow skill do?

Reference-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.

How do I install it?

Run `npx skills add nexu-io/open-design --skill ecommerce-image-workflow --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From nexu-io/open-design, a repository with 83,577 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going