wp-edit-themelisted

# WP Edit Theme Theme-level writes — the highest-risk surface in WordPress (bad PHP in functions.php = White Screen of Death; bad JSON in theme.json = Site Editor white-page in editor). This skill enforces child-theme-first, pre-write validation, snapshot-before-switch, and atomic session grouping so the user can revert any combination. ## Iron Rule <EXTREMELY-IMPORTANT> 1. NEVER edit a parent theme's files directly when the user owns the site — scaffold a child theme first via `rolepod_wp_child_theme_create`, then edit IN the child. Parent edits get overwritten on theme update; child edits survive. 2. NEVER call `wp_cli_run ["theme", "activate", ...]` directly — use `rolepod_wp_theme_switch_safe` which snapshots the current theme + auto-rolls-back if the new theme breaks the frontend. 3. ALWAYS rely on the file_write pre-write validators (PHP `php -l` server-side, JSON.parse client-side) — they cannot be bypassed. If validation throws, the payload IS broken; do not retry with the same content. </EXTREMELY-IMPORTANT> ## When to use - "Edit functions.php" / "add a callback to the theme" - "Change theme.json palette / typography / spacing" - "Edit global styles" / "Site Editor preferences" - "Make a child theme of Twenty Twenty-Five" - "Switch theme from X to Y" - "Override a template" (single.php / archive.php / footer.html) Skip when: - Page-builder widget tree (Elementor / Divi / Oxygen / Bricks) → `wp-edit-design`. - New theme from scratch (skeleton bootstrap) → `wp-s