Verified Agent Skill record

Clone Website

Reverse-engineer and rebuild one or more target URLs as pixel-perfect Next.js clones. The skill inspects each page section with browser automation, writes detailed component specification files, extracts real content and assets, and dispatches builder agents to construct components in parallel under collision-resistant per-site and per-page paths.

Tasks

Clone a single target URL as a pixel-perfect Next.js page, replacing the untouched scaffold at src/app/page.tsx so the clone is served at /
Clone multiple URLs from one origin while preserving each pathname as a distinct App Router route
Write a per-component specification file under docs/research/<site-key>/<page-key>/components/ before dispatching each builder agent
Download page assets (images, videos, fonts) to public/sites/<site-key>/<page-key>/ via a uniquely named script such as scripts/download-assets-<site-key>-<page-key>.mjs
Extract interactive behavior (scroll triggers, hover states, tabbed content) by capturing computed CSS before and after triggers and documenting the interaction model
Verify the merged project compiles with npx tsc --noEmit in each builder and npm run build after merging worktrees

Inputs

One or more target URLs in the user request
Optional user overrides for fidelity level, customizations, or scope
A Next.js + shadcn/ui + Tailwind v4 scaffold already in place and passing npm run build
An available browser MCP tool (Chrome MCP, Playwright MCP, Browserbase MCP, or Puppeteer MCP)
For separate origins, a user-provided or approved prepared Next.js project root per origin

Outputs

Next.js App Router route files under <app-root>/src/app/
Component files under src/components/sites/<site-key>/<page-key>/ (shared components under shared/)
Assets under public/sites/<site-key>/<page-key>/ (shared assets under shared/)
Full-page desktop (1440px) and mobile (390px) screenshots under docs/design-references/<site-key>/<page-key>/
Research artifacts and component spec files under docs/research/<site-key>/<page-key>/
Asset-download scripts under scripts/
An output plan listing every target URL, site-key, page-key, destination route, and artifact roots

Limitations and checks

Out of scope by default: real backend/database, authentication, real-time features, SEO optimization, and accessibility audits
Fidelity defaults to pixel-perfect exact emulation with no customization unless the user specifies otherwise
URLs differing only by query string or fragment share a pathname and must have route and state behavior resolved explicitly
The skill cannot proceed if no browser MCP tool is available or if any target URL is invalid or inaccessible
Conflicting existing routes require the user to decide whether to update, choose another route, or skip
Confirm every planned route, artifact root, screenshot root, component root, asset root, and downloader filename is unique or an explicitly approved shared location before writing
Verify each built route resolves at the exact normalized URL before completion
Confirm a spec file exists for every component before its builder agent is dispatched