
Clone Website
Reverse-engineer and clone a website in one shot, extracts assets, CSS, and content...
Install
npx skills add yournextstore/yournextstore --skill clone-website -g -a claude-code -y- Repository
- yournextstore/yournextstore5.5k
- Category
- Design
- Updated
- 4d ago
- License
- MIT
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Reverse-engineer and clone a website in one shot, extracts assets, CSS, and content section-by-section and proactively dispatches parallel builder agents in worktrees as it goes. Use this whenever the user wants to clone, replicate, rebuild, reverse-engineer, or copy any website. Also triggers on phrases like "make a copy of this site", "rebuild this page", "pixel-perfect clone". Provide the target URL as an argument.
Clone Website
You are about to reverse-engineer and rebuild $ARGUMENTS as a pixel-perfect clone.
This is not a two-phase process (inspect then build). You are a foreman walking the job site, as you inspect each section of the page, you write a detailed specification to a file, then hand that file to a specialist builder agent with everything they need. Extraction and construction happen in parallel, but extraction is meticulous and produces auditable artifacts.
Tool: This skill uses
agent-browserfor all browser automation, screenshots, DOM inspection, JavaScript evaluation, clicking, scrolling, and viewport control. If you need detailed command reference beyond what's shown here, invoke the/agent-browserskill.
Pre-Flight
- agent-browser is required. Test it immediately by running
agent-browser open about:blank. If it's not installed, runnpm install -g agent-browser && agent-browser install. This skill cannot work without browser automation. If you need detailed command reference, invoke the/agent-browserskill. - Read
TARGET.mdfor URL and scope. If the URL doesn't match$ARGUMENTS, update it. - Verify the base project builds:
npm run build. The Next.js + shadcn/ui + Tailwind v4 scaffold should already be in place. If not, tell the user to set it up first. - Create the output directories if they don't exist:
docs/research/,docs/research/components/,docs/design-references/,scripts/.
Guiding Principles
These are the truths that separate a successful clone from a "close enough" mess. Internalize them, they should inform every decision you make.


