À utiliser lors de la construction ou du débogage des fonctionnalités de l'API d'interactivité WordPress (directives data-wp-*, store/state/actions @wordpress/interactivity, intégration du viewScriptModule des blocs, wp_interactivity_*()), y compris les performances, l'hydratation et le comportement des directives.
Cette compétence est conçue pour les développeurs travaillant avec l'API d'interactivité de WordPress, une technologie permettant d'ajouter des comportements dynamiques aux blocs WordPress côté client via des directives HTML personnalisées (data-wp-*) et un store JavaScript partagé. Elle facilite la construction et le débogage de fonctionnalités interactives comme la gestion d'état, les actions utilisateur, l'intégration de viewScriptModule dans les blocs, et les fonctions PHP associées (wp_interactivity_*()). La compétence couvre également des aspects critiques tels que les performances, l'hydratation du DOM, et le comportement précis des directives. Elle s'applique à tout projet WordPress utilisant le package @wordpress/interactivity, que ce soit dans le contexte de l'éditeur de blocs (Gutenberg) ou du rendu frontal, et est compatible avec les outils de développement standard (comme les navigateurs et les environnements Node.js pour la compilation du JavaScript). En fournissant une documentation localisée et des explications détaillées, elle aide les développeurs à adopter rapidement cette API moderne sans avoir à consulter constamment la documentation officielle en anglais, améliorant ainsi leur productivité et la qualité de leurs implémentations interactives.
npx skills add https://github.com/wordpress/agent-skills/tree/main/skills/wp-interactivity-apiInstalled? Explore more Productivité et collaboration skills: steipete/gemini, steipete/gh-issues, steipete/skill-creator · View all 6 →
À utiliser lors de la construction ou du débogage des fonctionnalités de l'API d'interactivité WordPress (directives data-wp-, store/state/actions @wordpress/interactivity, intégration du viewScriptModule des blocs, wp_interactivity_()), y compris les performances, l'hydratation et le comportement des directives.
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.