skills/commercetools-merchant-center/SKILL.md
Production-tested patterns for commercetools Merchant Center custom applications, custom views, UI Kit, and deployment from a Platinum partner with 50+ live implementations.
npx skillsauth add ariessolutionsio/composable-skills commercetools-merchant-centerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Progressive loading — only load what you need:
references/custom-applications.mdreferences/custom-views.mdreferences/ui-data-fetching.mdreferences/ui-forms-components.mdreferences/deployment.md| Pattern | File | Impact |
|---------|------|--------|
| Custom Application vs Custom View | references/custom-applications.md | Wrong choice means rebuilding from scratch. Applications are full pages; Views are embedded panels. |
| Application Shell & Entry Point Config | references/custom-applications.md | Misconfigured entryPointUriPath or cloudIdentifier blocks all development. Reserved paths silently fail. |
| OAuth Scopes & Permission Model | references/custom-applications.md | Missing scopes cause 403 errors in production. Over-scoping violates least privilege. Team assignment is required. |
| Pattern | File | Impact |
|---------|------|--------|
| Custom View Panel Types & Locators | references/custom-views.md | Wrong panel size or locator means content does not display where users expect it. |
| Data Fetching with useMcQuery | references/ui-data-fetching.md | Using raw Apollo without MC context breaks authentication. Must use GRAPHQL_TARGETS. |
| Forward-To Proxy for External APIs | references/ui-data-fetching.md | Custom API integration requires /proxy/forward-to with JWT validation. Direct calls from the browser fail. |
| Form Patterns with Formik | references/ui-forms-components.md | MC SDK fields expect Formik integration. Raw form state causes validation and accessibility gaps. |
| Routing & Navigation | references/ui-forms-components.md | Must use useRouteMatch for nested routes. Hardcoded paths break across projects. |
| UI Kit Components & Design System | references/ui-forms-components.md | Ignoring ui-kit produces inconsistent UX and fails design review. |
| Pattern | File | Impact | |---------|------|--------| | Deployment to Vercel / Netlify | references/deployment.md | Missing SPA rewrites cause 404s. Wrong build command skips MC compilation. | | Deployment to commercetools Connect | references/deployment.md | connect.yaml misconfiguration blocks deployment. APPLICATION_URL is auto-provided. | | Application Registration & States | references/deployment.md | Forgetting to move from Draft to Ready means the app cannot be installed. | | Testing Custom Applications | references/deployment.md | MC-specific test utilities required for permission and context mocking. |
| Anti-Pattern | File | Consequence | |-------------|------|-------------| | Using raw Apollo instead of useMcQuery | references/ui-data-fetching.md | Breaks MC authentication context | | Calling external APIs directly from browser | references/ui-data-fetching.md | CORS failures, bypassed auth -- use Forward-To proxy | | Using raw React state instead of Formik | references/ui-forms-components.md | Validation and accessibility gaps with MC fields | | Using ApplicationShell in a Custom View | references/custom-views.md | Wrong shell -- Custom Views require CustomViewShell | | Reserved or hardcoded entryPointUriPath | references/custom-applications.md | Application silently fails to load | | Forgetting Draft-to-Ready state transition | references/deployment.md | App appears registered but cannot be installed |
Does the functionality need its own page and main menu entry?
YES --> Custom Application
NO --> Continue
Does the functionality enhance an EXISTING built-in MC page?
(e.g., extra details on an Order, Customer, or Product page)
YES --> Custom View
NO --> Continue
Does the functionality require complex multi-page navigation?
(e.g., list page, detail page, create/edit forms)
YES --> Custom Application
NO --> Continue
Is the functionality a simple panel showing contextual info or actions?
(e.g., order tracking, loyalty points, quick edits)
YES --> Custom View (narrow or extended panel)
NO --> Custom Application (default choice for standalone features)
Use this skill to DESIGN and STRUCTURE your MC extension, then use the Developer MCP for MC SDK docs and the Commerce MCP for CRUD operations.
tools
Operator-side patterns for integrating Marketplacer into a composable commerce stack — GraphQL Operator API, per-seller order splits via Invoices, caller-shaped webhooks with HMAC, MPay deposit-and-reconcile payouts, Golden Product PIM sync, wholesale orders, additional charges, and Catalog Rules. Use when implementing or maintaining a Marketplacer marketplace behind any commerce platform (commercetools, Kibo, Scayle, etc.), any search engine, any PIM, OMS, or ERP. Triggers on Marketplacer, marketplace, multi-vendor, multi-seller, Advert, Seller, Invoice, Golden Product, MPay, Airwallex, Hyperwallet, Xero, RefundRequest, RemittanceAdvice, Remittance, Taxon, Prototype, Catalog Rule, marketplace commission, marketplace fees, marketplace operator, marketplace webhooks, paymentReferences. Consult this skill before writing code that talks to a Marketplacer instance, defines a Marketplacer webhook, or maps Marketplacer data into another system.
tools
Use for Kibo Subscription Commerce work — implementing recurring billing, configuring plans (evergreen, fixed-term, subscribe-and-save), managing subscriptions (pause, skip, swap, cancel), setting up dunning / retry for failed payments, handling cycles and continuity orders, building customer self-service portals, and understanding the Subscription-to-Order relationship. Triggers on Kibo Subscription, Kibo Subscription Commerce, subscriptionCreate, subscriptionUpdate, subscription cycle, subscription pause / skip / swap, subscription dunning, recurring billing Kibo, evergreen subscription, fixed-term subscription, subscribe and save, continuity order, payment recycling, subscription churn, subscription retention. Invoke for any Kibo Subscription question — API integration, implementation, configuration, debugging, or projecting subscription state into reporting/ERP.
development
Use for Kibo Order Management (OMS) implementation — design order routing strategies (DC-to-store fallback, location-based), implement fulfillment workflows (BOPIS, curbside pickup, ship-from-store), build RMA and returns processing, integrate inventory APIs with WMS (Refresh vs Adjust semantics), set up standalone-OMS behind Shopify / SFCC / custom storefronts, or import orders from external platforms. Triggers on Kibo OMS, Kibo Order Management, Kibo fulfillment, order routing, BOPIS, ship-from-store, fulfiller, fulfillment task, RMA, Kibo returns, Kibo inventory location, Kibo dropship, Kibo carrier, agentic order routing, standalone OMS. Covers routing rules, allocation logic, carrier integration, location capabilities, and the OMS-behind-non-Kibo-storefront pattern.
tools
Build, debug, and integrate Kibo Commerce eCommerce features — implement checkout/cart/catalog flows, troubleshoot cart and promotion issues, develop B2B portals, write API Extensions (Arc.js), configure Event Subscriptions, or connect to external PIMs/OMS/search. Covers OAuth, `x-vol-tenant`/`x-vol-site`/`x-vol-master-catalog` headers, tenant/site/catalog hierarchy, `@kibocommerce/rest-sdk`, REST vs GraphQL selection. Triggers on Kibo, Kibo Commerce, KiboCommerce, KiboSoftware, x-vol-tenant, x-vol-site, MasterCatalog, Kibo cart/checkout/catalog/storefront/B2B/promotions, API Extensions, Arc.js, Event Subscription, @kibocommerce/rest-sdk. Use whenever working with Kibo's commerce platform — implementing new features, debugging existing code, or integrating external systems.