What problem does it solve? Node.js developers using the Cacheable ecosystem often misuse TTL semantics, stale API patterns, or misconfigure L1/L2 stores, tags, and distributed sync, leading to subtle caching bugs in production. ## Core Features & Use Cases - L1/L2 Cache Setup: Configures Cacheable with memory primary and Redis/Valkey secondary stores, including TTL shorthand, maxTtl caps, and nonBlocking modes. - Cache Patterns: Covers wrap/memoize, getOrSet cache-aside, tag-based invalidation, hooks, events, and instance statistics. - Ecosystem Guidance: Provides package selection across cacheable, cache-manager, @cacheable/memory, and Keyv storage adapters, plus production pitfalls like undefined misses and shared-store clear() hazards. - Use Case: When adding Redis-backed caching to an Express or NestJS service, use this Skill to generate correct Cacheable configuration with tag invalidation and error event handling. ## Quick Start Ask the AI to set up a Cacheable instance with in-memory L1 and Redis L2 storage including TTL defaults and tag invalidation for your Node.js service.