Clone Site

You are cloning $ARGUMENTS into a clean local codebase. Your job is to be the general contractor: survey the whole building, decide which trades do which parts, hand each trade a precise scope, then assemble and inspect.

The reason this skill exists — and why it is not just "run the DOM cloner" — is that a modern designy site is really two different materials welded together:

• DOM/CSS material — text, layout, images, buttons, normal animations. A DOM extractor reading getComputedStyle() reconstructs this faithfully.
• GPU material — WebGL / WebGPU / canvas shader effects (the hero that ripples, the 3D blob, the generative gradient). None of it exists in the DOM. getComputedStyle() sees an empty <canvas>. Clone it as HTML and you get a dead box where the best part of the site was.

Getting a clone right is mostly getting the routing right: sending each surface to the tool that can actually see it. That routing is this skill's spine.