wp-phpstan 是做什麼的？
用於在 WordPress 專案（外掛、主題、網站）中設定、執行或修復 PHPStan 靜態分析：phpstan.neon 設定、基準線、WordPress 特定型別以及處理第三方外掛類別。
用於在 WordPress 專案（外掛、主題、網站）中設定、執行或修復 PHPStan 靜態分析：phpstan.neon 設定、基準線、WordPress 特定型別以及處理第三方外掛類別。
此技能專注於在 WordPress 專案中配置和使用 PHPStan 靜態分析工具。它涵蓋了從建立 phpstan.neon 設定檔、生成基準線（baseline）以抑制現有錯誤，到處理 WordPress 特有的型別系統（例如 `WP_Post`、`WP_Query`）以及解決第三方外掛和主題中類別無法解析的問題。對於希望透過靜態分析提升程式碼品質、減少潛在錯誤並改善型別安全性的 WordPress 開發者來說，這項技能特別實用。它支援在任何 WordPress 專案目錄中使用，並依賴 PHPStan 和相關的 WordPress 擴充套件（如 phpstan-wordpress）來提供準確的分析結果。
npx skills add https://github.com/wordpress/agent-skills/tree/main/skills/wp-phpstanInstalled? Explore more 研究與資料分析 skills: affaan-m/uspto-database, affaan-m/scholar-evaluation, affaan-m/literature-review · View all 6 →
用於在 WordPress 專案（外掛、主題、網站）中設定、執行或修復 PHPStan 靜態分析：phpstan.neon 設定、基準線、WordPress 特定型別以及處理第三方外掛類別。
This repo contains 13 individual skills — each has its own dedicated page.
Use when creating, editing, or reviewing WordPress Playground blueprint JSON files. Triggers on mentions of blueprints, playground configuration, or requests to set up a WordPress demo environment.
Use when the user asks about WordPress codebases (plugins, themes, block themes, Gutenberg blocks, WP core checkouts) and you need to quickly classify the repo and route to the correct workflow/skill (blocks, theme.json, REST API, WP-CLI, performance, security, testing, release packaging).
Use when working with the WordPress Abilities API (wp_register_ability, wp_register_ability_category, /wp-json/wp-abilities/v1/*, @wordpress/abilities) including defining abilities, categories, meta, REST exposure, and permissions checks for clients.
Use when developing WordPress (Gutenberg) blocks: block.json metadata, register_block_type(_from_metadata), attributes/serialization, supports, dynamic rendering (render.php/render_callback), deprecations/migrations, viewScript vs viewScriptModule, and @wordpress/scripts/@wordpress/create-block build and test workflows.
Use when developing WordPress block themes: theme.json (global settings/styles), templates and template parts, patterns, style variations, and Site Editor troubleshooting (style hierarchy, overrides, caching).
Use when building UIs leveraging the WordPress Design System (WPDS) and its components, tokens, patterns, etc.
Use when building or debugging WordPress Interactivity API features (data-wp-* directives, @wordpress/interactivity store/state/actions, block viewScriptModule integration, wp_interactivity_*()) including performance, hydration, and directive behavior.
Use when investigating or improving WordPress performance (backend-only agent): profiling and measurement (WP-CLI profile/doctor, Server-Timing, Query Monitor via REST headers), database/query optimization, autoloaded options, object caching, cron, HTTP API calls, and safe verification.
Use for WordPress Playground workflows: fast disposable WP instances in the browser or locally via @wp-playground/cli (server, run-blueprint, build-snapshot), auto-mounting plugins/themes, switching WP/PHP versions, blueprints, and debugging (Xdebug).
Use when developing WordPress plugins: architecture and hooks, activation/deactivation/uninstall, admin UI and Settings API, data storage, cron/tasks, security (nonces/capabilities/sanitization/escaping), and release packaging.
Use when you need a deterministic inspection of a WordPress repository (plugin/theme/block theme/WP core/Gutenberg/full site) including tooling/tests/version hints, and a structured JSON report to guide workflows and guardrails.
Use when building, extending, or debugging WordPress REST API endpoints/routes: register_rest_route, WP_REST_Controller/controller classes, schema/argument validation, permission_callback/authentication, response shaping, register_rest_field/register_meta, or exposing CPTs/taxonomies via show_in_rest.
Use when working with WP-CLI (wp) for WordPress operations: safe search-replace, db export/import, plugin/theme/user/content management, cron, cache flushing, multisite, and scripting/automation with wp-cli.yml.
USPTO patent and trademark data workflow for official record lookup, PatentSearch queries, TSDR checks, assignment data, and reproducible IP research logs.
Structured scholarly-work evaluation for papers, proposals, literature reviews, methods sections, evidence quality, citation support, and research-writing feedback.
Systematic literature-review workflow for academic, biomedical, technical, and scientific topics, including search planning, source screening, synthesis, citation checks, and evidence logging.
The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
Agent skill repository discovered by 10x-chat research.
Review backend code for quality, security, maintainability, and best practices based on established checklist rules. Use when the user requests a review, analysis, or improvement of backend files (e.g., `.py`) under the `api/` directory. Do NOT use for frontend files (e.g., `.tsx`, `.ts`, `.js`). Supports pending-change review, code snippets review, and file-focused review.