Menu
Discuss a new block's purpose and requirements with the user, then create a GitHub issue with a structured breakdown ready for /wp-acf-blocks:add-block.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Scaffold, revise and manage custom ACF Gutenberg blocks for WordPress with Tailwind CSS. Use when the user wants to create a new block, revise/audit blocks, or set up a WordPress blocks project.
Scaffold one or more ACF Gutenberg blocks from GitHub issues, a markdown brief, or interactive prompts. Generates block.json, fields.json, render.php, and optional view.js.
Deep AI audit of all blocks or specific blocks — runs structural checks first, then uses AI to review content quality, descriptions, grammar, admin render justification, wrapper usage, and empty-state messages.
Fast structural audit of all blocks or specific blocks — checks required files, wrapper attributes, fields.json timestamp, previewImage, viewScript. No AI, runs instantly via script.
Set up a new WordPress theme with the wp-acf-blocks block development workflow
Integrate GROQ LLM streaming into a project. Use when the user wants to add GROQ, set up GROQ streaming, or use a GROQ model in their app.
| name | plan-block |
| description | Discuss a new block's purpose and requirements with the user, then create a GitHub issue with a structured breakdown ready for /wp-acf-blocks:add-block. |
Read @/knowledge/acf-blocks/conventions.md for the breakdown format and namespace detection rules before starting.
Ask: Which GitHub project should this issue go into? Accept a project URL or project name. If the user has used one before this session, suggest it.
gh project list --owner <owner>
Ask: What is this block for? Describe it loosely.
Then ask clarifying questions based on the response. Cover all of these before drafting - but ask conversationally, not as a form:
Stop asking when you have enough to write a complete breakdown. Usually 3-5 exchanges.
Write the breakdown in standard format:
## Block: {slug}
**Slug:** `{slug}`
**Title:** {Title}
**Description:** {One sentence describing what this block does.}
### Fields
- `{field_name}` — {type} — {purpose}
- `{repeater_name}` — repeater
- `{sub_field}` — {type}
### Layout
- {Layout description line by line}
- {Note any JS interactions needed}
Rules:
team-grid, faq-accordion)get_field()(return_format: id)(return_format: array)Show the draft to the user and ask: Does this look right? Any changes?
Iterate until approved.
gh issue create \
--repo <owner>/<repo> \
--title "Block: {Title}" \
--body "{breakdown}" \
--project "{project name or URL}"
Show the created issue URL and number.
Issue #42 created: Block: {Title}
Run this to scaffold:
/wp-acf-blocks:add-block #42