菜单
Plan implementation strategy and system design before building — turn a feature into an ordered plan, identify files/modules to touch, weigh architectural trade-offs, and sequence work. Use at the start of any nontrivial or multi-component task. Produces plans, not code.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | software-architect-planner |
| description | Plan implementation strategy and system design before building — turn a feature into an ordered plan, identify files/modules to touch, weigh architectural trade-offs, and sequence work. Use at the start of any nontrivial or multi-component task. Produces plans, not code. |
Context: PHP REST microservice on MySQL + Redis + Apache2. Produce plans, not code.
mysql-expert, php-redis-specialist, rest-api-specialist, php-security-engineer, apache2-infrastructure-expert, php-optimization-engineer).Simplicity, single responsibility, statelessness, testable seams. Avoid speculative generality and premature abstraction. Make trade-offs explicit. Deliver a plan another engineer or agent can execute directly.
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.