wp-block-themes_skill
- JavaScript
159
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill automattic/agent-skills --skill wp-block-themes- SKILL.md3.9 KB
Overview
This skill helps developers build, edit, and troubleshoot WordPress block themes focused on theme.json, templates, template parts, patterns, and style variations. It streamlines locating block theme roots, making safe theme.json changes, and resolving Site Editor/preview mismatches. The goal is predictable style hierarchy, correct template wiring, and reliable pattern and variation behavior.
How this skill works
The skill inspects the project to detect block theme roots and key folders, then guides edits to theme.json, templates/, parts/, patterns/, and styles/ with checks for WordPress version compatibility. It provides procedures to create or convert a block theme, confirms expected style inheritance, and includes verification steps to validate Site Editor and frontend behavior. It also lists common failure modes and debugging steps to quickly isolate issues.
When to use it
- Editing theme.json presets, settings, or per-block styles
- Adding or fixing templates (templates/*.html) and template parts (parts/*.html)
- Creating or controlling theme-owned patterns (patterns/) and inserter visibility
- Adding or updating style variations (styles/*.json)
- Troubleshooting styles not applying in Site Editor, post editor, or frontend
Best practices
- Start from a known-good scaffold or export rather than guessing theme layout
- Be explicit about the minimum supported WordPress version for the theme.json schema
- Treat settings (UI controls) separately from styles (visual defaults) when editing theme.json
- Keep template parts directly in parts/ (do not nest) and templates in templates/
- When changing style variations, remember user selections are stored in the database and may not auto-update
Example use cases
- Convert a classic theme to a block theme and set a theme.json base typography and color scale
- Fix a missing template part that breaks the Site Editor by ensuring correct parts/ placement
- Add a theme-owned pattern to patterns/ and control its inserter visibility
- Create a new style variation and verify the Styles UI and frontend render expected defaults
- Debug a case where editor styles differ from frontend by checking theme.json shape, overrides, and active theme
FAQ
User customizations or a child theme can override theme.json defaults; also validate theme.json shape and that you edited the active theme root.
How do I choose the right theme.json schema version?
Base the schema on your minimum supported WordPress core version; different core versions enable different theme.json features and keys.
