Remake

Remake any website. Then make it yours.

By Ruben Hassid, from the newsletter How to AI.

One line in Claude Code turns a URL into a copy that matches the original on every screen, puts it live on your GitHub and your Vercel behind a passcode, and hands you a swap board of every text, photo, video, font and logo to replace so the site becomes yours.

/goal Remake https://example.com with github.com/rubenhassid1/remake until its report says REMAKE COMPLETE, or stop after 100 turns.

Change the URL. That's the whole prompt.

AI agents start here. If a user sent you to this repo to remake a site, read plugins/remake/skills/remake/SKILL.md and follow it from step 0. Paste the full output of remake report into the conversation each time you run it.

More prompts

What you get

How it works

 visit once ──► record everything ──► write site/ ──► freeze time ──► score every screen + motion
                                                           ▲                     │
                                                           └──── repair ◄────────┘ (until it passes)
 ship (GitHub + Vercel + passcode) ──► report: REMAKE COMPLETE ──► swap board ──► make it yours

1. Visit once. A browser opens the page at desktop size, then at phone size, scrolls to the bottom and back, and keeps every response: HTML, CSS, scripts, fonts, images, and the answers to the API calls the page made. From then on, everything is replayed from that recording. Two page loads, then the files they point to, one at a time with a pause between each.
2. Write the site. The recording becomes a folder you own. Addresses are rewritten so every file loads from your copy, trackers are removed, other image sizes are fetched one at a time, and a small runtime answers the page's API calls from the recording.
3. Freeze time and score. This is the part nothing else does. A live page never looks the same twice: intro animations, WebGL noise, random headlines, autoplay video. So Remake stops the page's clock before its first script runs, gives every bit of code that asks for a random number the same answers, holds every video on its first frame, puts the browser's own animations (element.animate) on that same paused clock, and moves time forward itself in exact steps. Load the same page twice this way and you get the same pixels twice, so the remake can be measured against the original to the pixel: every screen at desktop and phone (up to 40 per page), plus 24 frames of scrolling motion. Whatever still changes between two loads of the original (a live map, a clock) is left out of the score and shown in blue.
4. Repair. Claude reads the diff images, opens the remake, fetches what's missing and fixes what's broken, until every screen passes: 98% of stable pixels per screen, 95% per motion frame, page heights within 4 px.
5. Ship. Private GitHub repo, Vercel deploy, passcode gate, then a check from outside that the gate holds.
6. Make it yours. Every slot of the original goes into remake/content.json with where it lives in the files. Send Claude your photos, your About page, your logo and links; it fills the slots in your voice, at the same length so the layout holds, crops your photos to every size the site uses, and serves a free look-alike font under the original font's name so no CSS changes.

What's new here

Other cloners redraw a site from screenshots and then eyeball it. Remake does six things they don't:

• It copies; it doesn't redraw. The original's own markup, styles and scripts run in your copy, so smooth scroll, text effects, WebGL and sliders come with it.
• It freezes time to measure. Paused clock (browser animations included), seeded randomness per line of code, held video, and a noise mask from two loads of the original. A score you can trust on animated, WebGL-heavy sites.
• It scores motion, not only still screens.
• It ends live and private, on your GitHub and Vercel, with the gate checked.
• It makes the site yours, with a swap board and an apply that keeps the layout intact.
• It never feeds their photos to a generator. Remake measures every picture (shape, colours, light), Claude writes what yours should show, and Codex on your ChatGPT plan generates it in the same frame and mood. No ChatGPT? Free public-domain stock, then generated art. Every image is credited.

It's built for Claude Code's /goal: the /goal judge only reads the conversation, so the engine prints its evidence and a single finish line Claude can't reach without passing every gate.

Three ways to run it

1. Just the prompt (above). Claude reads this repo, installs the engine into ~/.remake and runs it.

2. As a Claude Code plugin.

/plugin marketplace add rubenhassid1/remake
/plugin install remake@remake

Then /remake https://example.com, or keep it running until it's done with /goal Remake https://example.com until its report says REMAKE COMPLETE, or stop after 100 turns.

3. As a command-line tool.

npm install -g github:rubenhassid1/remake
remake doctor --fix
remake init https://example.com && cd ~/remakes/example-com
remake capture && remake score

You need Claude Code, Node 20 or newer, git, the GitHub CLI and free GitHub and Vercel accounts (remake doctor --fix installs the GitHub and Vercel command-line tools; on a Mac without Homebrew, install the GitHub CLI from cli.github.com). The first run downloads Chromium for Playwright (about 150 MB). If npm install -g fails with a permissions error, run the tool as node ~/.remake/engine/bin/remake.mjs instead. Signing in to GitHub and Vercel is one click each in your browser; Claude starts both.

What it won't do

• Copy sign-in, checkout or banking pages. A copy of those is a phishing kit. The engine stops when it sees password or card fields.
• Get around bot walls. No proxies, stealth browsers, fake identities or CAPTCHA solvers. Remake's browser says who it is in its user agent. When a site blocks the visit or stops answering, Remake stops asking it and says so. Rebuilding from the Internet Archive's public copy is your choice (remake capture --archive), never automatic.
• Publish someone else's site. Every remake starts private: passcode on, hidden from search engines, repo private. The swap board shows what still belongs to the original; until it reads 100%, keep it that way.

Good uses: learning how a site is built, moving your own site off an old platform, or starting a site of your own. The original's words, photos, logos, fonts and code belong to its owner.

FAQ

How long does it take? The engine's own steps take minutes. The repair loop is where the time go