@sadrmanesh/commerce-agent-skills 0.0.0-stage → 0.3.1

package/skills/b2b-pricing/evals/examples/tiered-wholesale.md

@@ -0,0 +1,3 @@
+The unit price is resolved on the server by one function used by the product page, the cart, and order placement. The wholesale group has a price list with two entries for the mug: `minQuantity` 1 at 9.00 and `minQuantity` 10 at 8.50.
+
+A wholesale buyer ordering 9 mugs gets 9.00 each and sees "10 or more: 8.50 each". At 10 mugs the line is priced at 8.50 each. A guest matches no list and pays the public 11.00. The product page cache varies by group so the wholesale price is never shown to guests.

package/skills/b2b-pricing/evals/tasks.json

@@ -0,0 +1,19 @@
+{
+  "tasks": [
+    {
+      "id": "tiered-wholesale",
+      "task": "Wholesale buyers pay 9.00 per mug, or 8.50 each from 10 mugs. Guests pay 11.00. Describe where the price is computed and what a wholesale buyer sees for 9 and for 10 mugs.",
+      "expects": {
+        "must_include": ["server", "price list", "minQuantity", "9.00", "8.50"],
+        "must_not_include": ["compute the price in JavaScript in the browser"]
+      }
+    },
+    {
+      "id": "net-terms",
+      "task": "A company account wants to pay by invoice on Net 30 terms. What checks run before the order is accepted?",
+      "expects": {
+        "must_include": ["credit limit", "open invoices", "due date"]
+      }
+    }
+  ]
+}

package/skills/b2b-pricing/references/price-lists.md

@@ -0,0 +1,46 @@
+# Price lists
+
+## Shape
+
+```json
+{
+  "id": "wholesale-2026",
+  "currency": "EUR",
+  "groups": ["wholesale"],
+  "priority": 10,
+  "validFrom": "2026-01-01",
+  "validTo": "2026-12-31",
+  "entries": [
+    { "sku": "MUG-RED", "minQuantity": 1, "unitPrice": 9.00 },
+    { "sku": "MUG-RED", "minQuantity": 10, "unitPrice": 8.50 },
+    { "sku": "MUG-RED", "minQuantity": 50, "percentOff": 20 }
+  ]
+}
+```
+
+A contract is a price list with `companies` instead of `groups`.
+
+## Rules
+
+| Rule | Recommendation |
+| --- | --- |
+| Which lists apply | Lists for the buyer's company (contracts), then the buyer's groups, valid on the order date, in the cart currency |
+| Tier inside a list | Highest `minQuantity` that is at most the line quantity |
+| Several lists apply | Contract first. Then the lowest unit price, or the highest priority if the store chooses that. Record the rule in one place. |
+| `percentOff` base | The public regular price of the SKU |
+| Rounding | Round the unit price to the currency's minor unit, then multiply |
+
+## Request for the resolver script
+
+```json
+{
+  "sku": "MUG-RED",
+  "quantity": 12,
+  "company": "acme",
+  "groups": ["wholesale"],
+  "date": "2026-10-30",
+  "currency": "EUR",
+  "basePrice": 11.0,
+  "strategy": "lowest"
+}
+```

package/skills/b2b-pricing/scripts/resolve-price.mjs

@@ -0,0 +1,93 @@
+#!/usr/bin/env node
+// Resolve a B2B unit price from price lists.
+// Usage: node resolve-price.mjs <request.json> <lists.json>
+import { readFile } from "node:fs/promises";
+import path from "node:path";
+import { fileURLToPath } from "node:url";
+
+function roundMoney(value, decimals = 2) {
+  const factor = 10 ** decimals;
+  return Math.round(value * factor) / factor;
+}
+
+function inWindow(list, date) {
+  if (!date) return true;
+  if (list.validFrom && date < list.validFrom) return false;
+  if (list.validTo && date > list.validTo) return false;
+  return true;
+}
+
+function tierFor(list, request) {
+  const entries = (list.entries ?? [])
+    .filter((entry) => entry.sku === request.sku)
+    .sort((a, b) => a.minQuantity - b.minQuantity);
+  const eligible = entries.filter((entry) => entry.minQuantity <= request.quantity);
+  if (eligible.length === 0) return null;
+  const entry = eligible[eligible.length - 1];
+  const next = entries.find((candidate) => candidate.minQuantity > request.quantity) ?? null;
+  return { entry, next };
+}
+
+function unitPrice(entry, basePrice, decimals) {
+  if (typeof entry.unitPrice === "number") return roundMoney(entry.unitPrice, decimals);
+  if (typeof entry.percentOff === "number") {
+    if (typeof basePrice !== "number") throw new Error(`${entry.sku}: percentOff needs basePrice`);
+    return roundMoney(basePrice * (1 - entry.percentOff / 100), decimals);
+  }
+  throw new Error(`${entry.sku}: an entry needs unitPrice or percentOff`);
+}
+
+/**
+ * Returns { unitPrice, source, list, minQuantity, nextTier }.
+ * Contract lists (with `companies`) win. Otherwise `strategy` is "lowest" (default) or "priority".
+ */
+export function resolvePrice(request, lists, { decimals = 2 } = {}) {
+  if (!Number.isInteger(request.quantity) || request.quantity <= 0) throw new Error("quantity must be a positive whole number");
+  const active = lists.filter(
+    (list) => inWindow(list, request.date) && (!request.currency || !list.currency || list.currency === request.currency),
+  );
+  const contracts = active.filter((list) => request.company && (list.companies ?? []).includes(request.company));
+  const groupLists = active.filter((list) => (list.groups ?? []).some((group) => (request.groups ?? []).includes(group)));
+
+  const candidates = [];
+  for (const [source, pool] of [["contract", contracts], ["group", groupLists]]) {
+    for (const list of pool) {
+      const tier = tierFor(list, request);
+      if (!tier) continue;
+      candidates.push({
+        unitPrice: unitPrice(tier.entry, request.basePrice, decimals),
+        source,
+        list: list.id,
+        priority: list.priority ?? 0,
+        minQuantity: tier.entry.minQuantity,
+        nextTier: tier.next
+          ? { minQuantity: tier.next.minQuantity, unitPrice: unitPrice(tier.next, request.basePrice, decimals) }
+          : null,
+      });
+    }
+    if (source === "contract" && candidates.length > 0) break;
+  }
+
+  if (candidates.length === 0) {
+    if (typeof request.basePrice !== "number") throw new Error(`${request.sku}: no price list applies and no basePrice`);
+    return { unitPrice: roundMoney(request.basePrice, decimals), source: "public", list: null, minQuantity: 1, nextTier: null };
+  }
+  const strategy = request.strategy ?? "lowest";
+  candidates.sort((a, b) =>
+    strategy === "priority" ? b.priority - a.priority || a.unitPrice - b.unitPrice : a.unitPrice - b.unitPrice || b.priority - a.priority,
+  );
+  const { priority: _priority, ...best } = candidates[0];
+  return best;
+}
+
+const isCli = process.argv[1] && path.resolve(process.argv[1]) === fileURLToPath(import.meta.url);
+if (isCli) {
+  const [requestFile, listsFile] = process.argv.slice(2);
+  if (!requestFile || !listsFile) {
+    console.error("Usage: node resolve-price.mjs <request.json> <lists.json>");
+    process.exit(2);
+  }
+  const request = JSON.parse(await readFile(requestFile, "utf8"));
+  const lists = JSON.parse(await readFile(listsFile, "utf8"));
+  console.log(JSON.stringify(resolvePrice(request, lists), null, 2));
+}

package/skills/catalog-import-and-migration/SKILL.md

@@ -0,0 +1,58 @@
+---
+name: catalog-import-and-migration
+description: "Import, export, and migrate product catalogs with stable SKU keys, a dry run, parent-before-variation order, batched writes, and URL redirects. Use when moving a store between platforms, bulk importing CSV or JSON products, or exporting a catalog for another system."
+license: MIT
+compatibility: "The row checker needs Node.js 20 or newer and no packages."
+metadata:
+  author: Naser Sadrmanesh
+  version: "0.3.1"
+---
+
+# Catalog import and migration
+
+An import is a repeatable job, not a one-off script. Run it against a copy first, make it safe to run twice, and keep a report of every row. Column maps between platforms are in [the field mapping notes](references/field-mapping.md).
+
+## Procedure
+
+1. Export the source with every field you need: products, variations, attributes, categories, images, stock, prices, SEO fields, and old URLs. Keep the raw export unchanged.
+2. Map fields to the target in one file. Normalize units, currencies, decimals, and booleans there, not in ad hoc fixes.
+3. Choose a stable key. Use the SKU when every sellable unit has a unique one; otherwise keep the source id in a dedicated field such as `meta:source_id`. Never key on the product name.
+4. Check every row before writing anything: `node scripts/check-import-rows.mjs rows.json` reports duplicate SKUs, variations without a parent, invalid prices, and negative stock.
+5. Do a dry run that reports creates, updates, and skips per row without writing.
+6. Import in order: categories and attributes, then parent products, then variations, then images and relations (upsells, bundles). A variation needs its parent's id.
+7. Write in batches (the WooCommerce batch endpoint takes up to 100 items per request) and record the target id for every source key, so a rerun updates instead of duplicating.
+8. Create 301 redirects from every old product and category URL to the new one.
+9. Compare counts and totals: products, variations, stock units, and a sample of prices.
+
+## Idempotent runs
+
+Look up each row by its key before deciding create or update. Store `source key -> target id` after every batch. A crash halfway through then resumes without duplicates.
+
+## Images
+
+Download source images once, deduplicate by content hash, and upload them to the target media library before linking them. Hotlinking to the old store breaks when it shuts down.
+
+## Exports
+
+Export with a documented column set and UTF-8. Include ids, SKUs, and parent references so the file can be imported back. Use `.` as the decimal separator and ISO 8601 dates. Escape fields with quotes according to RFC 4180 when writing CSV.
+
+## Gotchas
+
+- Spreadsheet programs strip leading zeros from SKUs and barcodes and turn long numbers into scientific notation. Treat them as text.
+- Importing variations before their parent creates orphans or fails. Sort parents first.
+- Prices with a comma decimal (`19,90`) parse as 1990 or fail in some importers.
+- Running the import twice without a key creates every product twice.
+- Missing redirects lose search rankings and break links in old emails.
+- Customer passwords usually cannot move between platforms. Plan a reset email instead of copying hashes the target cannot read.
+
+## Verification
+
+- The row checker reports no errors before the real run.
+- A second run of the same file updates rows and creates nothing.
+- Product, variation, and stock totals match the source.
+- Every old URL in a sample returns 301 to the right new page.
+- A variable product shows the same options and per-variation prices as the source.
+
+## Evaluation
+
+Worked examples and the checks they must satisfy are in [evals/tasks.json](evals/tasks.json).

package/skills/catalog-import-and-migration/evals/examples/platform-migration-urls.md

@@ -0,0 +1,3 @@
+Export every old product and category URL with its source id. After the import, map each source id to the new URL and create a permanent 301 redirect for each.
+
+Test a sample of old URLs, including ones from email campaigns and the sitemap, and check each returns 301 to the right page. Submit the new sitemap so search engines move their index to the new URLs.

package/skills/catalog-import-and-migration/evals/examples/rerunnable-import.md

@@ -0,0 +1,3 @@
+Use the SKU as the key and check every row first: duplicate SKUs, variations whose `Parent` is missing, and comma decimals. Then do a dry run that reports create, update, or skip for each row without writing.
+
+Import categories and attributes, then variable parents, then variations under each parent. Write with the batch endpoint, 100 items per request, and after each batch save the map from source key to WooCommerce id. If the job crashes, rerunning it looks up each SKU first and updates instead of creating duplicates.

package/skills/catalog-import-and-migration/evals/tasks.json

@@ -0,0 +1,20 @@
+{
+  "tasks": [
+    {
+      "id": "rerunnable-import",
+      "task": "Write the plan for importing 20,000 products with variations from a CSV into WooCommerce so that the job can crash and be run again safely.",
+      "expects": {
+        "must_include": ["SKU", "dry run", "Parent", "batch", "source key"],
+        "must_not_include": ["match products by name"]
+      }
+    },
+    {
+      "id": "platform-migration-urls",
+      "task": "A store moves from one platform to another and the product URLs change. What keeps search rankings and old links working?",
+      "expects": {
+        "must_include": ["301", "redirect"],
+        "must_not_include": ["302"]
+      }
+    }
+  ]
+}

package/skills/catalog-import-and-migration/references/field-mapping.md

@@ -0,0 +1,43 @@
+# Field mapping
+
+## WooCommerce CSV importer columns
+
+The built-in product CSV importer reads these columns, among others.
+
+| Column | Notes |
+| --- | --- |
+| `ID` | Existing product id. Leave empty to create. |
+| `Type` | `simple`, `variable`, `variation`, `grouped`, `external` |
+| `SKU` | Unique per product and variation. Used to match existing products when "Update existing products" is checked. |
+| `Name` | Product name. Variations can leave it empty. |
+| `Parent` | For a variation: the parent's SKU, or `id:123` |
+| `Regular price`, `Sale price` | Decimal with `.` |
+| `Stock`, `In stock?` | Quantity, and `1` or `0` |
+| `Categories` | Comma-separated, `>` for hierarchy: `Clothing > Shirts` |
+| `Images` | Comma-separated URLs. The first is the main image. |
+| `Attribute 1 name`, `Attribute 1 value(s)`, `Attribute 1 visible`, `Attribute 1 global` | Variable products list all values. Variations list their one value. |
+| `Meta: _custom_key` | Custom meta |
+
+For more control, use the REST API: create the parent with `POST products`, then variations with `POST products/{id}/variations/batch`.
+
+## Common platform mappings
+
+| Concept | WooCommerce | Shopify | Generic JSON |
+| --- | --- | --- | --- |
+| Product | product | product | `product` |
+| Sellable unit | variation | variant | `variant` |
+| Option | attribute | option (up to 3 per product) | `options` |
+| Price | `regular_price` | `price` | `price` |
+| Compare-at price | `regular_price` with a `sale_price` | `compareAtPrice` | `listPrice` |
+| Stock | `stock_quantity` | inventory level per location | `stock` |
+| Handle or slug | `slug` | `handle` | `slug` |
+
+Shopify allows at most three options per product, and a limited number of variants per product, so a WooCommerce product with four attributes must be split or flattened before migrating.
+
+## Report file
+
+Write one line per source row:
+
+```json
+{"key":"TEE-BLUE-M","action":"update","targetId":5123,"warnings":[]}
+```

package/skills/catalog-import-and-migration/scripts/check-import-rows.mjs

@@ -0,0 +1,75 @@
+#!/usr/bin/env node
+// Check catalog rows before an import.
+// Usage: node check-import-rows.mjs <rows.json>
+// rows.json: [{ "sku": "TEE", "type": "variable", "name": "Tee" }, { "sku": "TEE-M", "type": "variation", "parent": "TEE", "regularPrice": "19.90", "stock": 4 }]
+import { readFile } from "node:fs/promises";
+import path from "node:path";
+import { fileURLToPath } from "node:url";
+
+const TYPES = new Set(["simple", "variable", "variation", "grouped", "external"]);
+const PRICE = /^\d+(?:\.\d{1,4})?$/;
+
+/** Returns a list of problems, one string per problem, with the row number (1-based). */
+export function checkImportRows(rows) {
+  if (!Array.isArray(rows)) return ["rows must be an array"];
+  const errors = [];
+  const seen = new Map();
+  const parents = new Map();
+  rows.forEach((row, index) => {
+    const label = `row ${index + 1}`;
+    if (!row || typeof row !== "object") {
+      errors.push(`${label}: must be an object`);
+      return;
+    }
+    const type = row.type ?? "simple";
+    if (!TYPES.has(type)) errors.push(`${label}: unknown type ${type}`);
+    const sku = typeof row.sku === "string" ? row.sku.trim() : "";
+    if (sku === "") {
+      errors.push(`${label}: missing sku`);
+    } else if (seen.has(sku)) {
+      errors.push(`${label}: duplicate sku ${sku} (first on row ${seen.get(sku)})`);
+    } else {
+      seen.set(sku, index + 1);
+      if (type === "variable") parents.set(sku, index + 1);
+    }
+    if (typeof row.sku === "number") errors.push(`${label}: sku must be text, not a number`);
+    if (type !== "variation" && (typeof row.name !== "string" || row.name.trim() === "")) errors.push(`${label}: missing name`);
+    for (const field of ["regularPrice", "salePrice"]) {
+      if (row[field] === undefined || row[field] === "") continue;
+      if (!PRICE.test(String(row[field]))) errors.push(`${label}: ${field} "${row[field]}" must use digits and a . decimal`);
+    }
+    if (row.salePrice && row.regularPrice && Number(row.salePrice) >= Number(row.regularPrice)) {
+      errors.push(`${label}: salePrice must be lower than regularPrice`);
+    }
+    if (row.stock !== undefined && (!Number.isInteger(row.stock) || row.stock < 0)) {
+      errors.push(`${label}: stock must be a whole number of 0 or more`);
+    }
+  });
+  rows.forEach((row, index) => {
+    if (row?.type !== "variation") return;
+    const label = `row ${index + 1}`;
+    if (!row.parent) {
+      errors.push(`${label}: variation without parent`);
+    } else if (!parents.has(row.parent)) {
+      errors.push(`${label}: parent ${row.parent} is not a variable product in this file`);
+    } else if (parents.get(row.parent) > index + 1) {
+      errors.push(`${label}: parent ${row.parent} comes after its variation; sort parents first`);
+    }
+  });
+  return errors;
+}
+
+const isCli = process.argv[1] && path.resolve(process.argv[1]) === fileURLToPath(import.meta.url);
+if (isCli) {
+  const [file] = process.argv.slice(2);
+  if (!file) {
+    console.error("Usage: node check-import-rows.mjs <rows.json>");
+    process.exit(2);
+  }
+  const errors = checkImportRows(JSON.parse(await readFile(file, "utf8")));
+  if (errors.length > 0) {
+    for (const error of errors) console.error(`- ${error}`);
+    process.exit(1);
+  }
+  console.log("Rows look importable.");
+}

package/skills/catalog-order.txt

@@ -0,0 +1,29 @@
+woocommerce-plugin-development
+woocommerce-rest-api
+wordpress-plugin-security
+payment-gateway-integration
+product-catalog-modeling
+marketplace-search-and-ranking
+checkout-ux-and-conversion
+rtl-and-persian-localization
+order-and-webhook-reliability
+ecommerce-seo-structured-data
+multi-vendor-payouts
+shopify-app-development
+headless-nextjs-storefront
+google-merchant-product-feeds
+tax-and-shipping
+subscription-billing
+fraud-and-risk-basics
+vector-product-search
+product-description-guardrails
+conversion-event-tracking
+stripe-payments
+iranian-payment-gateways
+inventory-and-multi-warehouse
+returns-and-refunds
+b2b-pricing
+catalog-import-and-migration
+storefront-accessibility
+storefront-performance
+mcp-store-tooling

package/skills/checkout-ux-and-conversion/SKILL.md

@@ -0,0 +1,86 @@
+---
+name: checkout-ux-and-conversion
+description: "Design checkout so the full cost is visible before payment, guest purchase works, and field or payment errors can be corrected without losing the cart. Use when changing the checkout flow, address form, payment choice, or order confirmation page."
+license: MIT
+metadata:
+  author: Naser Sadrmanesh
+  version: "0.3.1"
+---
+
+# Checkout UX and conversion
+
+Use this skill when changing the checkout a shopper sees. Payment capture rules live in the payment skill. Persian and RTL layout lives in the localization skill. Field-level review questions are in [the checkout review](references/checkout-review.md).
+
+This skill does not claim a conversion rate. It states conditions the checkout has to meet so a shopper can finish an order they already decided to place.
+
+## Procedure
+
+1. Show merchandise, discounts, shipping, tax, and the amount that will be charged before the pay control.
+2. Allow a guest purchase. Offer account creation after the order, or as an optional choice that does not block payment.
+3. Validate fields inline, next to the field, in the shopper's language. Move focus to the first error.
+4. Keep the cart and the entered address when payment is declined.
+5. Disable the pay control after the first accepted submit, and make the order request idempotent so a double submit creates one order.
+6. Confirm with an order number and a plain statement of what was charged. Do not offer a second pay control on that page.
+
+## Cost
+
+- Shipping method and shipping cost are chosen before payment. If the address changes the cost, update the total before the shopper pays.
+- A fee or payment surcharge is a line in the total, not a surprise on the provider's page.
+- The currency is visible. If you display a second currency, the charged currency is the one in the pay button label.
+- Coupon entry does not clear the address or the selected shipping method.
+
+## Address and contact
+
+- Ask for the fields the order needs. Drop a field rather than marking it optional and ignoring it.
+- Use autocomplete attributes from the HTML specification: `given-name`, `family-name`, `address-line1`, `address-line2`, `address-level1`, `address-level2`, `postal-code`, `country`, `email`, `tel`.
+- Set input types: `email`, `tel`, and an appropriate keyboard for the postal code. Do not force a North American phone mask on other countries.
+- When the country changes which fields are required, update the form before submit. WooCommerce does this through country locale settings. Do not keep a second hard-coded field list that disagrees with `woocommerce_get_country_locale`.
+- The country control comes before fields whose labels and requirements depend on it.
+
+## Payment choice
+
+- List only methods the shop can capture and refund.
+- Each method shows its name and, when it adds a cost, that cost.
+- Card entry uses the provider's hosted fields or a redirect. The merchant page does not collect PAN or CVV.
+- The primary control states the action and the amount, for example "Pay 19.00 USD". A generic "Submit" is not enough when more than one control is on the page.
+- Express wallets, when you offer them, create the same server-side order and idempotency path as the regular form.
+
+## Errors
+
+- Field errors name the field and how to fix it. Do not rely on color alone.
+- A payment decline says that the payment was not taken and that the shopper can try another method. Do not say the order was placed.
+- A network timeout says the outcome is unknown and points to the order status or a retrieve. Do not immediately start a second charge. Reuse the same idempotency key.
+- Keep the shopper's typed values. Re-render the form with those values and the error.
+
+## Confirmation
+
+- Show the order number, the charged total, and the shipping destination.
+- Send the receipt email once, from the paid transition, not from the browser page load.
+- A reload of the confirmation page does not place another order.
+
+## Mobile and accessibility
+
+- One column when the viewport is narrow. The total stays visible near the pay control.
+- Tap targets are large enough to hit without zooming. Error text is not only a tooltip.
+- Every control has a label. Errors use `aria-invalid` and are referenced from the field.
+- Focus order follows the visual order, including in RTL layouts.
+
+## Gotchas
+
+- Hiding shipping cost until after the pay button is the usual reason a shopper abandons at the last step. Show it earlier.
+- Creating the account, and requiring the shopper to leave checkout to verify email, loses the order in progress. Save the order first.
+- A pay button that stays enabled can create two pending orders. Disable it and dedupe on the server.
+- Validation that only runs in the browser will be skipped. Repeat every rule on the server.
+- Third-party badge images do not replace a real returns or shipping policy link.
+
+## Verification
+
+- A guest can pay without creating a password.
+- Changing the address updates shipping and the pay-button amount before payment.
+- A declined payment preserves the cart and the address.
+- Submitting twice creates one order and charges once.
+- Keyboard-only use reaches every field, the error, and the pay control. In a narrow viewport the total is still visible with the pay control.
+
+## Evaluation
+
+Worked examples and the checks they must satisfy are in [evals/tasks.json](evals/tasks.json).

package/skills/checkout-ux-and-conversion/evals/examples/guest-total.md

@@ -0,0 +1,3 @@
+Show the full cost and allow a guest purchase.
+
+The shipping method and tax are visible before the pay control. A guest can pay. Account creation is offered after the order, not as a gate.

package/skills/checkout-ux-and-conversion/evals/examples/single-submit.md

@@ -0,0 +1,3 @@
+After the first accepted submit, disable the pay control and send a stable idempotency key for that attempt.
+
+The server returns the original order when the same key is retried. The cart remains if the provider declines.

package/skills/checkout-ux-and-conversion/evals/tasks.json

@@ -0,0 +1,30 @@
+{
+  "tasks": [
+    {
+      "id": "guest-total",
+      "task": "Let a guest see shipping and the charged total before paying, without creating a password first.",
+      "expects": {
+        "must_include": [
+          "guest",
+          "shipping"
+        ],
+        "must_not_include": [
+          "password is required"
+        ]
+      }
+    },
+    {
+      "id": "single-submit",
+      "task": "Stop a double click on the pay control from creating two orders for one cart.",
+      "expects": {
+        "must_include": [
+          "idempotency",
+          "disable"
+        ],
+        "must_not_include": [
+          "Math.random()"
+        ]
+      }
+    }
+  ]
+}

package/skills/checkout-ux-and-conversion/references/checkout-review.md

@@ -0,0 +1,41 @@
+# Checkout review
+
+Walk a real order in the browser. Record pass or fail. Do not treat a screenshot of the empty form as a review.
+
+## Before payment
+
+- Guest checkout is available, or the shop has a written reason it is not.
+- Line items, discounts, shipping, tax, and total match what the pay control will charge.
+- The shipping method can be changed without retyping the address.
+- A coupon or gift card failure leaves the rest of the form intact.
+- The pay button names the amount and currency.
+
+## Address
+
+- Required fields match the selected country.
+- Autocomplete attributes are set on contact and address fields.
+- Phone and postal code inputs do not apply a mask from a different country.
+- Error text is next to the field and is announced to assistive technology.
+
+## Payment
+
+- Only live, refundable methods are listed.
+- Card data is entered in hosted fields or on the provider page.
+- The first submit disables the pay control.
+- A second submit does not create a second order.
+- A decline keeps the cart.
+
+## After payment
+
+- The confirmation page shows the order number and the charged total.
+- Reloading confirmation does not charge again.
+- The receipt email is sent once.
+- The order is unpaid until the payment skill's server-side confirmation runs. The confirmation page does not itself mark the order paid.
+
+## RTL
+
+- Totals align to the correct side for the document direction.
+- The pay control is in the focus order a shopper expects for that direction.
+- Payment marks and card logos are not mirrored.
+
+Use the Persian and RTL skill for the layout rules behind these checks.

package/skills/conversion-event-tracking/SKILL.md

@@ -0,0 +1,64 @@
+---
+name: conversion-event-tracking
+description: "Send commerce analytics events with stable names, item ids, and a purchase event that fires once from a confirmed order. Use when adding or changing view_item, add_to_cart, begin_checkout, purchase, or refund tracking."
+license: MIT
+compatibility: "The event checker requires Node.js 20 or newer. No network access."
+metadata:
+  author: Naser Sadrmanesh
+  version: "0.3.1"
+---
+
+# Conversion event tracking
+
+Use this skill for measurement events. Checkout behavior is the checkout skill. Firing `purchase` before the payment skill confirms the order will count money you did not take.
+
+Event names and parameter rules below follow Google's GA4 recommended ecommerce events. Other analytics tools should use the same payload shape in this project so there is one server-side record. Re-check GA4's event reference if a report disagrees with a parameter.
+
+## Procedure
+
+1. Use the recommended names: `view_item`, `add_to_cart`, `begin_checkout`, `add_shipping_info`, `add_payment_info`, `purchase`, and `refund`.
+2. Send `items` with `item_id` (the SKU or stable unit id) and `item_name`. Include `price` and `quantity` when you send `value`.
+3. Set `value` to the sum of `price * quantity`. Do not include shipping or tax in `value`. Send those as `shipping` and `tax` on `purchase`.
+4. If `value` is set, set `currency` to the order's ISO 4217 code.
+5. Fire `purchase` once, from the server-confirmed payment, with a non-empty `transaction_id` equal to the order number.
+6. Respect the shop's consent settings before loading advertising tags. Do not describe that as a universal legal rule. The shop's policy decides where consent is required.
+
+Parameter checks are in [the event notes](references/events.md). Run `node scripts/check-event.mjs --file event.json`. Worked examples and checks are in [evals/tasks.json](evals/tasks.json).
+
+## Purchase
+
+`transaction_id` is required for `purchase`. GA4 deduplicates purchases that share a transaction id on web streams. An empty string is a bad id: Google documents that purchases with `transaction_id=""` are deduplicated together. Never send an empty id.
+
+The thank-you page may render the event only if a reload will send the same `transaction_id`. Prefer sending `purchase` from the server when payment is confirmed, and treat the browser event as a duplicate of that id rather than a second order.
+
+`value` excludes tax and shipping. A 10.00 item, 1.00 tax, and 2.00 shipping is `value: 10`, `tax: 1`, `shipping: 2`, not `value: 13`.
+
+## Items
+
+- `item_id` is the purchasable unit, not only the parent, when variants have different prices.
+- `quantity` is an integer greater than zero for a purchase line.
+- Do not put the customer's name, email, or phone on the item or the event.
+
+## Consent and duplicates
+
+- If the shop requires consent for advertising measurement, do not load those tags before the choice is stored.
+- Order-state analytics the merchant runs on their own server can still record the paid order. Keep that separate from a browser advertising tag.
+- `refund` uses the same `transaction_id` as the purchase and the refunded `items` or value. Do not reuse a purchase event to mean a refund.
+
+## Gotchas
+
+- Firing `purchase` on button click counts failed payments.
+- A new transaction id on every page load defeats deduplication and over-counts.
+- Summing tax into `value` overstates item revenue in GA4's definition.
+- Debug views that use a constant transaction id will collapse real orders together if that code ships.
+
+## Verification
+
+- The checker accepts a purchase whose `value` equals the item sum and rejects a purchase with an empty `transaction_id`.
+- A declined payment does not emit `purchase`.
+- Reloading the confirmation page does not create a second transaction id.
+- Item ids on variant products are variant SKUs.
+
+## Evaluation
+
+Worked examples and the checks they must satisfy are in [evals/tasks.json](evals/tasks.json).

package/skills/conversion-event-tracking/evals/examples/purchase-once.md

@@ -0,0 +1,3 @@
+Send purchase from the confirmed order.
+
+`transaction_id` is `1042`. `value` is the sum of item price times quantity. Tax and shipping are separate fields. A reload uses the same transaction id.

package/skills/conversion-event-tracking/evals/examples/variant-item-id.md

@@ -0,0 +1,3 @@
+Fire `add_to_cart` with `item_id` `SHIRT-BLUE` and the variant price.
+
+Do not emit purchase from the button click. Purchase waits for payment confirmation.