From zenbu-powers
Use when developing WordPress block themes: theme.json (global settings/styles), templates and template parts, patterns, style variations, and Site Editor troubleshooting (style hierarchy, overrides, caching).
npx claudepluginhub zenbuapps/zenbu-powers --plugin zenbu-powersThis skill uses the workspace's default tool permissions.
**Compatibility**: Targets WordPress 6.9+ (PHP 7.2.24+). Filesystem-based agent with bash + node. Some workflows require WP-CLI.
Develops and debugs WordPress block themes: edits theme.json settings/styles, manages templates/parts/patterns/style variations, troubleshoots Site Editor (hierarchy, overrides, caching).
Guides WordPress theme development workflow: setup, template hierarchy, custom post types, block editor support, responsive design, and WP 7.0 features like Pattern Editing, Navigation Overlays, and admin refresh.
Generates WordPress Full Site Editing block themes: theme.json configs, block templates, template parts, patterns, functions.php, and styles.
Share bugs, ideas, or general feedback.
Compatibility: Targets WordPress 6.9+ (PHP 7.2.24+). Filesystem-based agent with bash + node. Some workflows require WP-CLI.
Use this skill for block theme work such as:
theme.json (presets, settings, styles, per-block styles)templates/*.html) and template parts (parts/*.html)patterns/*.php) and controlling what appears in the inserterstyles/*.json)node skills/wp-project-triage/scripts/detect_wp_project.mjsnode skills/wp-block-themes/scripts/detect_block_themes.mjsIf multiple themes exist, pick one and scope all changes to that theme root.
If you are creating a new block theme from scratch (or converting a classic theme):
theme.json schema versions differ.Read:
references/creating-new-block-theme.mdAfter creating the theme root, re-run detect_block_themes and continue below.
theme.json presenttemplates/ and/or parts/ presentRead:
references/debugging.md (style hierarchy + fastest checks)theme.json changes safelyDecide whether you are changing:
Read:
references/theme-json.mdtemplates/ and are HTML.parts/ and must not be nested in subdirectories.Read:
references/templates-and-parts.mdPrefer filesystem patterns under patterns/ when you want theme-owned patterns.
Read:
references/patterns.mdStyle variations are JSON files under styles/. Note: once a user picks a style variation, that selection is stored in the DB, so changing the file may not “update what the user sees” automatically.
Read:
references/style-variations.mdStart with:
references/debugging.mdCommon issues:
theme.json shape/typos prevent applicationIf upstream behavior is unclear, consult canonical docs:
theme.json, templates, patterns, and style variations.