Codex WordPress Theme Development Review
Purpose
Use this skill when Codex needs to review WordPress theme code, especially theme.json, template structure, Full Site Editing patterns, and classic-to-block migration concerns.
Focus Areas
- Theme type detection: block, classic, hybrid, or child theme
theme.json structure and versioning- Template hierarchy and required files
- Template parts, block markup, and pattern registration
- Global styles, spacing systems, and style variations
- Migration or compatibility issues between classic and block approaches
Workflow
- Detect the theme type and review context first.
- Validate
theme.json, required files, and template structure.
- Check template parts, patterns, style variations, and global style choices.
- Use shared reference docs for deeper checks only where needed.
- Report findings with severity, file references, and theme-specific remediation guidance.
Reference Files
Load only the references you need from:
../../claude-skills/wp-theme-development/references/theme-json-guide.md../../claude-skills/wp-theme-development/references/template-patterns.md../../claude-skills/wp-theme-development/references/fse-guide.md../../claude-skills/wp-theme-development/references/classic-to-block-guide.md
Output
- Group findings by severity
- Include file references across PHP, HTML, and JSON files
- Explain whether the issue affects block themes, classic themes, or both
- Suggest fixes that match current WordPress theme conventions
1---2name: wp-theme-development3description: WordPress theme review for Codex. Use when reviewing block themes, classic themes, or hybrid themes for theme.json structure, templates, template parts, style variations, global styles, and FSE patterns.4---56# Codex WordPress Theme Development Review78## Purpose910Use this skill when Codex needs to review WordPress theme code, especially `theme.json`, template structure, Full Site Editing patterns, and classic-to-block migration concerns.1112## Focus Areas1314- Theme type detection: block, classic, hybrid, or child theme15- `theme.json` structure and versioning16- Template hierarchy and required files17- Template parts, block markup, and pattern registration18- Global styles, spacing systems, and style variations19- Migration or compatibility issues between classic and block approaches2021## Workflow22231. Detect the theme type and review context first.242. Validate `theme.json`, required files, and template structure.253. Check template parts, patterns, style variations, and global style choices.264. Use shared reference docs for deeper checks only where needed.275. Report findings with severity, file references, and theme-specific remediation guidance.2829## Reference Files3031Load only the references you need from:3233- `../../claude-skills/wp-theme-development/references/theme-json-guide.md`34- `../../claude-skills/wp-theme-development/references/template-patterns.md`35- `../../claude-skills/wp-theme-development/references/fse-guide.md`36- `../../claude-skills/wp-theme-development/references/classic-to-block-guide.md`3738## Output3940- Group findings by severity41- Include file references across PHP, HTML, and JSON files42- Explain whether the issue affects block themes, classic themes, or both43- Suggest fixes that match current WordPress theme conventions44
jorgerosal