用于开发 WordPress（Gutenberg）区块：block.json 元数据、register_block_type(_from_metadata)、属性/序列化、支持功能、动态渲染（render.php/render_callback）、弃用/迁移、viewScript 与 viewScriptModule，以及 @wordpress/scripts/@wordpress/create-block 构建和测试工作流。
此技能旨在指导开发者高效构建 WordPress Gutenberg 区块。它覆盖了从区块元数据定义（block.json）、注册方法（register_block_type 及 register_block_type_from_metadata）到属性声明、序列化逻辑、支持（supports）配置的完整流程。对于动态渲染场景，技能详解了 render.php 和 render_callback 的用法，并强调了弃用与迁移（deprecations/migrations）的最佳实践。此外，它清晰区分了 viewScript 与 viewScriptModule 的使用场景，并整合了 @wordpress/scripts 和 @wordpress/create-block 的构建与测试工作流，确保与 WordPress 官方工具链的无缝集成。该技能适用于所有主流 AI 代理（如 Claude Code、Cursor 等），帮助开发者快速生成符合 WordPress 编码标准的区块代码。
npx skills add https://github.com/wordpress/agent-skills/tree/main/skills/wp-block-developmentInstalled? Explore more 生产力与协作 skills: steipete/gemini, steipete/gh-issues, steipete/skill-creator · View all 6 →
用于开发 WordPress（Gutenberg）区块时使用：block.json 元数据、register_block_type(_from_metadata)、属性/序列化、supports、动态渲染（render.php/render_callback）、弃用/迁移、viewScript 与 viewScriptModule，以及 @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.