워드프레스/블록 테마
워드프레스 블록 테마 개발 시 사용: theme.json (전역 설정 및 스타일), 템플릿 및 템플릿 파트, 패턴, 스타일 변형, 사이트 편집기 문제 해결 (스타일 계층, 재정의, 캐싱).
워드프레스 블록 테마 개발 시 사용: theme.json (전역 설정/스타일), 템플릿 및 템플릿 파트, 패턴, 스타일 변형, 사이트 편집기 문제 해결 (스타일 계층, 재정의, 캐싱).
이 스킬은 워드프레스 블록 테마 개발을 위한 포괄적인 도움말을 제공합니다. `theme.json` 파일을 통한 전역 설정 및 스타일 관리, 템플릿과 템플릿 파트 생성, 패턴 활용, 스타일 변형 등 블록 테마의 핵심 요소를 지원합니다. 또한 사이트 편집기에서 발생하는 스타일 계층 충돌, 재정의 문제, 캐싱 관련 이슈를 해결하는 데 유용합니다. 이 스킬은 개발자와 AI 에이전트가 워드프레스 블록 테마를 효율적으로 구축하고 문제를 진단할 수 있도록 설계되었습니다.
npx skills add https://github.com/wordpress/agent-skills/tree/main/skills/wp-block-themes워드프레스 블록 테마 개발 시 사용: theme.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 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".