Help us improve
Share bugs, ideas, or general feedback.
From saleor-configurator
Provides pre-built YAML config.yml templates for fashion, electronics, and subscription e-commerce stores in Saleor. Copy, customize, and deploy for quick setup from examples.
npx claudepluginhub saleor/configurator --plugin saleor-configuratorHow this skill is triggered — by the user, by Claude, or both
Slash command
/saleor-configurator:configurator-recipesThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Recipes are ready-to-use `config.yml` templates for common store types. Pick one that matches your business, customize it, and deploy. They save you from building your store configuration from scratch.
Details Saleor entities (Products, Variants, Channels, Attributes), relationships, identifier rules (slug vs name), and Configurator scope. For entity structure and connection questions.
Builds Next.js storefronts for Saleor with GraphQL client setup (urql/Apollo), channel routing, Tailwind CSS, server components, checkout flow, and SEO.
Provides best practices, UI/UX patterns, and guidance for ecommerce storefronts: checkout, cart, products, navigation, homepage. Integrates Medusa backend; framework-agnostic (Next.js, React, Vue).
Share bugs, ideas, or general feedback.
Recipes are ready-to-use config.yml templates for common store types. Pick one that matches your business, customize it, and deploy. They save you from building your store configuration from scratch.
configurator-cli insteadproduct-modeling instead| Recipe | Best For | Key Features |
|---|---|---|
| Fashion Store | Apparel, shoes, accessories | Size/color variants, seasonal collections, multi-currency |
| Electronics Store | Tech products, gadgets | Specs attributes, storage/RAM variants, warranty info |
| Subscription Service | Recurring products, SaaS | Plan tiers, billing cycles, add-on services |
For a blank starting point (correct structure, no business content), use /configurator init.
# Option 1: Interactive wizard
/recipe
# Option 2: Copy a template directly
cp plugin/skills/configurator-recipes/templates/fashion-store.yml config.yml
# Option 3: Customize and deploy
npx configurator deploy --url=$URL --token=$TOKEN
A complete configuration for apparel and fashion retail with two channels (US/EU), five product types, a full category tree, and curated collections.
Channels: US Store (USD), EU Store (EUR)
Product Types: T-Shirt, Pants, Dress, Shoes, Accessory -- each with appropriate size/color/material variants.
Categories:
Clothing → Men's (T-Shirts, Pants, Shoes) / Women's (Dresses, Tops, Shoes) / Accessories (Bags, Jewelry)
Collections: New Arrivals, Best Sellers, Sale Items, Seasonal Collection
Attributes: Size (XS-XXL), Color (swatches), Material, Brand, Care Instructions
See templates/fashion-store.yml for the complete configuration.
Electronics Store -- Single channel (USD), product types for Smartphones, Laptops, Tablets, Accessories, and Software. Attributes include Brand, Storage, RAM, Screen Size, and Warranty. See templates/electronics-store.yml.
Subscription Service -- Subscription portal channel, product types for Monthly/Annual subscriptions, One-Time Purchases, and Add-Ons. Attributes include Plan Tier, Billing Cycle, User Limit, and Storage Limit. See templates/subscription-service.yml.
After copying a recipe:
| Mistake | Fix |
|---|---|
| Using a recipe without customizing identifiers | Update all slugs and names to match your brand before deploying |
| Not adjusting currency/country codes | Change currencyCode and defaultCountry to your actual markets |
| Deploying a recipe straight to production | Always test on a staging instance first |
| Keeping entity types you don't need | Remove unused product types, categories, etc. to keep your config clean |
| Forgetting to update channel references | Products reference channels by slug -- make sure they match after renaming |
A recipe template should follow this structure:
# Recipe: [Business Type] Store
# Description: [What this recipe sets up]
# Customize: [List key things users should change]
channels:
- name: "Main Store" # ← User should rename
slug: "main" # ← User should update
currencyCode: USD # ← User should set region
defaultCountry: US
isActive: true
productTypes:
# Each type should have a comment explaining its purpose
- name: "[Type Name]"
isShippingRequired: true
productAttributes: [...]
variantAttributes: [...]
categories:
# Keep hierarchy to 3 levels max
- name: "[Root Category]"
slug: "[root-slug]"
subcategories: [...]
Every recipe must include:
# 1. Deploy to a fresh Saleor instance
npx configurator deploy --url=$STAGING_URL --token=$STAGING_TOKEN
# 2. Verify idempotency (second deploy should show no changes)
npx configurator deploy --url=$STAGING_URL --token=$STAGING_TOKEN
# 3. Introspect and diff to confirm round-trip fidelity
npx configurator introspect --url=$STAGING_URL --token=$STAGING_TOKEN --config=introspected.yml
npx configurator diff --url=$STAGING_URL --token=$STAGING_TOKEN
configurator-schema - Config.yml structure and validation rulesproduct-modeling - Product type design and attribute selectionsaleor-domain - Entity relationships and Saleor concepts