6DuckLearn Skills

ecommerce platform adapter contract

Use when configuring an ecommerce platform adapter for 6DuckLearn/Codex. Defines the safe adapter contract between merchant scenario skills, platform skills, MCP/API/CLI connectors, read-only capability probes, Change Preview gates, and custom setup fallbacks.

ecommerce Tags: ecommerce, adapter, platform, connector, mcp, api, cli, setup, capability-probe, change-preview, shopify, shopline, custom

Ecommerce Platform Adapter Contract

You help 6DuckLearn users attach platform-specific ecommerce capabilities to the merchant scenario skills.

Use this as the generic adapter contract before using a Shopify, SHOPLINE, WooCommerce, custom, or future platform adapter.

Adapter Stack

Layer Responsibility
Merchant scenario skill Understand the merchant goal and produce the operating workflow
Platform adapter skill Map the workflow to platform concepts, scopes, limits, and setup steps
MCP/API/CLI connector Discover real capabilities and perform read-only probes
Confirmation gate Show exact Change Preview or Import Preview before mutation

Required Setup Brief

Adapter Setup Brief

| Field | Value |
|---|---|
| Platform | Shopify / SHOPLINE / WooCommerce / Custom / Unknown |
| Store identifier | exact domain, admin URL, or shop ID |
| Connector available | MCP / API / CLI / CSV only / none |
| Auth state | connected / not connected / test only / unknown |
| Requested workflow | catalog / inventory / orders / discounts / reports / storefront / import |
| Execution mode | read-only / draft / prepare live changes / live after confirmation |
| Missing setup | ... |

Capability Probe

Before promising execution, run or design a read-only probe:

Probe Evidence
initialize/connectivity connector responds
tools/list or route list supported actions are visible
read-only store identity store/domain matches the merchant
read-only object sample products/orders/inventory/report endpoint works
scope check missing scopes are listed

If no connector exists, produce setup instructions, CSV/import drafts, or admin-ready steps. Do not claim live execution.

Routing Rules

  • Shopify setup or execution: route to shopify-commerce-adapter.
  • SHOPLINE setup or execution: route to shopline-commerce-adapter.
  • Custom platform setup: route to ecommerce-custom-platform-setup.
  • Unknown platform: ask for platform, store URL, export sample, API docs, and desired workflow.
  • Store-changing actions always require a Change Preview before execution.

Change Preview Contract

Change Preview

| Platform object | Current | Proposed | Evidence | Risk |
|---|---|---|---|---|
| ... | read-only source value | requested change | connector/API/CSV row | customer / inventory / payment / SEO impact |

I will not apply these changes until you confirm. Reply "apply" to proceed, or tell me what to adjust.

Quality Gate

Before finishing:

  • Platform identity is explicit.
  • Connector capability is proven or clearly marked missing.
  • Unsupported actions are named.
  • Any mutation is previewed, not executed silently.
  • Custom setup gets a reusable adapter brief, not one-off instructions.

Related skills

  • ecommerce custom platform setup — Use when a merchant or builder wants to configure ecommerce support for a custom, unknown, headless, or not-yet-adapted platform. Produces an adapter setup brief, capability map, required credentials/scopes, read-only probe plan, CSV fallback, and MCP/API/CLI handoff checklist.
  • shopify commerce adapter — Use when configuring Shopify ecommerce workflows in Codex/6DuckLearn. Maps merchant scenario skills to Shopify Admin, Storefront MCP, GraphQL, CLI, CSV, products, variants, inventory, orders, discounts, metafields, and read-only probes before any store-changing action.
  • shopline commerce adapter — Use when configuring SHOPLINE ecommerce workflows in Codex/6DuckLearn. Maps merchant scenario skills to SHOPLINE products, variants, categories, inventory, orders, promotions, pages, Shop Builder widgets, CSV/import paths, and connector capability probes before execution.
  • ecommerce merchant operator — Use when a merchant wants help running or improving an ecommerce store. Triage the request, route phase-1 work to Shopify, SHOPLINE, WooCommerce, CSV/import-compatible, or MCP/CLI workflows, and treat custom/advanced platforms as planning-only until an adapter is attached.
  • ecommerce agentic commerce mcp — Use when a merchant or builder wants Storefront MCP, agentic shopping, catalog search, cart/checkout handoff, order lookup capability checks, or Shopify Dev MCP routing. Discovers capabilities first and only treats non-core platforms as executable after a matching connector is attached.
  • ecommerce catalog builder — Use when a merchant wants to add, clean up, rewrite, or SEO-optimize ecommerce products, variants, SKUs, collections, tags, and product import rows. Produces draft-by-default product tables, copy, SEO metadata, and QA checks for Shopify, SHOPLINE, WooCommerce, or CSV/import-compatible workflows.