wp-project-triage 是做什麼的？
當您需要對 WordPress 倉庫（外掛、主題、區塊主題、WordPress 核心、Gutenberg、完整網站）進行確定性檢查時使用。這包括檢查工具、測試與版本提示，並產出結構化的 JSON 報告來引導工作流程與防護措施。
用於對 WordPress 倉庫（外掛、主題、區塊主題、WordPress 核心、Gutenberg、完整網站）進行確定性檢查，包含工具、測試與版本提示，並產出結構化的 JSON 報告來引導工作流程與防護措施。
這項技能提供一個自動化的 WordPress 專案分類工具，可對任何 WordPress 相關的 Git 倉庫進行深入分析。它會判斷專案類型（如外掛、主題、區塊主題、WordPress 核心、Gutenberg 或完整網站），並掃描專案中的建置工具、測試框架以及相關的版本資訊。技能的最終產出是一個結構化的 JSON 報告，該報告能為 CI/CD 流程、開發工作流程或 AI 代理（如 Claude Code、Cursor 或 Codex）提供明確的防護措施與引導。此技能支援所有主要的 WordPress 生態系統專案，並採用確定性檢查方式，確保每次分析都能產出一致且可靠的結果，避免依賴猜測或不穩定的啟發式方法。
npx skills add https://github.com/wordpress/agent-skills/tree/main/skills/wp-project-triage當您需要對 WordPress 倉庫（外掛、主題、區塊主題、WordPress 核心、Gutenberg、完整網站）進行確定性檢查時使用。這包括檢查工具、測試與版本提示，並產出結構化的 JSON 報告來引導工作流程與防護措施。
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 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 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".