This skill validates WordPress FSE (Full Site Editing) theme structure including templates hierarchy, page associations, theme.json configuration, block styles, featured images usage, file permissions, and UpdraftPlus backup configuration. Use when auditing a WordPress site, after creating/modifying templates, before production deployment, or when troubleshooting backup issues.
Validates WordPress FSE theme structure including templates, theme.json, block styles, file permissions, and UpdraftPlus backup configuration. Use before production deployment or after template modifications to catch structural issues and backup misconfigurations.
/plugin marketplace add theflysurfer/claude-skills-marketplace/plugin install theflysurfer-claude-skills-marketplace@theflysurfer/claude-skills-marketplaceThis skill inherits all available tools. When active, it can use any tool Claude has access to.
README.mdassets/validation-report-template.mdreferences/fse-best-practices.mdreferences/wordpress-template-hierarchy.mdscripts/check_block_styles.shscripts/check_theme_json.pyscripts/check_updraftplus.shscripts/validate_templates.shComprehensive validation tool for WordPress Full Site Editing (FSE) themes.
Use this skill to validate WordPress site structure in these scenarios:
Template Hierarchy
Theme Configuration
Block Styles
Content Structure
File Permissions (Docker/VPS context)
UpdraftPlus Backup Configuration
Run the template validator script:
bash scripts/validate_templates.sh <theme-path>
This checks:
See references/wordpress-template-hierarchy.md for complete hierarchy documentation.
Validate the theme configuration:
python scripts/check_theme_json.py <path/to/theme.json>
Validates:
Check functions.php for registered block styles:
bash scripts/check_block_styles.sh <theme-path>
Detects:
For WordPress installations, verify page associations:
# Check pages without featured images
wp post list --post_type=page --format=json --allow-root | jq '.[] | select(.featured_image == null)'
# Check template assignments
wp db query "SELECT p.ID, p.post_title, pm.meta_value as template FROM wp_posts p LEFT JOIN wp_postmeta pm ON p.ID = pm.post_id AND pm.meta_key = '_wp_page_template' WHERE p.post_type = 'page' AND p.post_status = 'publish';" --allow-root
For Docker/VPS deployments:
# Check theme files ownership
docker exec <container> ls -la /var/www/html/wp-content/themes/<theme-name>/
# Fix permissions if needed
docker exec <container> chown -R www-data:www-data /var/www/html/wp-content/themes/<theme-name>/
docker exec <container> find /var/www/html/wp-content/themes/<theme-name>/ -type f -exec chmod 644 {} \;
docker exec <container> find /var/www/html/wp-content/themes/<theme-name>/ -type d -exec chmod 755 {} \;
Validate backup plugin configuration:
bash scripts/check_updraftplus.sh <container-name>
Checks:
Common Issues Fixed:
Use the report template to document findings:
cp assets/validation-report-template.md validation-report-$(date +%Y%m%d).md
# Edit with validation results
Refer to references/fse-best-practices.md for complete guidelines. Key checks include:
Templates
front-page.html or page-{slug}.html (not generic page.html)index.html (fallback)Theme.json
Block Styles
register_block_style()Content
File Organization
assets/css/assets/js/templates/parts/Fix: Create minimal fallback template:
<!-- wp:template-part {"slug":"header"} /-->
<!-- wp:group {"tagName":"main"} -->
<main class="wp-block-group">
<!-- wp:post-content /-->
</main>
<!-- /wp:group -->
<!-- wp:template-part {"slug":"footer"} /-->
Fix: Validate JSON syntax with jsonlint or use WordPress schema validator.
Fix:
# Set featured image for page
wp post meta update <page-id> _thumbnail_id <image-id> --allow-root
Fix:
docker exec <container> chown -R www-data:www-data /var/www/html/wp-content/uploads/
docker exec <container> chmod -R 755 /var/www/html/wp-content/uploads/
After validation, the skill generates a markdown report (validation-report-YYYYMMDD.md) containing:
See assets/validation-report-template.md for the report format.
references/wordpress-template-hierarchy.md - Complete WordPress template hierarchyreferences/fse-best-practices.md - FSE development best practicesscripts/validate_templates.sh - Template structure validatorscripts/check_theme_json.py - Theme.json validatorscripts/check_block_styles.sh - Block styles analyzerThis skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.