Caching

Automatic project context detection with priority-based resolution (Manual setting → Git remote → Subdirectory pattern → Local path → Custom patterns). Auto-activates at start of every CCPM command to ensure correct project context. Supports monorepos with subdirectory detection using glob patterns and priority weighting. Handles ambiguous detection (multiple matches) by asking user to clarify. Caches detection result for command duration (fast reuse). Provides clear error messages with actionable suggestions when no project detected. Displays project context in command headers (e.g., "📋 Project: My Monorepo › frontend"). Supports auto-detection mode (cd = switch) or manual setting (stable context across sessions). Performance: <100ms for auto-detection, 0ms for manual.

Use when configuring CDN for media delivery, implementing cache invalidation, or designing signed URL patterns. Covers CDN configuration, edge caching, origin shielding, and secure media access for headless CMS.

Review Next.js App Router code for optimal Partial Prerendering (PPR), caching strategy, Suspense boundaries, and React Query integration. Ensure adherence to Next.js 16+ Cache Components best practices.

Development: Cleanup and maintenance for the development environment.Removes build artifacts, caches, containers, and recovers disk space.Run from repository root with 'just clean'. Use when developers needto free disk space or reset the build environment.

Use when designing content delivery networks, caching strategies, or global content distribution. Covers CDN architecture, cache hierarchies, origin shielding, cache invalidation, and edge optimization.

Use when working with WP-CLI for WordPress operations: safe search-replace, db export/import, plugin/theme management, cron, cache flushing, multisite, and automation with wp-cli.yml.

Synchronize memories between Turso (durable) and redb (cache) storage layers. Use when cache appears stale, after failures, or during periodic maintenance.

Local Podman registry mirror management. Cache container images locally forfaster pulls. Supports any registry (ghcr.io, docker.io, private). Use whenusers need to set up registry mirrors for faster container operations.

This skill enables Claude to analyze and improve application caching strategies. It optimizes cache hit rates, TTL configurations, cache key design, and invalidation strategies. Use this skill when the user requests to "optimize cache performance", "improve caching strategy", "analyze cache hit rate", or needs assistance with "cache key design", "TTL optimization", or "cache invalidation". The skill identifies potential bottlenecks and recommends adjustments for improved performance and efficiency of caching mechanisms like Redis.

This skill automates the API-first workflow for creating new Go API endpoints. It handles OpenAPI spec updates, code generation, SQLC query creation, handler implementation, and Redis caching patterns. Use when adding new endpoints to the Lexicon backend.

This skill enables Claude to analyze and improve application caching strategies. It optimizes cache hit rates, TTL configurations, cache key design, and invalidation strategies. Use this skill when the user requests to "optimize cache performance", "improve caching strategy", "analyze cache hit rate", or needs assistance with "cache key design", "TTL optimization", or "cache invalidation". The skill identifies potential bottlenecks and recommends adjustments for improved performance and efficiency of caching mechanisms like Redis.

Full SDK integration test that runs actual queries through the Claude SDK sandbox. Use after making changes to SDK client code, session management, skill loading, network proxy, voice/TTS, or image generation. Runs real prompts through the SDK to verify the complete path works.

HTTPプロトコルの仕様に基づき、RESTful APIおよびWebサービス実装における通信設計を提供。ステータスコード、ヘッダー、キャッシュ、冪等性設計を網羅。Anchors:• HTTP/2 in Action (Barry Pollard) / 適用: プロトコル仕様・パフォーマンス / 目的: 効率的なHTTP通信• RESTful Web Services (Richardson, Ruby) / 適用: REST設計原則 / 目的: 一貫したAPI設計• Web API Design (Brian Mulloy) / 適用: 実践的なAPI設計パターン / 目的: 使いやすいAPITrigger:Use when designing REST APIs, implementing HTTP clients, configuring cache strategies, setting security headers, or ensuring idempotency.http, rest api, status codes, cache-control, cors, idempotency, headers, http/2, keep-alive

Reactアプリのデータフェッチ、キャッシュ、エラーハンドリング、楽観的更新を整理するスキル。ライブラリ選定から設計・実装・検証までの実務フローを提供する。Anchors:• Stale-While-Revalidate Pattern / 適用: キャッシュ戦略 / 目的: サーバー状態の一貫性確保• React Query vs SWR / 適用: ライブラリ選定 / 目的: 要件に最適な選択• MSW / 適用: テスト環境構築 / 目的: API依存の排除Trigger:Use when implementing data fetching patterns, cache strategies, error handling, optimistic updates, or choosing between SWR and React Query.data fetching, cache strategy, swr, react query, optimistic updates, error handling

This skill enables Claude to implement multi-tier database caching solutions. It is triggered when the user requests database caching, performance improvements, or reduced database load. The skill utilizes Redis, in-memory caching, and CDN layers to optimize database performance by reducing database load, improving query latency, and supporting horizontal scaling with cache-aside, write-through, and read-through patterns. Use this skill when the user mentions terms like "database caching", "improve database performance", "reduce database load", or uses the `/caching` command.

GitHub Actions の実行コストを最適化するためのスキル。コスト計測、削減施策の設計、実装、継続的な監視を一連で扱う。Anchors:• High Performance Browser Networking / 適用: 計測から改善する姿勢 / 目的: 速度とコストの可視化• Designing Data-Intensive Applications / 適用: 制約下の設計判断 / 目的: ランナー/ストレージの効率化• Continuous Delivery / 適用: 改善の反復 / 目的: 継続的最適化のサイクル化Trigger:Use when optimizing GitHub Actions workflow execution time, reducing runner costs, managing billing, or optimizing artifact storage and cache usage.github actions cost optimization, runner costs, workflow budget, artifact storage, caching strategy

API rate limiting and quota management implementation. Use when implementing request throttling, API quotas, backpressure handling, or protection against abuse. Keywords: rate limiting, throttling, token bucket, sliding window, leaky bucket, quota, Redis, backpressure, API limits, DDoS protection.

GitHub ActionsでのDockerビルド/プッシュを設計・実装するスキル。レジストリ認証、キャッシュ戦略、マルチプラットフォーム対応を整理する。Anchors:• docker/build-push-action / 適用: ビルドとプッシュ / 目的: 自動化• BuildKit / 適用: キャッシュ最適化 / 目的: ビルド高速化• Registry Authentication / 適用: 認証設計 / 目的: 安全な配布Trigger:Use when configuring GitHub Actions for Docker build and push, managing registry auth, or optimizing BuildKit cache.docker build push action, buildx, registry auth, github actions docker

Seed JSON configuration files into database. Use ONCE at BAZINGA session initialization, BEFORE spawning PM.

This skill enables Claude to implement multi-tier database caching solutions. It is triggered when the user requests database caching, performance improvements, or reduced database load. The skill utilizes Redis, in-memory caching, and CDN layers to optimize database performance by reducing database load, improving query latency, and supporting horizontal scaling with cache-aside, write-through, and read-through patterns. Use this skill when the user mentions terms like "database caching", "improve database performance", "reduce database load", or uses the `/caching` command.