Init

Claude Plugin - Scaffold, audit and manage custom ACF Gutenberg blocks for WordPress with Tailwind CSS integration.

Install

npx -y skills add phucbm/wp-blocks-dev --skill init

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Initialize a new WordPress theme with the wp-blocks-dev block development workflow

SKILL.md

2.4 KB, 601 tokens by cl100k_base, as published. Nobody here has run it

Read [@/knowledge/acf-blocks/conventions.md](/knowledge/acf-blocks/conventions.md), [@/knowledge/tailwind/build-pipeline.md](/knowledge/tailwind/build-pipeline.md), and [@/knowledge/typescript/tsup-setup.md](/knowledge/typescript/tsup-setup.md), then:

1. Collect project info

Ask for all answers before proceeding:

Project name — human-readable, e.g. My Client Site
Theme slug — kebab-case, e.g. my-client-site
Author — developer or agency name

2. Confirm optional features

Default yes for all:

Tailwind v4 — CSS build pipeline with per-developer CSS support
TypeScript + tsup — JS bundler for entry files and block scripts
Per-developer CSS — multi-dev Tailwind setup

3. Check for existing files

If a file already exists, ask whether to overwrite or skip. Never silently overwrite.

4. Scaffold the theme

Create under themes/{slug}/:

themes/{slug}/
├── style.css           Theme header (Name, Author, Text Domain, Version)
├── index.php           <?php // Silence is golden.
├── functions.php       require register-blocks + enqueue-assets, PX_PROJECT_NAME constant
├── blocks.json         []
├── QUICKSTART.md
├── blocks/
├── inc/
│   ├── register-blocks.php
│   └── enqueue-assets.php
├── helpers/
└── assets/
    ├── js/
    └── css/

QUICKSTART.md content:

# Quick Start
- `/wp-blocks-dev:create-block <name>` — scaffold a new block
- `/wp-blocks-dev:audit-blocks` — audit all blocks against conventions

5. If Tailwind selected

Follow knowledge/tailwind/build-pipeline.md. Copy the template:

mkdir -p themes/{slug}/scripts themes/{slug}/assets/css
cp $(claude plugin path wp-blocks-dev)/templates/tailwind.js themes/{slug}/scripts/tailwind.js

Remind user to copy tailwind-theme-loader.php into mu-plugins/.

6. If TypeScript selected

Follow knowledge/typescript/tsup-setup.md. Create tsup.config.ts, tsconfig.json, and assets/js/index.entry.ts.

7. Confirm completion

Print a summary of what was created and what was skipped. Next steps:

Activate the theme in WordPress
Run pnpm install && pnpm build if Tailwind or TS was selected
Use /wp-blocks-dev:create-block to add the first block

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.