saleor-storefront
Audited by Runlayer on Feb 23, 2026
Malicious tool definition detected
Tool: AGENTS.md [1/4] Description: # Saleor Storefront **Version 1.0.0** Saleor February 2026 > **Note:** > This document is mainly for agents and LLMs to follow when building, > maintaining, or debugging Saleor-powered storefronts. Humans may also > find it useful, but guidance here is optimized for AI-assisted workflows.
Tool: AGENTS.md [2/4] Description: cookies leak into cached responses - No "Signature has expired" errors on public pages ## Anti-patterns ❌ **Don't request `MANAGE_*` fields in storefront queries** — They'll fail for customers ❌ **Don't use staff tokens in production storefronts** — Use app tokens instead ❌ **Don't cache authenticated queries** — User-specific data must be fresh ❌ **Don't mix public and authenticated data in a single cached response** ### 1.3 GraphQL Patterns Common patterns an
Tool: AGENTS.md [3/4] Description: > **For schema types**, prefer your generated types file first. It contains the full Saleor schema as TypeScript types, generated via API introspection.
Tool: AGENTS.md [4/4] Description: cart - No valid checkout ID exists in storage - Existing checkout is not found in Saleor (expired/deleted) ### Completion When `checkoutComplete` succeeds: - Checkout is converted to an Order - The checkout ID becomes invalid - A new checkout must be created for future purchases ## Common Errors ### "CHECKOUT_NOT_FULLY_PAID" ``` The authorized amount doesn't cover the checkout's total amount. ``` **Causes**: 1.
Malicious tool definition detected
Tool: README.md Description: # Saleor Storefront Skill Universal agent skill for building storefronts on the [Saleor](https://saleor.io) e-commerce platform.
Malicious tool definition detected
Tool: SKILL.md Description: --- name: saleor-storefront description: > Saleor e-commerce API patterns for building storefronts.
Malicious tool definition detected
Tool: references/saleor-key-directories.md Description: # Saleor Core Key Directories Reference for navigating the Saleor source code when investigating API **behavior** (permission checks, filtering logic, side effects).
Malicious tool definition detected
Tool: rules/api-data-model.md Description: # Saleor API Data Model Understanding Saleor's data model quirks — nullable fields, pricing structure, and automatic storefront filtering — prevents bugs and wasted debugging time.
Malicious tool definition detected
Tool: rules/api-graphql-patterns.md Description: # Saleor GraphQL Patterns Common patterns and gotchas when writing GraphQL queries against the Saleor API.
Malicious tool definition detected
Tool: rules/api-investigation.md Description: # Saleor API Investigation How to investigate Saleor API behavior when documentation is unclear or you need to understand exact data models, permission checks, or filtering logic.
Malicious tool definition detected
Tool: rules/api-permissions.md Description: # Saleor API Permissions Understanding how Saleor's permission model works prevents "Permission denied" errors and ensures your storefront queries only request data they're authorized to access.
Malicious tool definition detected
Tool: rules/channels-purchasability.md Description: # Saleor Channels & Purchasability Understanding Saleor's channel model and the "fulfillment triangle" is essential for debugging why products appear unavailable or can't be purchased.
Malicious tool definition detected
Tool: rules/checkout-lifecycle.md Description: # Saleor Checkout Lifecycle Understanding how Saleor checkout sessions work — creation, persistence, completion, and common failure modes — prevents payment errors and lost orders.
Malicious tool definition detected
Tool: rules/products-variants.md Description: # Saleor Products & Variants Understanding Saleor's product-variant model is essential for building product detail pages, cart operations, and filtering.