메뉴
Redis from PHP — caching, sessions, rate limiting, locks, queues/streams, pub/sub, sorted-set patterns, TTL/eviction. Use when adding Redis to a feature, designing key schemes, or fixing cache correctness/stampede issues.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | php-redis-specialist |
| description | Redis from PHP — caching, sessions, rate limiting, locks, queues/streams, pub/sub, sorted-set patterns, TTL/eviction. Use when adding Redis to a feature, designing key schemes, or fixing cache correctness/stampede issues. |
Prefer the phpredis extension (perf); Predis when a pure-PHP client is required.
Cache-aside with explicit TTLs by default. Prevent stampedes (locks, request coalescing, probabilistic early expiry). Every cached key needs a clear invalidation rule. No TTL-less caching without an explicit invalidation path. Distinguish cache (reconstructable) from source of truth (needs persistence/replication).
Namespaced, colon-delimited (svc:entity:id:field). Small values. Pick the right structure (String/Hash/Set/ZSet/List/Stream/Bitmap/HLL) per access pattern — don't serialize blobs everywhere.
Lua (EVAL/EVALSHA) or MULTI/WATCH for read-modify-write. Locks: SET NX PX with unique token, release via Lua compare-and-delete. Redlock only when multi-node correctness demands it (note caveats).
Token-bucket/sliding-window as an atomic Lua script. Prefer Redis Streams + consumer groups over LIST queues when you need acks/retries/at-least-once.
Choose maxmemory-policy deliberately (allkeys-lru for pure cache, noeviction for datastore/queue). Use SCAN not KEYS. Mind pipelining, pconnect, and serialization cost. Always state the failure mode (miss, Redis down, stale data).
Apache2 (httpd) configuration and ops for PHP services — vhosts, MPM tuning, PHP-FPM via mod_proxy_fcgi, mod_rewrite, TLS/HTTP2, compression/caching, hardening, and diagnosing 5xx/perf issues. Use for web-server config, deployment topology, and Apache performance/security.
Test automation strategy and engineering across the pyramid — unit, integration, API/contract, and end-to-end. Use for designing a test strategy, building API/E2E suites, CI test pipelines, fixtures/factories, flake reduction, and coverage of a REST microservice. Complements phpunit-testing for cross-cutting and higher-level testing.
MySQL schema design, indexing, and query tuning. Use when modeling tables, choosing types/keys, writing or optimizing SQL, reading EXPLAIN output, or resolving slow queries, deadlocks, and transaction issues.
Modern PHP 8.4/8.5 authoring and review. Use when writing idiomatic typed PHP, applying new language features, migrating older code, or resolving type/strictness issues. State the minimum PHP version any recent feature requires.
PHP performance — profiling, removing hotspots, cutting latency/memory, OPcache/JIT/preloading, eliminating N+1, efficient structures, generators/streaming, connection reuse, benchmarking. Use when something is slow or memory-heavy, or to validate an optimization. Measure first.
Defensive application security for PHP/web services — secure coding review, input validation, authn/authz, session/token security, injection/XSS/CSRF/SSRF/IDOR/deserialization defenses, secrets, and crypto. Use for security reviews and security-sensitive design. Defensive use only.
