wpds은(는) 무엇을 하나요?
WordPress 디자인 시스템(WPDS) 및 그 구성 요소, 토큰, 패턴 등을 활용한 UI 구축 시 사용됩니다.
WordPress 디자인 시스템(WPDS) 및 그 구성 요소, 토큰, 패턴 등을 활용한 UI 구축 시 사용됩니다.
이 스킬은 WordPress 디자인 시스템(WPDS)을 기반으로 UI를 구축할 때 활용됩니다. WPDS는 일관된 디자인 언어를 제공하여 개발자가 테마, 플러그인, 또는 WordPress 관리 화면에서 통일된 사용자 경험을 구현할 수 있도록 돕습니다. 이 스킬은 WPDS의 컴포넌트, 디자인 토큰, 패턴 등을 참조하고 적용하는 데 중점을 두며, Claude Code, Cursor, Codex 등 다양한 AI 에이전트 플랫폼에서 사용될 수 있습니다. 개발자는 이 스킬을 통해 디자인 시스템의 지침을 코드 생성에 직접 반영함으로써, 디자인 일관성을 유지하고 개발 시간을 단축할 수 있습니다. SKILL.md 문서에는 WPDS의 주요 개념과 사용법이 상세히 설명되어 있어, AI 에이전트가 컨텍스트에 맞는 UI 컴포넌트와 스타일을 제안하거나 생성하는 데 도움을 줍니다.
npx skills add https://github.com/wordpress/agent-skills/tree/main/skills/wpdsWordPress 디자인 시스템(WPDS) 및 그 구성 요소, 토큰, 패턴 등을 활용한 UI 구축 시 사용됩니다.
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 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".