Real case studies

## Original vs. clone — side by side.

Not cherry-picked stills. In each clip the live site is on the left and the clone-team build is on the right — driven in lockstep so both stay at the exact same point. One recording, perfectly in sync.

### 🎵 Mubasic

Animated split-hero · GSAP sliding letter-bars · `mubasic-test.webflow.io`

Visit original ↗

### 🧬 Wembi

Lenis smooth-scroll · scroll-driven 3D · reveal animations · `wembi.ai`

Visit original ↗

↑ Real screen recordings of the live sites and their clone-team builds — not mockups.

Two deliverables, every run

## Not just pixels — understanding.

Most "AI clone this site" tools hand you a rough one-shot and call it done. clone-team gives you the clone and the blueprint.

🎨

### An exact UI clone

Pixel-perfect, behavior-accurate, in your stack — React, Next.js, Vue, Svelte, Angular, or plain HTML/CSS — independent of the source site's stack.

📐

### ARCHITECTURE.md

Routes, observed API/network surface, inferred data model & entities, auth/session flow, state & navigation, and step-by-step user journeys.

The engine

## A dynamic Workflow that can't skip the test.

The build/test loop is a deterministic program, not a model's good intentions. "Done" is literally a loop condition in code.

user ⇄ MANAGER (main thread) requirements, creds, recon, │ foundation, final regression, pause/resume │ launches a DYNAMIC WORKFLOW that ENFORCES the loop ▼ per page, in parallel: extract → spec → DEVELOPER builds → TESTER full regression → (NG) fix → re-test → OK ✅ in parallel: BACKEND ARCHITECT writes ARCHITECTURE.md then: assemble → final regression → fix
🔒

#### The Tester gate is unskippable

Per page, a `while` loop runs until the Tester returns `OK`. No human, model, or deadline pressure can bypass it.

🔀

#### It adapts to the work

One-page site → one builder. Nine-page site → nine, concurrently. The Workflow reads the page list and fans out.

⚙️

#### It sizes the fleet to your PC

A capacity probe reads free memory and computes how many builders to run at once — fast on a big box, safe on a laptop.

↩️

#### Pausable & resumable

Across sessions and usage-limit cutoffs — progress is reconciled against a durable `state.json` + on-disk artifacts.

🛡️
Gate 1 — Tester Inside the loop, every round
✅
Gate 2 — Manager Final human sign-off
Requirements & setup

## Install once. It bootstraps the rest.

You need Claude Code, Node.js + npm, and a Chromium browser. Everything else — the companion skills and the `agent-browser` CLI — installs itself on first run, project-local, so your global setup stays clean.

Full install guide Read the case study