- Home
- Skills
- Frontend & Web Apps
- wp classic to fse migration
wp classic to fse migration
Migrate classic WordPress themes to FSE with theme.json v3, block patterns, and automated markup validation.
$12
Works with the AI Agents you already use
wp classic to fse migration
Example session with this skill installed
I need to migrate a classic child theme with a custom header.php and several Customizer colors to a block theme. Here is the output from the inventory script.
- Read your context and instructions
- Compiled the wp classic to
- Generated the UI component
The inventory identifies a medium-sized migration. The primary risks are the custom PHP logic in header.php and the reliance on theme_mod colors for the brand identity.
Migration Plan
| Classic Item | Block-theme Equivalent | Risk | Action Owner |
|---|---|---|---|
header.php | parts/header.html + PHP Pattern | Functional | Developer |
footer.php | parts/footer.html | Visual | Developer |
| Customizer Colors | theme.json settings.color.palette | Visual | Developer |
| Sidebar Widgets | parts/sidebar.html (Group/Columns) | Content | User (Rebuild) |
theme.json (v3)
{
"version": 3,
"settings": {
"appearanceTools": true,
"color": {
"palette": [
{
"color": "#1a1a1a",
"name": "Primary Brand",
"slug": "primary"
},
{
"color": "#ffffff",
"name": "Base White",
"slug": "base"
}
],
"defaultPalette": false
},
"typography": {
"defaultFontSizes": false,
"fontSizes": [
{
"size": "1rem",
"slug": "medium"
}
]
}
}
}
parts/header.html
<!-- wp:group {"tagName":"header","layout":{"type":"flex","justifyContent":"space-between"}} -->
<header class="wp-block-group">
<!-- wp:site-logo /-->
<!-- wp:navigation {"layout":{"type":"flex","orientation":"horizontal"}} /-->
</header>
<!-- /wp:group -->
Next steps
- Download brand WOFF2 files and update the
fontFacearray intheme.json. - Move the legacy shortcode logic from
functions.phpinto a companion plugin. - Activate the theme on staging and verify that existing menus map to the Navigation block.
header.html
TSX · React component
Example file from a real run - the skill writes it into your workspace.
Connects securely to your tools. The creator never sees your data.
About this skill
Moving from a classic WordPress theme to Full Site Editing (FSE) often breaks layouts, loses Customizer data, or introduces invalid block markup. This skill provides a structured engineering workflow to migrate PHP templates, widgets, and sidebars into a clean, block-based architecture.
What it does
- Theme inventorying runs a read-only script to map PHP hooks, shortcodes, and Customizer settings to block equivalents.
- Migration planning generates a risk-assessed roadmap flagging content-breaking changes and functionality gaps before writing code.
- Modern theme.json v3 builds a valid configuration with font face declarations, spacing scales, and slug-matched color palettes.
- Template conversion maps
header.php,footer.php, and page templates to HTML parts and PHP patterns for translatable strings. - Automated validation checks block markup for nesting errors, JSON attribute mismatches, and accessibility compliance.
How it works
- Analyze: Provide the theme folder to run the inventory script and identify specific hooks and templates.
- Plan: Review the generated migration table to decide how to handle logic that cannot live in pure HTML templates.
- Execute: Receive the full code for
theme.json, template parts, and patterns while moving shortcodes to a companion plugin. - Verify: Run the block markup checker to ensure zero "unexpected content" errors in the WordPress editor.
Frameworks & tools
Specifically designed for WordPress 6.6+ and theme.json v3. Uses Python scripts for static analysis of theme folders and standard PHP for block patterns.
Why this beats prompting it yourself
Generic prompts often produce invalid block markup that causes "This block contains unexpected or invalid content" errors. This skill follows the strict V3 specification and uses dedicated scripts to catch font-size traps and nesting issues that models usually miss.
Use cases
- Modernizing legacy themes to enable the Site Editor for clients without losing existing CSS tokens.
- Auditing hybrid themes to find missing
templatePartsdeclarations or invalidtheme.jsonstructures. - Converting child themes by properly merging block templates over a parent theme's architecture.
- Self-hosting Google Fonts via the
fontFaceAPI to ensure privacy compliance and performance.
Known limitations
Cannot automatically convert page builder content (Elementor/Divi) or download licensed binary font files. Requires manual verification of WooCommerce overrides and third-party plugin hooks.
Requires WordPress 6.6+ for theme.json v3 features. Does not support automatic conversion of page builder content or binary font downloads. Staging environment required for testing.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 13 days ago
Requires