monjurkuet

Web Clone — AI skill for Claude Code

AI community

Methodology + executable probes for faithfully cloning any website (static / React / WebGL / WordPress) — real source first, never AI-hallucinated code.

How to install Web Clone

This entry records only its repository, not the path inside it, so there is no exact command to give. Open monjurkuet/web-clone and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Web Clone does

Methodology + executable probes for faithfully cloning any website (static / React / WebGL / WordPress) — real source first, never AI-hallucinated code. English fork of Jane-xiaoer/claude-skill-web-clone with portability fixes.

Alternatives in AI

  • Guizang Ppt Skill — AI-agent Skill for generating polished HTML slide decks: editorial magazine and Swiss layouts, image prompts 24.9k ★
  • Claude Skill Web Clone — Methodology for faithfully cloning any website (static / React / WebGL) — without copying AI-hallucinated code 969 ★
  • Agentty — AI pair programming in your terminal — one static binary, sub-ms startup, any model 597 ★

README

🪞 Web Clone · Website Cloning Methodology

Reproduce any website — from a single-file static page to a WebGL-heavy interactive demo — without faking it from AI hallucinations.

A fork/adaptation of [Jane-xiaoer/claude-skill-web-clone](https://github.com/Jane-xiaoer/claude-skill-web-clone) (MIT), improved for portability and fully translated to English.

What this skill does

You see a website you love. You want to clone it — to learn how it works, remix it into your own thing, or run it offline. AI tools love to produce *plausible-looking* "clone analysis" documents full of code blocks that are entirely fabricated and break the moment you run them.

This skill is a **methodology plus executable probes that put real source first**, with a 6-step decision tree:

  • Static HTML/CSS sites → wget --mirror
  • React / Vue / Next content sites → rebuild on a template
  • Multi-page sites → crawl internal routes before designing templates
  • Interactive sites → record hover / click / scroll / canvas-drag states before cloning
  • WebGL / Canvas / Three.js heavy frontends → reverse-engineer real source, line by line; with no findable source, runtime frame-capture + a baseline-first replay gate with SOURCE / PARTIAL / GUESS evidence grading
  • Static-built sites (Astro / Vite SSG / Hugo), even WebGL-heavy → mirror-site.mjs full-scroll-captures and mirrors every deployed asset (incl. runtime-fetched .sog/.buf/.wasm) for a true 1:1 clone
  • Server-rendered multi-page sites (WordPress etc.) → sitemap-driven batch mirror: enumerate all URLs from sitemap_index.xml, download pages + assets concurrently, rewrite (strip tracking, localize URLs), verify in a real browser
  • Verify in a real browser, document the truth, replace content with yours
  • Visual / rebrand modes → distill a versionable design-dna.json (design tokens + style + effects), then "keep the DNA, swap the content"

Iron rule: real source first, never copy AI-guessed code

Any AI-writt