What problem does it solve?
This Skill solves the performance and rate-limit problems of headless VTEX storefronts by guiding which VTEX API responses can be safely cached and how to keep them fresh without risking transactional or personal data leakage.
Core Features & Use Cases
- Cacheable vs non-cacheable API guidance: Defines what must be cached (public, read-only like Intelligent Search and catalog) and what must never be cached (Checkout, Profile, OMS, Payments, pricing private).
- Stale-while-revalidate (SWR) freshness model: Recommends serving cached data immediately while refreshing in the background for better perceived performance.
- TTL + invalidation strategy: Proposes bounded TTLs (typically 2–15 minutes) and event-driven or manual invalidation so catalog and availability changes propagate in time.
Quick Start
Ask an AI to design your headless VTEX caching plan so Intelligent Search and Catalog are cached safely with SWR, while Checkout and other sensitive endpoints are explicitly marked as no-cache.