hello-retail

Get the plugin's Playwright browsers logged in to Hello Retail — one saved login (~/.hr-auth.json) shared by every playwright worker, so any number of Claude Code sessions can run storefront QA in parallel. Use whenever a QA or tile skill's login check fails on the Playwright backend (my.helloretail.com redirects to signin.html, the HR widget is missing, shopState.user is null, "Browser is already in use", the playwright servers fail to connect), or someone says "log in to Hello Retail in the browser", "set up the Playwright browsers", "set up parallel browsers", "my browser sessions are logged out", "hr-auth.json is missing/expired", "refresh the HR login", or asks how to QA several customers at once. Also the first-time setup on a new machine: installs Node.js and Playwright under ~/.hr-* with no admin rights. Never asks for or types credentials — the Google SSO login is always the operator's own action in the opened window.

Generate a branded Hello Retail PDF analytics report for a customer covering Search performance, Recommendations performance, Pages performance, and Product Agent (Klaviyo) results, using live data from the Hello Retail MCP. Trigger when someone says "analytics report for [customer/websiteUuid]", "generate a report for [domain]", "customer analytics PDF", "search report for [customer]", "recommendations report for [customer]", or "make a report for [websiteUuid]" — also when a language is named: "report in Danish", "rapport på dansk", "dansk analyserapport", "report in [language]".

Write or update the customer's living hand-off document, one file per website: platform and theme, the ClickUp card with project owner, developer, CSM and dates, the stage plan derived from the sold features, onboarding performance for management, the configuration per feature from the hello-retail MCP, every unique case and how it was solved, decisions, open items, and anonymised learnings for the knowledge base. Use when someone says "hand-off document for [domain]", "handoff doc", "handover for [customer]", "document this onboarding", "record what we did for [customer]", "close the onboarding", "final handoff", or ends a build / QA / feed task with "and write the handoff". Trigger with only a domain or website-uuid. Also runs automatically, in record mode, at the end of every developer, feed and QA skill. Read-only towards ClickUp and the dashboard. Does NOT build or QA — that is the *-developer and *-qa skills.

Migrate a Hello Retail V1 feed to a V2 product feed. Use whenever someone provides a legacy V1 feed configuration — crawl strings, or the raw crawlSpec JSON with "sel"/"val"/"multi"/"lit" targets and "proc" chains — and wants it "migrated", "converted", "ported" or "upgraded" to V2, or asks to "carry over the old logic" or "recreate this in v2". Trigger on the V1 config plus an intent to migrate, even before a websiteUuid or feed url has been given.

Set up a Hello Retail V2 product feed from scratch — fetch the feed, inspect its schema, build an explicit field mapping, generate human-readable transformation code, and create the feed via the Hello Retail MCP. Use this skill whenever someone says "set up a feed", "create a feed", "new feed for [platform]", "onboard a feed", or provides a feed URL and asks to connect it to Hello Retail. Trigger even if the user only provides a URL and a website UUID — that's enough to start.

Answer any question about Hello Retail from the bundled team wiki — what the platform does, how features work (Search, Recommendations, Pages, Product Agents, Retail Media), platform-specific install nuance (Shopify, Magento, custom), the D&TS onboarding flow, base templates, code cheat-sheets, acronyms and jargon. Trigger for questions like "how does X work in Hello Retail", "what does HR's Y feature do", "how do we onboard a customer", "what does this acronym mean", "which fields does the feed need", "how do swatches work on Magento", or any Hello Retail / HR / D&TS domain question.

Build a Hello Retail newsletter / email product-tile Liquid template that matches a customer's live storefront category-page tiles. Use whenever someone wants a newsletter product tile, email product tile, "email tile", "newsletter Liquid", "make a newsletter tile for [URL]", "build an email product tile matching this shop", "turn these tiles into a newsletter template", or pastes category-page / product-card markup and asks for an email version. Trigger even on just "newsletter tile" with a URL, or a question about which feed fields to use in a newsletter. Starts from the shared default design, scans the live tile, and produces a template Hello Retail renders to an image for the email. Designs are read, rendered and saved directly via the hello-retail MCP (newsletterContent_listDesigns / getDesign / getRenderingInfo / renderDesign / updateDesign / createDesign). Does NOT handle on-site Search or Recommendations tiles, or inbox-rendered triggered emails — that's triggered-email-developer.

QA of a Hello Retail email design before handoff — a Newsletter Content product tile (rendered server-side into one JPEG per product) and/or a Triggered Email design (base shell plus the four trigger flows). Use whenever someone says "newsletter QA", "QA the newsletter tile", "QA the email tile", "QA the triggered email", "QA the abandoned cart email", "review the email design", or gives a website-uuid and asks whether the design is ready. Runs a CODE pass (diff against the shared default, markers, translation, renderer or email-client compatibility, data binding, Liquid gotchas) and a light RENDERED pass, then compares with the shop's category-page tile on a "similar, not pixel-perfect" bar. Read-only: never writes a design; fixes go through newsletter-developer / triggered-email-developer. Trigger even on just "newsletter" or "abandoned cart" with a uuid or URL. Not for on-site Search, Recoms or Pages — those are search-qa, recom-qa, pages-qa.

Build and edit Hello Retail PAGES designs — the dynamic category/brand pages that replace a shop's static listing pages — via the Pages MCP tools (pages_listDesigns, pages_getDesign, pages_updateDesign, pages_updateDesignFilters, pages_updateDesignSorting, pages_createDesign, pages_copyDesign). Use when someone wants to create, customize, splice a product tile into, or configure filters/sorting on a Pages design. Also owns the PAGE CONFIGS: which products a page selects, their boosts, out-of-stock handling and design — "which products show on this category page", "pin/boost products on a Pages category", "create a brand page", "copy this page to another website". Also sets up Pages for API use, where the customer's frontend renders the products ("Pages via API", "headless Pages", "Pages config for API use"). Draft-only: publishing is a My Hello Retail dashboard step. Sibling of search-developer / recom-developer; the tile body comes from tile-extractor.

Full QA of a Hello Retail Pages implementation (Hello Retail-rendered category pages). Use whenever someone says "pages QA", "QA the category pages for [URL]", "check HR Pages", "review the pages implementation", or gives a storefront URL and asks to compare Hello Retail Pages with the shop's own category pages. Rendered pass: crawls category pages (main, sub, sale, brand), enables drafts via the on-site widget, walks the Pages and Product Tile checklists (design, filters, sorting, loading, products, translations, tile parity) on desktop and mobile/tablet. Detects API-based Pages first (widget label "Pages (API)") and skips the rendered walk for them; code-level and dashboard checks go to the operator's manual list. One report per domain. Trigger even if the user only says "pages" with a URL. Search → search-qa; Recommendations → recom-qa.

The D&TS master QA checklists for a Hello Retail onboarding, divided by feature: Setup & Data (feeds, selectors, order feed, tracking, sales status), Product Tile, Recommendations, Search, Pages, and Retail Media. Use this skill whenever someone says "QA checklist", "run the checklist", "manual QA", "go through the QA list for [feature]", "what should I check for [feature]", or wants the item-by-item catalogue of known defects to verify before handoff. Trigger even if the user only names a feature and says "checklist". For a single-feature QA prefer the full per-feature skills — search-qa / recom-qa / pages-qa — which run the two-pass QA on top of this catalogue; this skill is the shared catalogue + procedure behind them, and the direct entry for multi-feature, Setup & Data, and Retail Media walks.

Build a customer's Hello Retail Recommendations design — the swiper-slider box around the product tile — for an onboarding. Reads the live recom design via the hello-retail MCP, generates the slider shell (banner branch, swiper init/breakpoints/version/loop, the afterInit add-to-cart hook, clone-safe delegated handlers), drops in the product tile, shows a diff, and pushes a REVIEW draft via recoms_updateDesign — never publishes. Use for any HR Recommendations UI work: recom box, recom slider, .hr-product tile, swiper breakpoints, in-slider swatches or add-to-cart wiring, banner / Retail Media slides, REVIEW-draft pushes, or questions about HR recom structure. Trigger even if the operator only gives a website-uuid + design-key. The product tile body itself is produced by the tile-extractor skill, which this skill invokes. Does NOT handle HR Search — that's the separate search-developer skill.

Full QA of a Hello Retail Recommendations implementation. Use whenever someone says "QA this recom", "QA the recoms for [URL]", "check the recommendations", "QA the swiper", "run the recom checklist", or gives a storefront URL and asks to compare Hello Retail recommendation tiles with the shop's own product tiles. Two passes in one report: a RENDERED pass (delivery-mode detection, enables draft boxes via the on-site widget, crawls homepage / category / PDP / cart / 404, finds every box including upsell and cart recoms, checks tile parity, pricing, carousel behaviour, page-fit, translations, breakpoints, walks the Recommendations + Product Tile checklists, screenshots every FAIL) and a CODE pass on recoms_getDesign (click tracking, load order, placement selectors, leftover placeholders, Liquid gotchas). Targets the draft / internal-review design when one exists, else LIVE. One report per domain. Trigger even if the user only says "QA recoms" with a URL. Search → search-qa; Pages → pages-qa.

Build or edit a customer's Hello Retail Search design — the overlay or embedded shell around the product tile, desktop and mobile. Reads the live design via the hello-retail MCP, generates the shell (structure, branding, header matching, localization, trigger and placement selectors, tile-interactivity JS), drops in the product tile from tile-extractor, shows a diff, and pushes a REVIEW draft via search_updateDesign — never publishes. Use for any Hello Retail Search work: "build the search for [URL]", "the search on my webshop", search.liquid / search.css / search.js, trigger-selector wiring, add-to-cart / swatch / review / wishlist JS, branding, translation, or layout options on an existing design (filters column, sticky filters, result count, show-more, mobile buttons). Trigger even if only a website-uuid is given — with no search key it lists the website's configs, creates the config as a draft, then asks a short intake for whatever is missing. Does NOT handle Recommendations — that's recom-developer.

Full QA of a Hello Retail Search implementation. Use whenever someone says "QA the search for [URL]", "QA this customer", "self QA", "run the search checklist", "review the search implementation", or gives a storefront URL and asks to compare Hello Retail search with the shop's own product tiles. Two passes in one report: a RENDERED pass (delivery-mode detection, enables draft solutions via the on-site widget, inspects native category-page tiles, opens the overlay, checks tile parity, pricing, translations, filters, mobile/tablet, walks the Search + Product Tile checklists, screenshots every FAIL) and a CODE pass on search_getDesign (click tracking, interactivity re-binding, selectors, leftover placeholders, Liquid gotchas). Targets LIVE or a REVIEW draft. One report per domain; dashboard-only items go to a manual list. Trigger even if the user only says "QA" with a URL. Recoms → recom-qa; Pages → pages-qa.

Debug a Hello Retail support ticket and answer it from evidence — gate it first (confirm the customer, website and feature and wait, check what the MCP can reach, rule out false positives, widen the scope), then read the live configuration, reproduce on the storefront via Playwright (Claude in Chrome as the fallback), and propose the fix the evidence supports — cited to the config, the reproduction, or the knowledge base. Use when someone pastes a support ticket ("Resolve this Hello Retail support ticket. Run the hello-retail:support-debugging skill"), or says "debug this ticket", "triage this support issue", "customer says search is broken", "the recom box is gone on [domain]", or hands over a ClickUp card. Trigger even when only the mail body is pasted with no customer id. Names one of four outcomes early — solve, ask, hand back, cannot solve — and proposes the fix rather than writing it unasked. Does NOT run a pre-handoff QA walk (search-qa / recom-qa / pages-qa) or build a design (*-developer).

Extract a customer's live product tile and convert it into a production-ready Hello Retail Liquid template + JavaScript for an onboarding. Visits the live category page via the Playwright MCP (Claude in Chrome is the fallback when it isn't available), detects the platform (Shopify, Magento, WooCommerce, Shopware, DanDomain, Lightspeed, PrestaShop and other webshop platforms), surveys every tile variation (sale, sold-out, badges, ratings, swatches, hover images), maps each element to the HR feed with a parity table, and returns the Liquid tile body plus ATC / rating / slider JS — never CSS. Use whenever someone wants to build or convert a Hello Retail product tile, a ".hr-product" tile, a dynamic tile template, or to turn a live storefront card or static HTML tile into HR Liquid. This skill produces the tile BODY that search-developer, recom-developer and pages-developer drop into their shells.

Build a Hello Retail Triggered Email design — a real, inbox-rendered HTML email (NOT a render-to-image newsletter) that matches the customer's live storefront. Use whenever a Hello Retail CSM wants to build or update a triggered email, an abandoned-cart email, a price-drop email, a back-in-stock email, a post-conversion email, or the shared triggered-email base design/shell — e.g. "build a triggered email for [URL]", "make an abandoned cart email", "price drop email", "back in stock email", "post conversion email", "update the TE base design", or when handed a website UUID + search key. Trigger even if they only say "triggered email for [URL]" or just name one flow. Covers all four trigger designs plus the base shell, mirrors the customer's live HR Search tile, and produces table-based, email-client-hardened Liquid with fully inline styles and a 2-up product grid. Does NOT handle on-site Search/Recommendations tiles or render-to-image Newsletter tiles — those are separate skills.