finds.dev← search

// the find

JCodesMore/ai-website-cloner-template

★ 16,922 · TypeScript · MIT · updated Jun 2026

Clone any website with one command using AI coding agents

A Next.js template that orchestrates AI coding agents to reverse-engineer websites into clean React code. You point it at a URL, and the agent pipeline screenshots the site, extracts design tokens, writes component specs, then spawns parallel builders in git worktrees to reconstruct each section. Aimed at developers who need to migrate a legacy site or recover lost source code.

The parallel worktree build strategy is genuinely smart — each section gets its own agent running concurrently instead of serializing everything through one context window, which would degrade quality on larger sites. The sync scripts that regenerate per-agent instruction files from a single source of truth (AGENTS.md + SKILL.md) are the right call; maintaining 13 platform-specific copies by hand would rot immediately. Using getComputedStyle() values in the component specs rather than eyeballing CSS is the correct approach — you get actual pixel values instead of the agent hallucinating spacing. Broad agent support (Claude Code, Cursor, Codex, Aider, etc.) with zero forking of the core skill logic is well-executed.

The output quality is entirely a function of the underlying AI agent — the template is scaffolding, not a guarantee, and the README's own demo shows a passable but not pixel-perfect result. There's no mention of how dynamic content (SPAs with client-side rendering, auth-gated pages, infinite scroll) is handled; the reconnaissance phase likely misses significant portions of those sites. Next.js 16 and React 19 are bleeding-edge and several common ecosystem packages aren't there yet, which will bite you the moment you try to add any third-party component library beyond shadcn. The ethical disclaimers in 'Not Intended For' are self-policed and unenforceable — this is a scraping and reproduction tool, and its most obvious misuse is exactly the thing it says not to do.

View on GitHub → Homepage ↗

// want more like this?

We dig through GitHub every week and send a few repos picked for what you actually care about — each with an honest take like this one.

Get finds in your inbox → Search again →