wp-project-triage 是做什么的？
当您需要对WordPress仓库（插件/主题/区块主题/WP核心/Gutenberg/完整站点）进行确定性检查时使用，包括工具链/测试/版本提示，以及用于指导工作流程和防护措施的结构化JSON报告。
用于对WordPress仓库（插件/主题/区块主题/WP核心/Gutenberg/完整站点）进行确定性检查，包括工具/测试/版本提示，并生成结构化JSON报告以指导工作流程和防护措施。
该技能（wordpress/wp-project-triage）旨在为开发者或AI代理提供对WordPress项目仓库的深度确定性检查。它能够自动识别仓库类型（如插件、主题、区块主题、WordPress核心、Gutenberg或完整站点），并分析其中的工具链、测试配置以及版本信息。最终生成一个结构化的JSON报告，为后续的工作流程（如部署、测试、代码审查）提供清晰的指导和约束条件（guardrails）。该技能适用于任何基于WordPress的代码仓库，特别适合在CI/CD管道或AI辅助开发环境中使用，以确保对项目状态的准确理解并避免配置错误。通过系统化扫描文件结构、配置文件（如package.json、composer.json）和关键的WordPress文件（如style.css、plugin.php），它能够快速提供可靠的元数据，减少人工检查和误判。
npx skills add https://github.com/wordpress/agent-skills/tree/main/skills/wp-project-triage当您需要对WordPress仓库（插件/主题/区块主题/WP核心/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".