Utilisé lors du développement de blocs WordPress (Gutenberg) : métadonnées block.json, register_block_type(_from_metadata), attributs/sérialisation, supports, rendu dynamique (render.php/render_callback), dépréciations/migrations, viewScript vs viewScriptModule, et workflows de build et test avec @wordpress/scripts/@wordpress/create-block.
Cette compétence est conçue pour les développeurs créant des blocs Gutenberg personnalisés pour WordPress. Elle couvre tous les aspects essentiels du développement de blocs : la définition des métadonnées via `block.json`, l'enregistrement des types de blocs avec `register_block_type()` et `register_block_type_from_metadata()`, la gestion des attributs et de leur sérialisation, ainsi que les options de supports (supports). Elle prend en charge le rendu dynamique côté serveur avec `render.php` ou `render_callback`, et guide dans la mise en place des dépréciations et migrations de versions de blocs. La compétence distingue également `viewScript` et `viewScriptModule` pour l'inclusion de scripts côté client. Enfin, elle intègre les workflows modernes de build (@wordpress/scripts) et de création initiale (@wordpress/create-block) ainsi que les procédures de test. C'est un guide complet pour toute la chaîne de développement de blocs WordPress.
npx skills add https://github.com/wordpress/agent-skills/tree/main/skills/wp-block-developmentInstalled? Explore more Productivité et collaboration skills: steipete/gemini, steipete/gh-issues, steipete/skill-creator · View all 6 →
Utilisé lors du développement de blocs WordPress (Gutenberg) : métadonnées block.json, register_block_type(_from_metadata), attributs/sérialisation, supports, rendu dynamique (render.php/render_callback), dépréciations/migrations, viewScript vs viewScriptModule, et workflows de build et test avec @wordpress/scripts/@wordpress/create-block.
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 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 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.
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.