web-clone

Clone websites by URL into a client-ready codebase with Playwright MCP.

1|Updated Mar 17, 2025
One-click install
npx skills add https://github.com/ozby/node-pubsub --skill web-clone-ozby
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: web-clone
Source: https://github.com/ozby/node-pubsub/tree/main/.codex/skills/web-clone
Command: npx skills add https://github.com/ozby/node-pubsub --skill web-clone-ozby

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cloning a live website into a working, client-ready codebase that faithfully replicates visual design and core interactions is time-consuming and error-prone. This skill automates the process, enabling rapid prototyping and offline development with verifiable fidelity.

Core Features & Use Cases

  • URL-driven live cloning powered by Playwright MCP for live page extraction.
  • LLM-driven code generation with iterative verification using a visual verdict tool.
  • Single-page clone scope suitable for quick prototypes, UI verification, and reference replicas.

Quick Start

Provide a live URL and run the automated clone workflow to generate a working, locally served replica.

Frequently Asked Questions about web-clone

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

FAQPage Schema
How do I clone a live website into a working codebase from a URL?

Cloning a live website from a URL is done using Playwright for browser automation to extract page structure, generating a reusable frontend scaffold with layout shells, components, and basic interactions.

What is single-page website cloning used for in frontend development?

Single-page website cloning is used for rapid prototyping, UI verification, and offline development when the original backend is unavailable, yielding a client-ready codebase that mirrors the target's visual design.

Do I need Playwright MCP to automate website cloning?

Yes, Playwright MCP is required to provide the live page extraction and browser automation needed to drive the URL-driven cloning workflow and generate the working replica.

How does visual verification work when replicating a website's UI?

Visual verification during website replication works by using a visual verdict tool to iteratively check LLM-generated code against the target, ensuring the output codebase faithfully mirrors the original visual design.

What are the limitations of using automated cloning for single-page prototypes?

The main limitation of automated single-page cloning is its scope: it focuses on visual fidelity and basic interactions rather than backend logic, making it best suited for quick prototypes and offline reference.