WP Block Development

94TrustedShips scripts

Custom Gutenberg block creation, metadata management, and server-side render integration.

What it does

Wp Block Development changes your assistant from a general coding helper into a specialized WordPress block architect. It enables the model to interpret existing block structures and perform precise modifications to manifest files, ensuring that your component configurations align with current WordPress registration standards.

This skill is for developers who manage custom Gutenberg blocks, whether static or dynamic. It allows the assistant to handle complex tasks like migrating block versions, managing attribute serialization, and implementing server-side render callbacks without guessing the file architecture of your theme or plugin.

When it earns its place

Reach for it when…

Use this skill when modifying block metadata, configuring script modules, establishing save or render patterns, or managing block deprecation cycles within a WordPress codebase.

Look elsewhere when…

Do not use this skill for general WordPress site maintenance like database optimization, theme CSS styling, or plugin troubleshooting that does not involve custom Gutenberg block logic.

What to say to use it

You never invoke a skill directly — the assistant picks it up when your request matches what it covers. These are the kinds of things that do that.

  • update this block to use apiVersion 3
  • create a new dynamic block structure for my plugin
  • fix the invalid block error in my custom component
  • register these block attributes in my block.json

Install it

Install for all your projects

Copy the skill directory into your personal skills folder. Claude picks it up on its own the next time your request matches what it does — there is nothing to enable.

bash
git clone --depth 1 --branch trunk https://github.com/WordPress/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/wp-block-development ~/.claude/skills/wp-block-development

Install for one project only

Put it in the project's own skills folder instead, so it can be committed and shared with everyone working on that repository.

bash
cp -r /tmp/agent-skills/skills/wp-block-development .claude/skills/wp-block-development

If a skill of the same name exists in both places, the personal one wins.

Installing on Claude.ai or through the API instead? The full guide covers every surface.

Pair it with an MCP server