Community생산성 & 협업github.com

wordpress/wp-interactivity-api

WordPress Interactivity API 기능(data-wp-* 지시문, @wordpress/interactivity 스토어/상태/액션, 블록 viewScriptModule 통합, wp_interactivity_*() 함수) 구축 또는 디버깅 시 사용합니다. 성능, 하이드레이션, 지시문 동작을 포함합니다.

wp-interactivity-api란 무엇인가요?

이 스킬은 WordPress Interactivity API를 사용하여 대화형 블록을 구축하거나 디버깅할 때 필요한 모든 것을 제공합니다. 개발자는 `data-wp-*` 지시문을 사용하여 프론트엔드 동작을 선언적으로 정의하고, `@wordpress/interactivity` 패키지를 통해 스토어, 상태, 액션을 관리할 수 있습니다. 또한, 블록의 `viewScriptModule`을 통합하여 클라이언트 측 JavaScript를 효율적으로 로드하고, `wp_interactivity_*()` PHP 함수를 사용하여 서버 측에서 초기 상태를 설정할 수 있습니다. 이 스킬은 성능 최적화, 하이드레이션 문제 해결, 지시문 동작 분석에 유용하며, WordPress 6.5+ 환경에서 현대적인 대화형 블록 개발을 지원합니다.

지원 대상~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/wordpress/agent-skills/tree/main/skills/wp-interactivity-api

Installed? Explore more 생산성 & 협업 skills: steipete/gemini, steipete/gh-issues, steipete/skill-creator · View all 6 →

즐겨 사용하는 AI에게 물어보기

이 에이전트 스킬이 미리 로드된 새 채팅을 엽니다.

문서

wp-interactivity-api은(는) 무엇을 하나요?

WordPress Interactivity API 기능(data-wp-* 지시문, @wordpress/interactivity 스토어/상태/액션, 블록 viewScriptModule 통합, wp_interactivity_*())을 구축하거나 디버깅할 때 사용합니다. 성능, 하이드레이션, 지시문 동작을 포함합니다.

주요 기능

  • data-wp- 지시문*: 프론트엔드에서 선언적으로 상호작용을 정의합니다.
  • @wordpress/interactivity 패키지: 스토어, 상태, 액션을 관리합니다.
  • viewScriptModule 통합: 블록에 클라이언트 측 JavaScript를 추가합니다.
  • wp_interactivity_*() PHP 함수: 서버 측에서 초기 상태를 설정합니다.

사용 예시

// @wordpress/interactivity 스토어 예시
const { store } = window.wp.interactivity;

store('my-block', {
  state: {
    count: 0,
  },
  actions: {
    increment() {
      this.state.count++;
    },
  },
});
<!-- data-wp-* 지시문 예시 -->
<div data-wp-interactive="my-block">
  <span data-wp-text="state.count">0</span>
  <button data-wp-on--click="actions.increment">증가</button>
</div>
// PHP에서 초기 상태 설정
$context = array('count' => 5);
wp_interactivity_state('my-block', $context);

참고 자료

Individual skills in this repo

This repo contains 13 individual skills — each has its own dedicated page.

wordpress/blueprint

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.

wordpress/wordpress-router

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).

wordpress/wp-abilities-api

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.

wordpress/wp-block-development

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.

wordpress/wp-block-themes

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).

wordpress/wpds

Use when building UIs leveraging the WordPress Design System (WPDS) and its components, tokens, patterns, etc.

wordpress/wp-performance

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.

wordpress/wp-phpstan

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.

wordpress/wp-playground

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).

wordpress/wp-plugin-development

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.

wordpress/wp-project-triage

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.

wordpress/wp-rest-api

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.

wordpress/wp-wpcli-and-ops

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.

관련 스킬