Se utiliza cuando el usuario pregunta sobre bases de código de WordPress (plugins, temas, temas de bloques, bloques de Gutenberg, checkouts de WP core) y es necesario clasificar rápidamente el repositorio y enrutar al flujo de trabajo/habilidad correcto (bloques, theme.json, API REST, WP-CLI, rendimiento, seguridad, pruebas, empaquetado de versiones).
El router de WordPress es una habilidad diseñada para clasificar y enrutar automáticamente consultas relacionadas con repositorios de WordPress. Identifica el tipo de proyecto (plugins, temas, bloques Gutenberg, checkouts de WP core) y redirige la solicitud al flujo de trabajo o habilidad especializada correspondiente, como desarrollo de bloques, configuración de theme.json, integración con la API REST, comandos WP-CLI, optimización de rendimiento, análisis de seguridad, ejecución de pruebas o empaquetado de versiones. Es útil para desarrolladores que trabajan con ecosistemas WordPress y necesitan respuestas contextualmente relevantes sin tener que navegar manualmente por múltiples herramientas. Funciona como un enrutador inteligente, ahorrando tiempo y reduciendo errores al asignar tareas a los recursos adecuados.
npx skills add https://github.com/wordpress/agent-skills/tree/main/skills/wordpress-routerSe utiliza cuando el usuario pregunta sobre bases de código de WordPress (plugins, temas, temas de bloques, bloques de Gutenberg, checkouts de WP core) y es necesario clasificar rápidamente el repositorio y enrutar al flujo de trabajo/habilidad correcto (bloques, theme.json, API REST, WP-CLI, rendimiento, seguridad, pruebas, empaquetado de versiones).
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".