Shopify Pdp Set

---
name: "shopify-pdp-set"
description: "Turn seller-supplied product facts into a Shopify product-page image set for a single SKU. This Shopify PDP set studio lays out each named theme as a product detail image, keeping one image per theme so the listing gallery stays consistent. Use it for Shopify detail pages, listing galleries, and product detail images."
---

# Shopify Product-Page Stills

Turn seller-supplied product facts into one Shopify product-page still
per named theme. Deliver 4 to 8 stills for one SKU. Keep each still as
its own file.

## Scope and adjacent routes

Use this Skill when a Shopify listing needs a themed product-page
gallery from facts the seller already supplied.

Route a generic marketplace hero-lifestyle-detail gallery to
`ecommerce-listing-image-set`. Route Amazon A+ selling-point modules to
`amazon-a-plus-module-pack`. Route a silent product-detail clip to
`instagram-reel-to-pdp-clip`. Do not look up public posts or store
catalogs for a missing theme.

## Collect confirmed facts

Hard inputs are:

- the exact SKU name;
- the seller-supplied product facts that will appear on the stills
  (material, size, use, look, or other theme the seller already wrote);
- how many stills the set should contain, or permission to use the
  default of 4.

Reuse brand palette, destination, language, and must-keeps already in
the conversation. Ask only for a missing hard input. A count outside
4 to 8 is still doable: confirm that set size and its live cost.

Do not invent a material, review quote, price, shipping promise, or
certification. A product photo is a visual reference, not a source for
missing product facts. File access is not consent.

Inspect every optional still. Record MIME type, width, height, aspect
ratio, byte size, and whether it has an alpha channel. For a local
file, upload only through the bundled client after inspection
(`scripts/mcp_client.py` / `beatra.assets.upload`). Keep the returned
artifact id. Never pass a local path to `beatra.images.generate` or
`beatra.images.edit`.

Default to one still per named theme. If the seller wants a standard
Shopify set and has not numbered the themes, plan up to four roles
from the facts already given: hero, detail, lifestyle, and use. Leave
a theme whose fact is missing on the plan.

Keep the same product look, palette, and lighting across the set so
the stills read as one Shopify product page.

## Plan the free set list

Write a labeled set list before any paid image. Default four themes
unless the seller names another count in 4 to 8. Each item records the
SKU, the printed product lines from supplied facts, visual role,
language, canvas, and any optional reference role.

That list is the free visible result. Planning is not approval.

Safe defaults:

- one `beatra.images.generate` call per theme;
- `model: "auto"` and `count: 1`;
- canvas `{"type":"preset","tier":"2K","aspect":"1:1"}` unless the
  seller named another Shopify slot;
- `beatra.images.edit` only after the seller accepts a still and asks
  for a local correction, with that accepted image as `images[0]`.

## Confirm once, create by theme

Planning is free. Before the first billable call, read
`beatra.models.list` for `text_to_image`:

```json
{"capability": "text_to_image"}
```

Show one current production card and wait:

1. Work — one Shopify product-page still per named theme
   (`beatra.images.generate`).
2. Credits — the live `text_to_image` price just read, times the
   theme count. Do not reuse a remembered number.
3. Count — one paid call per still. Do not batch several themes
   into one `count`.
4. Identity — one new opaque `client_request_id` per still.
5. If we stop here — the labeled set list remains usable.
6. If the balance is insufficient — relay the official message and
   its top-up URL exactly. Translate the prose; keep the URL. Do not
   retry until the seller says they have topped up.

Submit once through bundled `scripts/mcp_client.py`. Poll
`beatra.tasks.get`. Deliver actual bytes plus
`billing.net_charged_credits`. Do not promise the prepaid estimate is
the final charge.

After approval, submit each theme once. Keep no more than two
generation tasks in flight on one connection.

A later local correction is new paid work. Read the live `image_edit`
card first. Show a separate six-field edit card. Use a new
`client_request_id`.

## Review, deliver, and recover

Review printed lines against the confirmed fact list. Report only the
text the host can actually see. Treat generated small type as a review
item, not as certified Shopify listing copy.

Deliver the stills in theme order, the set list, observed dimensions
and formats, task IDs, resolved models, and returned
`billing.net_charged_credits`.

After a returned `task_id`, poll that task. If the create response is
lost, search with `beatra.tasks.list` and verify with
`beatra.tasks.get` before replay. Reuse an ID only with
byte-identical arguments. A changed SKU, theme fact, canvas, model, or
prompt is a new card and a new ID. Cancel only when the seller asks.

## Execution

Invoke every remote Beatra operation only through this package's bundled
`scripts/mcp_client.py`. Put the MCP tool name after `call` and send one
JSON object on standard input.

```bash
python3 scripts/mcp_client.py call beatra.models.list
```

```json
{"capability": "text_to_image"}
```

```text
printf '%s' '{"prompt":"Create the approved Shopify product-page still for the named theme. Show only the confirmed SKU and product facts. Keep the shared product-page look.","model":"auto","count":1,"canvas":{"type":"preset","tier":"2K","aspect":"1:1"},"client_request_id":"opaque-shopify-pdp-01"}' | python3 scripts/mcp_client.py call beatra.images.generate
```

Do not configure or call a host Beatra Connector, and do not use
REST/OpenAPI as a fallback.

## Account balance

When the user asks how many credits remain or whether a live estimate fits,
call `beatra.wallet.get`. When they ask what was charged, call
`beatra.wallet.ledger`. Both are read-only. Do not invent an account-balance or
top-up tool. Do not make `wallet.get` a required step before every paid submit.

When a model card comes back carrying a `top_up` block, relay its tiers as the
card lists them and in that order. Do not rank them, do not talk one down, and
do not pick one for the user. Which tier suits them is their call, made on
the wallet page with the whole list in front of them. Never quote a tier from
memory.

## References by task

- For theme lists, payloads, confirmation, polling, recovery, and
  review, read [Shopify PDP still workflow](references/workflow.md).
- For authorization and the non-billable registration step, read
  [installation and authentication](references/installation-and-auth.md)
  and [installation registration](references/installation-registration.md).
- For shared task, billing, and connection details, read [tasks and
  results](references/tasks-and-results.md), [billing, errors, and
  recovery](references/billing-errors-and-recovery.md), and [Bundled MCP
  Client diagnostics](references/mcp-connection.md).
- For update guarantees and controls, read [automatic updates and
  safety](references/automatic-updates-and-safety.md). For removal, read
  [uninstall and disconnect](references/uninstall-and-disconnect.md).

## Runtime and safe automatic updates

The bundled client silently checks for a newer release at most once
every 24 hours per installation. When a newer version is available, it
installs automatically without separate confirmation. It downloads only
from the fixed official Beatra discovery and immutable CDN paths for
this package, channel, and locale, verifies discovery data, archive,
manifest, and every packaged file, and replaces only package-owned
files.

Update checks, downloads, verification, replacement, rollback, and
recovery fail open: the current installation remains usable and the
original command continues. An update failure never authorizes retrying
a paid image request. The setting persists for this installation. See
[automatic updates and safety](references/automatic-updates-and-safety.md).

```text
python3 scripts/mcp_client.py update --auto off
python3 scripts/mcp_client.py update --auto on
python3 scripts/mcp_client.py update --check
```