skills/saleor-paper-storefront/SKILL.md
Project-specific patterns for the Saleor Paper storefront built with Next.js 16, TypeScript, and Tailwind CSS. Use when working with product pages, checkout flow, caching, variant selection, filtering, SEO, or UI components. For universal Saleor API patterns, see the saleor-storefront dependency.
npx skillsauth add saleor/storefront saleor-paper-storefrontInstall 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.
Project-specific guide for the Saleor Paper storefront — a Next.js 16 e-commerce application with TypeScript, Tailwind CSS, and the Saleor GraphQL API. Contains 11 rules across 6 categories covering caching, PDP architecture, checkout components, UI patterns, and SEO.
Prerequisite: This skill depends on
saleor-storefrontfor universal Saleor API knowledge (data model, permissions, checkout lifecycle, channels). Install it alongside this skill.
Reference these guidelines when:
| Priority | Category | Impact | Prefix |
| -------- | ------------- | -------- | ----------- |
| 1 | Data Layer | CRITICAL | data- |
| 2 | Product Pages | HIGH | product- |
| 3 | Checkout Flow | HIGH | checkout- |
| 4 | UI & Channels | MEDIUM | ui- |
| 5 | SEO | MEDIUM | seo- |
| 6 | Development | MEDIUM | dev- |
data-caching - Cache Components (PPR), cache tags, revalidation, price flowdata-graphql - Two codegen setups, permission patterns, nullable fieldsproduct-pdp - PDP architecture, gallery, data flow, add-to-cart, ErrorBoundaryproduct-variants - Variant selection state machine, option states, discount badgesproduct-filtering - Server vs client filtering, category slug resolutioncheckout-management - Checkout lifecycle, cookie storage, payment debuggingcheckout-components - Reusable checkout UI (SignInForm, AddressSelector, PaymentMethodSelector)ui-components - Design tokens, shadcn/ui primitives, component locationsui-channels - Multi-channel URLs, fulfillment model, purchasability debugging, channel selectorseo-metadata - JSON-LD structured data, metadata helpers, OG image generationdev-investigation - Saleor API source code investigation methodologyRead individual rule files for detailed explanations and code examples:
rules/data-caching.md
rules/product-variants.md
Each rule file contains:
For the complete guide with all rules expanded: AGENTS.md
development
Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.
development
Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.
development
Run, watch, debug, and extend OpenClaw QA testing with qa-lab and qa-channel. Use when Codex needs to execute the repo-backed QA suite, inspect live QA artifacts, debug failing scenarios, add new QA scenarios, or explain the OpenClaw QA workflow. Prefer the live OpenAI lane with regular openai/gpt-5.4 in fast mode; do not use gpt-5.4-pro or gpt-5.4-mini unless the user explicitly overrides that policy.
development
End-to-end Parallels smoke, upgrade, and rerun workflow for OpenClaw across macOS, Windows, and Linux guests. Use when Codex needs to run, rerun, debug, or interpret VM-based install, onboarding, gateway smoke tests, latest-release-to-main upgrade checks, fresh snapshot retests, or optional Discord roundtrip verification under Parallels.