agentsclimarketplace

Plan block

Skill phucbm/skills/skills/wordpress/wp-acf-blocks/skills/plan-block

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.From its SKILL.md

Install
npx -y skills add phucbm/skills --skill plan-block

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

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 2 stars2 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.

SKILL.md

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

Read @/knowledge/acf-blocks/conventions.md for the breakdown format and namespace detection rules before starting.

Step 1 — Get GitHub project

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>

Step 2 — Understand the block

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:

  • What content does it display? (text, images, video, links?)
  • Any repeating items? (cards, slides, rows, accordion items?)
  • Layout: single column, grid, split, tabs, accordion, slider?
  • Does anything expand, animate, or change on user interaction?
  • Is there a heading above the main content?
  • Any CTAs or links?
  • Mobile layout different from desktop?

Stop asking when you have enough to write a complete breakdown. Usually 3-5 exchanges.

Step 3 — Draft breakdown

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:

  • Slug: kebab-case, descriptive, concise (e.g. team-grid, faq-accordion)
  • Fields: only what render.php will actually read via get_field()
  • Image fields: always note (return_format: id)
  • Link fields: always note (return_format: array)
  • Layout: enough detail for Claude to generate structural HTML - columns, order, loops, interactions

Show the draft to the user and ask: Does this look right? Any changes?

Iterate until approved.

Step 4 — Create GitHub issue

gh issue create \
  --repo <owner>/<repo> \
  --title "Block: {Title}" \
  --body "{breakdown}" \
  --project "{project name or URL}"

Show the created issue URL and number.

Step 5 — Handoff

Issue #42 created: Block: {Title}

Run this to scaffold:
/wp-acf-blocks:add-block #42

What ships with it

Read from the repository

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

Keep looking

Skills are one crate of 326,851. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.