wp-block-development — Claude Code skill: Gutenberg blocks

What wp-block-development does

WP Block Development takes an agent through Gutenberg work: block.json metadata, registration via register_block_type with metadata, attributes and serialization, supports, dynamic rendering with render.php or render_callback, and the difference between viewScript and viewScriptModule. It starts with two scripts — list_blocks.mjs finds every block in the repo, detect_wp_project.mjs works out where you are.

Then come the steps: scaffold with @wordpress/create-block, move the block to apiVersion 3, pick a static or dynamic model, edit the metadata, register the block in PHP. Reference files in references/ back each step: attributes and serialization, wrapper props and supports, inner blocks, deprecations, tooling, debugging.

Build workflows follow whatever the repo already runs, usually @wordpress/scripts and wp-env. The agent needs bash and node, and some workflows want WP-CLI too. It targets WordPress 7.0+ with PHP 7.4.0+, and apiVersion 3 matters because the WordPress 7.0 post editor runs inside an iframe, where styles left out of the metadata never apply. On a full site, name the plugin or theme holding the block up front, or the edits land in the wrong block.json.