Classic-to-Block Theme Migrator

Classic-to-Block Theme Migrator runs in two modes. In ASSESS mode, it reads your classic theme file by file, classifies every template as auto-convertible, manual, or business-logic-that-belongs-in-a-plugin, scores each file by impact and effort, and returns a four-phase reversible migration plan with per-file risk ratings. In MIGRATE mode it produces the actual converted files: a valid theme.json with all design tokens mapped from your CSS variables and Customizer settings, converted template parts, Query Loop replacements for every classic loop, pattern files with correct Block Pattern headers, and a companion plugin scaffold that pulls CPTs, taxonomies, shortcodes, and REST endpoints cleanly out of the theme.

A typical input is a pasted or described classic theme directory — style.css, header.php, footer.php, functions.php, single.php, archive.php, and any page-specific templates — plus notes on whether CPTs, ACF field groups, or custom REST routes are present. The skill calibrates to whatever WordPress version is in use, flags any page-builder templates as out-of-scope manual work, and keeps the classic theme as a tagged git fallback throughout. No specific niche is assumed; the buyer supplies the actual theme and its business context.

A MIGRATE response for a theme with a registered CPT and custom loop would include, among other files: a complete theme.json (version 3 schema, WP 6.4+) with every palette color and font size as a named slug; parts/header.html showing the exact header.php-to-block-markup transformation; templates/archive.html with a Query Loop block and all child blocks (post-featured-image, post-title, post-excerpt, post-date, pagination) in place of The Loop; and a {theme-slug}-functionality plugin scaffold registering the CPT and its REST endpoint, with an explanation of what was extracted and why.