wp-block-development
by WordPressThe wp-block-development skill helps you create, update, and debug WordPress Gutenberg blocks with less guesswork. Use it for block.json metadata, register_block_type(_from_metadata), attributes and serialization, supports, dynamic rendering, deprecations, and build tooling. It is especially useful for Frontend Development tasks that affect editor and frontend parity.
This skill scores 84/100, which means it is a solid listing candidate for Agent Skills Finder. Directory users get a clearly triggerable WordPress block-development workflow with enough operational detail to reduce guesswork versus a generic prompt, though it is somewhat specialized and test-labeled rather than broadly polished.
- Strong triggerability: the frontmatter and "When to use" section clearly target block development tasks like block.json edits, dynamic rendering, deprecations, and build workflows.
- Good operational clarity: the skill provides a concrete procedure, required inputs, and a deterministic block-scanning script, which helps agents start correctly.
- Useful supporting references: ten reference files cover common failure modes such as invalid content, attributes not saving, apiVersion 3 migration, and inner blocks.
- Experimental/test signal is present, so users should expect a practical but not fully mature skill surface.
- No install command is provided in SKILL.md, so adoption may require users to infer setup from the repo structure.
Overview of wp-block-development skill
What wp-block-development does
wp-block-development is a practical skill for building and fixing WordPress Gutenberg blocks, especially when the issue lives in block.json, block registration, saved markup, or build tooling. The wp-block-development skill is best for readers who need to ship a block safely, not just understand the API surface.
Best-fit use cases
Use this wp-block-development guide when you are creating a new block, updating an existing one, diagnosing an invalid block, or moving a block toward dynamic rendering. It is also useful for Frontend Development work that touches viewScript, viewScriptModule, supports, wrapper output, or frontend/editor parity.
What makes it different
This skill is decision-oriented: it helps you choose the right block pattern, spot breaking changes before they land, and avoid common WordPress pitfalls like brittle attribute sources or missing deprecation paths. The main value of the wp-block-development skill is reducing guesswork around registration, serialization, and compatibility.
How to Use wp-block-development skill
Install and scope it correctly
Install the wp-block-development skill with npx skills add WordPress/agent-skills --skill wp-block-development. Then scope the task before prompting: name the repo root, the block namespace, the block path if known, and the WordPress version range. That context matters because wp-block-development behavior changes with apiVersion, modules, and server rendering support.
Start from the right files
Read SKILL.md first, then inspect the most relevant reference files for your task: references/block-json.md, references/attributes-and-serialization.md, references/creating-new-blocks.md, references/dynamic-rendering.md, references/deprecations.md, and references/debugging.md. If you need to find blocks quickly, use scripts/list_blocks.mjs to locate the block.json root instead of guessing.
Give a prompt that can be executed
A strong wp-block-development usage prompt names the goal, the current failure, and the constraints. For example: “Update my-plugin/blocks/cta so the button icon persists after save, keep existing posts valid, and support WordPress 6.9+.” That is better than “fix my block” because it tells the skill whether to change markup, add deprecated, or adjust registration.
Use a workflow that matches the block type
For static blocks, focus on attribute sources, serialized markup, and save(). For dynamic blocks, focus on render.php, render_callback, and wrapper attributes. For container blocks, check InnerBlocks structure before changing template rules. This wp-block-development install pattern works best when you read the block root, then test a small change path before broad refactors.
wp-block-development skill FAQ
Is wp-block-development only for Gutenberg block creation?
No. The wp-block-development skill also fits troubleshooting and maintenance: invalid content, missing editor styles, registration failures, deprecations, and frontend output drift. If your work touches block metadata or serialization, the skill is relevant.
Do I need this skill if I already know WordPress?
If you already know WordPress but want fewer mistakes in block implementation, yes. Ordinary prompts often miss the hidden compatibility work in block development, while wp-block-development pushes you toward the files and decisions that affect saved content and editor behavior.
When should I not use wp-block-development?
Do not use it for general PHP plugin architecture, theme styling, or unrelated JavaScript app work. It is most useful when the problem centers on block registration, block markup, dynamic rendering, or WordPress editor behavior.
Is wp-block-development beginner-friendly?
Yes, if the task is bounded. The skill helps beginners by pointing them to the exact files that matter and by separating static, dynamic, and nested block patterns. It is less helpful if you cannot identify the block root or do not know whether the block saves markup or renders on the server.
How to Improve wp-block-development skill
Provide the block facts up front
The best wp-block-development results come from inputs that include the block name, its folder, whether it is static or dynamic, and the WordPress version you must support. If you can paste the current block.json, the edit/save shape, or the failing markup, the skill can reason about compatibility instead of guessing.
Describe the failure mode, not just the feature
Tell the model what breaks: “attributes reset after update,” “editor shows invalid block,” “frontend CSS missing in iframe,” or “new markup must not break old posts.” Those details determine whether wp-block-development should recommend a migration, a registration fix, a wrapper change, or a build change.
Protect existing content
The most important improvement habit is preserving old posts. If saved HTML changes, ask for a deprecated path and a migration plan. If attributes are coming from brittle selectors, provide the current HTML and expected output so the wp-block-development guide can suggest a safer source.
Iterate with a narrow test loop
After the first answer, test one block, one post, and one WordPress version at a time. If the result is still wrong, feed back the exact console warning, invalid-content message, or rendered HTML diff. That makes the next wp-block-development iteration much more precise and usually avoids unnecessary refactors.