cacheable-matchers

Audit Deco storefront pages for cacheability gates in matchers and loaders.

13|2|Updated Feb 24, 2026

Search Tags:#cache #cdn #matcher #web-performance #cookies #loader #edge-caching

Ready to run

npx skills add https://github.com/decocms/storefront-skills --skill cacheable-matchers

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cacheable-matchers
Source: https://github.com/decocms/storefront-skills/tree/main/.claude-deco/skills/cacheable-matchers
Command: npx skills add https://github.com/decocms/storefront-skills --skill cacheable-matchers

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cacheability gates for pages using matchers and loaders are complex and error-prone; this skill provides a structured approach to ensure pages can be cached at the CDN edge when possible.

Core Features & Use Cases

Audits loader cache declarations to ensure public, static data can be cached, and identifies loaders that must be no-store.
Audits custom matchers to enforce cacheable = true for deterministic results, with caveats for query params and user- or geo-based variants.
Provides diagnostic guidance for preventing foreign Set-Cookies from breaking cacheability and moving personalization client-side when needed.

Quick Start

Audit a storefront page to identify cacheability gates and implement explicit cache declarations for loaders and matchers.

Frequently Asked Questions about cacheable-matchers

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I make pages using matchers and loaders cacheable at the CDN edge?▼

To make pages cacheable at the CDN edge, audit loader cache declarations and enforce cacheable flags on matchers. This ensures deterministic results are cached while preventing foreign cookies or personalization from breaking cacheability.

What is a cacheability gate for web performance and when do I need to evaluate it?▼

A cacheability gate is a condition that determines if a page can be stored at the CDN edge. You need to evaluate cacheability gates when using matchers and loaders to identify no-store requirements, cookies, and user segments that block caching.

How do I audit loader cache declarations for static versus no-store data?▼

Auditing loader cache declarations involves checking if public, static data is marked for caching and identifying loaders that must be set to no-store. This separates cacheable assets from dynamic, uncacheable user data.

Why do foreign Set-Cookie headers break HTML cacheability on storefront pages?▼

Foreign Set-Cookie headers break HTML cacheability by injecting dynamic user state into responses. Moving personalization client-side and preventing foreign cookies ensures compliant, cacheable outputs at the edge.

Can I cache matcher-enabled pages that rely on query params or geo-based variants?▼

Matcher-enabled pages using query params or geo-based variants require specific caveats for cacheability. You must enforce cacheable equals true for deterministic results while carefully handling variant-specific routing and user segments.

What are the limitations of edge caching for pages with user-based personalization?▼

Edge caching limitations occur when user-based personalization requires foreign cookies or dynamic data. Loaders must be declared no-store for user-specific segments, and personalization should be moved client-side to maintain cacheability.