# Shopify Product Site Factory

> Build, refine or review a Shopify single-product or small-catalog website using the integrated v1.2 workflow, verified product facts, full desktop/mobile Home design and staged acceptance. This portable edition covers individual storefronts, not team DEV onboarding or subscription-specific batch-template adapters.

- Skill: `voltsommer2026/shopify-product-site-factory` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add voltsommer2026/shopify-product-site-factory`
- Raw SKILL.md: https://api.skillmd.com/api/skills/voltsommer2026/shopify-product-site-factory/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: Voltsommer2026 (https://skillmd.com/u/voltsommer2026)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/voltsommer2026/shopify-product-site-factory

---


# Product Website Build and Review — Portable v1.2

Read [the v1.2 manual](../product-site-suite/references/manual-v1.2.md). For an existing workspace, read its AGENTS, project status, facts, visual baseline and role brief. Preserve approved decisions and exact source locations; when adopting a different standard version record the change instead of replacing project rules wholesale.

## Build route

1. Derive the task mode from the user's request: new design, visual-only, strict replication or local change. A reference URL alone does not imply strict replication. Preserve content and behavior for visual-only tasks.
2. Research the supplied product/reference and prepare the facts document plus appearance/structure reference pack. Separate verified, supplier-claimed and unknown facts; preserve actual product geometry. Do not require launch prices/policies before independent design work.
3. Reuse an approved visual direction. For new exploration provide 2–3 materially different style cards and at least one complete Home desktop/mobile proposal. For replication map the supplied reference instead of inventing alternate styles. No imaginary rendered images: generate or build viewable artifacts using available capabilities.
4. Within authorized scope implement the shared framework and browsable Home, then progressively complete Product, Support, policies, Cart, 404 and applicable states. Use short rounds of necessary questions, not an upfront internal checklist for the user.
5. Use editable native Shopify sections/templates and real product/variant/cart/checkout data when accessible. Check gallery, variants, quantity, inventory/error states and app-controlled pricing together. Missing business data stays internal/explicitly incomplete, never a fabricated public commitment.
6. Follow manual Q1–Q5 for relevant tests and G2–G4 for stage reporting. Remote upload requires the exact store/theme, current remote read, minimal reconciliation, targeted write, readback and frontend verification. Existing live themes are not working drafts; publication requires applicable explicit authorization.

## Review route

Establish scope, current URL/theme/version, access identity, actual viewport and target milestone. Use the manual's evidence table to record expectation, observed result, priority, proof and retest owner. Check real rendering and enabled purchase behavior; an HTTP response or file hash does not prove visual or transaction success. Classify failures and missing evidence without modifying the site unless fixes were authorized. Strict replication also requires the chapter-four map, deviation log, per-device diff and zero unapproved omissions/reordering.

## Integration and dependencies

Use one STATUS, facts ledger and visual baseline; pages submit evidence to the master owner of QA-CHECKLIST and shared files. Honor precise write boundaries and existing permissions. At runtime prefer available purpose-built tools and applicable Shopify/browser/Git operating skills. If those skills or tools are absent, use supported equivalents, inspect their current help and report the actual missing dependency; do not call a fictional wrapper or reuse another machine's domain/port/token.

No remote account, paid app, model subscription or MiroMiro endpoint is bundled. Browser and storefront operations need user-provided access. Do not install services, change DNS, submit orders or send contact-form/email tests without corresponding authorization. Keep local research and preview work moving when remote steps are blocked. Record untested iOS/Android, performance, public-access and payment states separately.

## Finish

Report completed and verified scope, exact artifact/preview, unresolved issues, applicable standard version and separate local/remote/Git/Live/checkout/payment states. Do not announce a complete store based on Home alone or a complete replica based on technical checks alone.