clone-site

Extracts design tokens, interactions, and motion from reference sites before rebuilding them.

Updated Jun 9, 2026
One-click install
npx skills add https://github.com/timikalo7/Execute --skill clone-site-timikalo7
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: clone-site
Source: https://github.com/timikalo7/Execute/tree/main/.claude/skills/clone-site
Command: npx skills add https://github.com/timikalo7/Execute --skill clone-site-timikalo7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Cloning a website from screenshots alone forces slow guess-and-check iteration on type scales, colors, and motion. This Skill enforces a proven order of operations that reads the reference's actual DOM and design system first, turning a multi-day guessing loop into a short, spec-driven build. ## Core Features & Use Cases - Design System Extraction: Runs design-system-extract.mjs to pull type scales, weights, color tokens, border radii, and animated elements into a committed design-tokens.json spec. - Interaction and Motion Capture: Drives the live site to record hover, focus, menu, and preloader states, plus detects scroll-driven axis motion that single screenshots cannot reveal. - Structured Iteration: Builds against captured slices and validates with a gauntlet loop (pixel profile, lateral motion, independent judge) instead of subjective impressions. - Use Case: When asked to "build a landing page like this reference site," load this Skill first to extract the real tokens and interactions, then build from the spec rather than from screenshots. ## Quick Start Clone the design of https://example.com by first extracting its design tokens and interaction states, then building the page from that spec.

Frequently Asked Questions about clone-site

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

FAQPage Schema
How do I clone a website's design accurately?▼

Extract the design system from the live DOM first using design-system-extract.mjs, which reads exact font sizes, weights, and color tokens. Then capture interaction states and page slices before building, rather than inferring metrics from screenshots.

How to extract design tokens from a website?▼

Run node .claude/skills/browser-drive/design-system-extract.mjs with the target URL and an output path. It produces a JSON file with type families, the full scale with ratios, colors by frequency, border radii, and animated elements.

Why does cloning a site from screenshots take so many iterations?▼

Screenshots only show rendered pixels, so type scales and colors must be guessed one metric per iteration. Reading values directly from the DOM is exact and instant, and scroll-driven motion is invisible in any single still frame.

Can scroll-driven animations be detected from screenshots?▼

No. A still of a travelling element looks identical to a static one. Use axis-motion.mjs against captured slices to find horizontal travel driven by vertical scroll, rotation, scrub, and counter-scroll effects.

What are the limitations of automated visual judging when cloning sites?▼

A judge is an evaluator, not an oracle; findings can be sampling artifacts or contradicted by the reference itself. Verify every finding against a named reference slice before acting, and suspect the comparison baseline before adjusting tolerances.