Verwenden Sie dies beim Entwickeln oder Debuggen von Funktionen der WordPress Interactivity API (data-wp-*-Direktiven, @wordpress/interactivity Store/State/Actions, Block viewScriptModule-Integration, wp_interactivity_*()), einschließlich Performance, Hydration und Direktivenverhalten.
Diese Fähigkeit ist für Entwickler und Debugger gedacht, die mit der WordPress Interactivity API arbeiten, einer nativen JavaScript-Bibliothek zur Erstellung interaktiver, serverseitig gerenderter Blöcke und Anwendungen. Sie deckt alle Kernkonzepte ab, darunter die data-wp-*-Direktiven (z. B. data-wp-bind, data-wp-text, data-wp-on), den @wordpress/interactivity-Store mit seinem reaktiven Zustands- und Aktionssystem, die Block-integration über viewScriptModule sowie die serverseitigen PHP-Funktionen (wp_interactivity_state, wp_interactivity_process_directives). Die Fähigkeit hilft bei der Analyse und Optimierung von Hydration (dem Prozess der Verbindung von serverseitig gerendertem HTML mit clientseitigen Interaktivitätsereignissen), der Behebung von Direktiven-Konflikten oder -Fehlern und der Leistungsoptimierung durch Batch-Updates und verzögerte Initialisierung. Sie ist plattformunabhängig innerhalb des WordPress-Ökosystems und kann über die CLI oder als KI-gestützte Anleitung in Entwicklungsumgebungen wie Cursor, Codex oder Claude Code genutzt werden.
npx skills add https://github.com/wordpress/agent-skills/tree/main/skills/wp-interactivity-apiInstalled? Explore more Produktivität & Zusammenarbeit skills: steipete/gemini, steipete/gh-issues, steipete/skill-creator · View all 6 →
Verwenden Sie dies beim Entwickeln oder Debuggen von Funktionen der WordPress Interactivity API (data-wp--Direktiven, @wordpress/interactivity Store/State/Actions, Block viewScriptModule-Integration, wp_interactivity_()), einschließlich Performance, Hydration und Direktivenverhalten.
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 UIs leveraging the WordPress Design System (WPDS) and its components, tokens, patterns, etc.
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.
Gemini CLI one-shot prompts, summaries, generation, skills, hooks, MCP, or Gemma routing.
Fetch GitHub issues, select candidates, spawn background fix agents, open PRs, and optionally process PR review comments.
Create, edit, audit, tidy, validate, or restructure AgentSkills and SKILL.md files.
Search, install, update, sync, or publish agent skills with the ClawHub CLI and registry.
Delegate coding work to Codex, Claude Code, or OpenCode as background workers; not simple edits or read-only code lookup.
List, configure, authenticate, call, and inspect MCP servers/tools with mcporter over HTTP or stdio.