Utilisez cette compétence lorsque l'utilisateur pose des questions sur des codebases WordPress (plugins, thèmes, thèmes blocks, blocs Gutenberg, extractions WP core) et que vous devez rapidement classer le dépôt et router vers le bon workflow/compétence (blocs, theme.json, API REST, WP-CLI, performance, sécurité, tests, packaging de release).
Cette compétence, `wordpress/wordpress-router`, agit comme un aiguilleur intelligent pour les projets WordPress. Lorsqu'un développeur ou un agent AI interagit avec un dépôt WordPress (plugin, thème, thème block, bloc Gutenberg, ou même une extraction du noyau WordPress), cette compétence analyse rapidement le codebase pour identifier le type de projet et la question posée. En fonction de cette classification, elle redirige ensuite vers le workflow ou la compétence spécialisée la plus appropriée, comme la création de blocs, la gestion du fichier `theme.json`, l'utilisation de l'API REST, WP-CLI, l'optimisation des performances, la sécurité, les tests, ou le packaging de release. Cela permet de gagner du temps en évitant de devoir analyser manuellement chaque dépôt et en garantissant que les bonnes pratiques et outils WordPress spécifiques au contexte sont appliqués. Sa principale utilité est d'automatiser le routage dans les environnements de développement assistés par IA (comme Claude Code, Cursor, etc.) pour les projets WordPress complexes.
npx skills add https://github.com/wordpress/agent-skills/tree/main/skills/wordpress-routerÀ utiliser lorsque l'utilisateur pose des questions sur des codebases WordPress (plugins, thèmes, thèmes blocks, blocs Gutenberg, extractions WP core) et que vous devez rapidement classer le dépôt et router vers le bon workflow/compétence (blocs, theme.json, API REST, WP-CLI, performance, sécurité, tests, packaging de release).
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 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 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".