Utilisez cette compétence lorsque vous avez besoin d'une inspection déterministe d'un dépôt WordPress (plugin/thème/thème bloc/WP core/Gutenberg/site complet) incluant des indices sur les outils, les tests et les versions, ainsi qu'un rapport JSON structuré pour guider les workflows et les garde-fous.
Cette compétence est conçue pour les développeurs et les ingénieurs logiciels travaillant sur des projets WordPress. Elle permet d'effectuer une inspection automatisée et déterministe d'un dépôt WordPress, tel qu'un plugin, un thème, un thème bloc, le noyau WordPress, Gutenberg ou un site complet. L'objectif principal est de collecter des informations essentielles sur l'environnement de développement, notamment les outils utilisés, la configuration des tests, les versions de dépendances et d'autres métadonnées. Le résultat est un rapport JSON structuré qui peut être utilisé pour guider les workflows automatisés, définir des garde-fous (guardrails) ou faciliter l'intégration continue. La compétence est utilisable avec des agents comme Claude Code, Cursor ou Codex, et se base sur une analyse du système de fichiers du dépôt. En résumé, elle offre une base fiable et reproductible pour toute tâche nécessitant une compréhension préalable de la structure et de la configuration d'un projet WordPress.
npx skills add https://github.com/wordpress/agent-skills/tree/main/skills/wp-project-triageUtilisez cette compétence lorsque vous avez besoin d'une inspection déterministe d'un dépôt WordPress (plugin/thème/thème bloc/WP core/Gutenberg/site complet) incluant des indices sur les outils, les tests et les versions, ainsi qu'un rapport JSON structuré pour guider les workflows et les garde-fous.
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".