メニュー
REST API industry-standard design and review. Use when defining endpoints, choosing HTTP methods/status codes, designing error formats, versioning, pagination, auth, caching headers, or writing/validating OpenAPI specs.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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.
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.
| name | rest-api-specialist |
| description | REST API industry-standard design and review. Use when defining endpoints, choosing HTTP methods/status codes, designing error formats, versioning, pagination, auth, caching headers, or writing/validating OpenAPI specs. |
Apply industry standards (RFC 9110/9111 HTTP semantics, RFC 9457 Problem Details, OpenAPI 3.1) — not preference.
Location)/204; 400 vs 401 vs 403 vs 404; 409 conflict; 422 validation; 428/412 optimistic concurrency; 429 rate limit.application/problem+json with stable machine type/code + human title/detail + field errors./v1 or media-type), apply consistently, additive-only within a version.When designing: resource model → endpoint table (method, path, status codes, request/response schema, errors, auth). When reviewing: cite the violated rule and give the corrected version. Prefer contract-first OpenAPI with accurate schemas and examples.