caching-strategy

What problem does it solve?

Cache expensive operations to avoid redundant work across workflow phases. Caches project docs (15min TTL), npm info (60min), grep results (30min), token counts (until file modified), web searches (15min). Auto-triggers when detecting repeated reads of same files or repeated API calls. Saves 20-40% execution time.

Core Features & Use Cases

• File read cache: Cache file contents until the file is modified.
• Search result cache: Cache grep/glob results for quick reuse.
• Network request cache: Cache npm/web API calls for common packages.
• Computed value cache: Cache expensive calculations until inputs change.
• Automatic invalidation: TTL expiration and file-mod time checks.
• Result: 20-40% faster workflow execution with zero behavioral changes.

Quick Start

1. Identify cacheable operations: idempotent reads, repeated patterns, repeated API calls, and expensive computations.
2. Generate a unique cache key per operation (e.g., file:, grep:, npm:, web:).
3. Implement caching with TTLs and invalidation rules.
4. Validate cache hits/misses and monitor performance improvements.