wp-plugin-development 是做什麼的？
用於開發 WordPress 外掛：架構與鉤子、啟用/停用/解除安裝、管理介面與設定 API、資料儲存、排程/任務、安全性（nonce/權限/清理/跳脫），以及發布封裝。
用於開發 WordPress 外掛：架構與鉤子、啟用/停用/解除安裝、管理介面與設定 API、資料儲存、排程/任務、安全性（nonce/權限/清理/跳脫），以及發布封裝。
這是一個專為開發 WordPress 外掛而設計的 AI 代理技能。它涵蓋了外掛開發的各個關鍵面向，包括整體架構設計、使用動作和過濾器（hooks）進行擴展、外掛啟用/停用/解除安裝的標準實作、建立管理後台 UI 以及利用 Settings API 管理設定、資料儲存方式（如選項、自訂文章型別、資料表）、排程與背景任務（Cron）、安全性措施（nonce、權限檢查、資料清理與跳脫），以及最終的發布封裝流程。此技能適用於 Claude Code、Cursor 等 AI 代理平台，能引導開發者遵循 WordPress 最佳實務，確保外掛的穩定性、安全性和可維護性。透過結構化的指引，它幫助開發者快速產出高品質的 WordPress 外掛程式碼。
npx skills add https://github.com/wordpress/agent-skills/tree/main/skills/wp-plugin-development用於開發 WordPress 外掛：架構與鉤子、啟用/停用/解除安裝、管理介面與設定 API、資料儲存、排程/任務、安全性（nonce/權限/清理/跳脫），以及發布封裝。
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 when configuring, running, or fixing PHPStan static analysis in WordPress projects (plugins/themes/sites): phpstan.neon setup, baselines, WordPress-specific typing, and handling third-party plugin classes.
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 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.
ElevenLabs text-to-speech with mac-style say UX.
Oracle CLI second-model review/debug/refactor/design with selected files, dry-run token checks, API or browser engine.
Capture and automate macOS UI with the Peekaboo CLI.
Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".
Build a throwaway prototype to flesh out a design — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".