wordpress-router은(는) 무엇을 하나요?
사용자가 WordPress 코드베이스(플러그인, 테마, 블록 테마, 구텐베르크 블록, WP 핵심 체크아웃)에 대해 질문할 때 저장소를 신속하게 분류하고 올바른 워크플로/스킬(블록, theme.json, REST API, WP-CLI, 성능, 보안, 테스트, 릴리스 패키징)로 라우팅합니다.
사용자가 WordPress 코드베이스(플러그인, 테마, 블록 테마, 구텐베르크 블록, WP 핵심 체크아웃)에 대해 질문할 때 저장소를 신속하게 분류하고 올바른 워크플로/스킬(블록, theme.json, REST API, WP-CLI, 성능, 보안, 테스트, 릴리스 패키징)로 라우팅합니다.
이 스킬은 WordPress 관련 코드베이스를 다룰 때 사용자 질문의 성격을 분석하여 가장 적합한 워크플로 또는 하위 스킬로 라우팅하는 역할을 합니다. 플러그인, 테마, 블록 테마, 구텐베르크 블록, 또는 WordPress 핵심 체크아웃 등 다양한 저장소 유형을 신속하게 분류할 수 있습니다. 주요 라우팅 대상으로는 블록 개발, theme.json 설정, REST API, WP-CLI, 성능 최적화, 보안 점검, 테스트, 그리고 릴리스 패키징 등이 포함됩니다. 이를 통해 개발자는 복잡한 WordPress 생태계 내에서 원하는 작업에 빠르게 접근할 수 있어 생산성을 크게 향상시킬 수 있습니다. 이 스킬은 Claude Code, Cursor, Codex 등 다양한 AI 에이전트 플랫폼에서 활용될 수 있습니다.
npx skills add https://github.com/wordpress/agent-skills/tree/main/skills/wordpress-router사용자가 WordPress 코드베이스(플러그인, 테마, 블록 테마, 구텐베르크 블록, WP 핵심 체크아웃)에 대해 질문할 때 저장소를 신속하게 분류하고 올바른 워크플로/스킬(블록, theme.json, REST API, WP-CLI, 성능, 보안, 테스트, 릴리스 패키징)로 라우팅합니다.
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".