liberate-it

Converts a public website URL into a WordPress block theme with captured layout, tokens and local assets.

7|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/fellyph/wp-clone-to-block-theme --skill liberate-it
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: liberate-it
Source: https://github.com/fellyph/wp-clone-to-block-theme/tree/main
Command: npx skills add https://github.com/fellyph/wp-clone-to-block-theme --skill liberate-it

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires node, git, curl, bash, python3, studio, chrome-devtools MCP, php, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Converting a live website into a WordPress block theme is slow, guessy, and error-prone because layout, real content, and visual style must be re-created manually.

Core Features & Use Cases

  • Pixel-close block-theme cloning: Captures a public URL, extracts design tokens and real section content, and generates runnable WP block theme patterns.
  • Local assets + offline-safe output: Downloads images/posters locally and rewrites patterns to use theme asset paths instead of expiring CDN URLs.
  • Design-brief + spec-driven generation: Writes a frozen design contract (design.md), creates per-section spec files from computed styles, then generates one pattern per section and validates artifacts.
  • Local WordPress Studio preview with visual QA: Deploys to a persistent Studio site and screenshots desktop/mobile for iterative visual comparison.

Quick Start

Run /liberate-it https://example.com/ and let it generate the cloned block theme under ./clones/<slug>/.

Frequently Asked Questions about liberate-it

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert a public website URL into a WordPress block theme?

To convert a public website URL into a WordPress block theme, capture the live layout, design tokens, and real content, then generate per-section block patterns with local assets. This process creates a runnable theme by rewriting CDN URLs to theme asset paths for offline-safe output.

What is the best way to clone a marketing or portfolio site into a WP block theme?

The best way to clone a marketing or portfolio site into a WP block theme is by capturing computed styles and real section content to create a frozen design contract. This generates per-section spec files and block patterns, deploying to a local WordPress Studio preview for visual QA.

Does website cloning into block themes require chrome-devtools MCP?

Yes, website cloning into block themes requires chrome-devtools MCP for accurate live layout capture. It also relies on deterministic JS extract scripts, WordPress Studio CLI for deployment, and strict artifact validation to prevent missing assets or template drift during the generation process.

How do I handle missing semantic sections when cloning a builder-driven web page?

When cloning a builder-driven web page with missing semantic sections, a fallback clustering strategy is applied to group elements into coherent sections. This ensures the automated generation of per-section block patterns and design specs remains accurate despite the lack of explicit semantic HTML.

What are the limitations of automated WordPress block theme generation from a live URL?

Limitations of automated WordPress block theme generation include potential template drift and missing assets if strict spec validation is bypassed. It also requires a specific local environment including node, git, php, python3, and curl to execute the deterministic capture and Studio CLI deployment scripts.

Why do my cloned WordPress block patterns reference expired CDN URLs instead of local assets?

Cloned WordPress block patterns reference expired CDN URLs when local asset downloading and path rewriting fail. To fix this, deterministic JS validation scripts must download images and posters locally, ensuring patterns use theme asset paths instead of expiring external CDN URLs.