clone-website

To clone a live website, provide one or more target URLs as arguments to trigger extraction. The skill reverse-engineers the site into isolated worktrees, extracting CSS, assets, and content to recreate or port the site reliably.

Yes, this skill supports multi-site cloning by dispatching parallel builders per site while isolating artifacts across hosts. Outputs are organized in per-site layouts to preserve fonts, colors, assets, and behavior for pixel-perfect recreation.

The best way to port a website experience is to reverse-engineer the live site into an isolated worktree with auditable artifacts. You provide the target URL, and the skill extracts the necessary CSS, assets, and content for reliable porting.

Yes, website cloning satisfies browser-automation prerequisites to capture complex UIs and interactions accurately. This ensures that the extracted assets and CSS preserve the original site's behavior for a pixel-perfect recreation.

Website clone outputs are organized in per-site directories like docs/research/<hostname> and docs/design-references/<hostname> to support multi-site projects. This per-site layout isolates artifacts across hosts during parallel builder-dispatch orchestration.

You should avoid parallel builder workflows for website cloning when working with a single, simple static page that lacks complex UIs or interactive elements. In those cases, standard extraction without isolated worktrees may be more efficient.