Agent Skills

saleor-storefront

backendsaleor2K installs

Saleor e-commerce API patterns for building storefronts. Use when working with Saleor's GraphQL API, products, variants, checkout, channels, permissions, or debugging API behavior. Framework-agnostic — applies to any Saleor storefront.

Install

npx skills add https://github.com/saleor/agent-skills --skill saleor-storefront
SKILL.md

Saleor Storefront

Universal guide for building storefronts on the Saleor e-commerce platform. Covers the Saleor GraphQL API data model, permission system, checkout lifecycle, channel architecture, and product/variant patterns. Framework-agnostic — these rules apply whether you're using Next.js, Remix, Nuxt, or a custom setup.

When to Apply

Reference these guidelines when:

  • Querying Saleor's GraphQL API for products, categories, or collections
  • Building product detail pages with variant selection
  • Implementing checkout and payment flows
  • Working with multi-channel and multi-currency setups
  • Debugging "product not purchasable" or permission errors
  • Working with Saleor 3.23+ stock availability modes (useLegacyShippingZoneStockAvailability)
  • Investigating Saleor API behavior via source code

Rule Categories

Priority Category Impact Prefix
1 API CRITICAL api-
2 Products HIGH products-
3 Checkout HIGH checkout-
4 Channels MEDIUM channels-

Quick Reference

1. API (CRITICAL)

  • api-data-model — Nullable fields, pricing structure, automatic storefront filtering
  • api-permissions — Token types, permission errors, two-tier query pattern
  • api-graphql-patterns — Channel-scoped queries, variant attributes, filtering, codegen
  • api-investigation — How to investigate Saleor API behavior via types and source

2. Products (HIGH)

  • products-variants — Variant model, selection vs non-selection attributes, pricing, UX patterns

3. Checkout (HIGH)

  • checkout-lifecycle — Session lifecycle, common errors, debugging payment issues

4. Channels (MEDIUM)

  • channels-purchasability — Stock availability modes (legacy vs direct, 3.23+), purchasability vs shippability, fulfillment triangle, mode-aware checklists, channel-scoped queries, stock webhooks

How to Use

Read individual rule files for detailed explanations and code examples:

rules/api-data-model.md
rules/products-variants.md

Each rule file contains:

  • Brief explanation of why it matters
  • Code examples (correct and incorrect patterns)
  • Anti-patterns to avoid

Full Compiled Document

For the complete guide with all rules expanded: AGENTS.md

Related skills

entra-app-registrationmicrosoft606KGuides Microsoft Entra ID app registration, OAuth 2.0 authentication, and MSAL integration. USE FOR: create app registration, register Azure AD app, configure OAuth, set up authentication, add API permissions, generate service principal, MSAL example, console app auth, Entra ID setup, Azure AD authentication. DO NOT USE FOR: Key Vault secrets (use azure-keyvault-expiration-audit), general Azure resource security guidance.azure-messagingmicrosoft595KTroubleshoot and resolve issues with Azure Messaging SDKs for Event Hubs and Service Bus. Covers connection failures, authentication errors, message processing issues, and SDK configuration problems. WHEN: event hub SDK error, service bus SDK issue, messaging connection failure, AMQP error, event processor host issue, message lock lost, message lock expired, lock renewal, lock renewal batch, send timeout, receiver disconnected, SDK troubleshooting, azure messaging SDK, event hub consumer, servicentra-agent-idmicrosoft328KProvision Microsoft Entra Agent Identity Blueprints, BlueprintPrincipals, and per-instance Agent Identities via Microsoft Graph, and configure OAuth 2.0 token exchange (fmi_path, OBO, cross-tenant) including the Microsoft Entra SDK for AgentID sidecar. USE FOR: Agent Identity Blueprint, BlueprintPrincipal, agent OAuth, fmi_path token exchange, agent OBO, Workload Identity Federation for agents, polyglot agent auth, Microsoft.Identity.Web.AgentIdentities. DO NOT USE FOR: standard Entra app registsupabasesupabase298KUse when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, Queues); client libraries and SSR integrations (supabase-js, @supabase/ssr) in Next.js, React, SvelteKit, Astro, Remix; auth issues (login, logout, sessions, JWT, cookies, getSession, getUser, getClaims, RLS); Supabase CLI or MCP server; schema changes, migrations, declarative schemas, security audits, Postgres extensions (pg_graphql, pg_cron, pg_vector); deb

Search skills and MCP servers

Fuzzy search across 23,137 skills and servers