Want to access all premium content?

Become a paying subscriber to get access to all courses, guides like this, prompts and skills library, and $500+ worth of AI tools.

Remake is a free, open-source tool that runs in Claude Code. It rebuilds a page in a folder you control, compares the result with the reference on desktop and mobile, and lists the text, images, fonts, and other assets you still need to replace. You can preview the result on Vercel behind a passcode, with the code in a private GitHub repository.

Start with one page you own or have permission to remake. Free GitHub and Vercel accounts cover the personal preview in this walkthrough. The simple page in the test took about 15 minutes to rebuild. You’ll need the Claude desktop app on a paid plan, plus GitHub and Vercel accounts.

Step 1: Set up your accounts. Get GitHub, Vercel, and Claude Code ready.

Step 2: Pick a reference site. Start with a single public landing page.

Step 3: Run the remake. Give Claude the URL and review the visual comparison.

Step 4: Make it yours. Add your brand, copy, and images.

Step 5: Check before going live. Review the swap board and test the site before removing the passcode.

Step 1: Set up your accounts

Create a GitHub account. Then open Vercel and choose Continue with GitHub to connect the two.

Open the Claude desktop app and switch to Code. Select This computer, choose a new, empty folder, and set the mode to Auto. The walkthrough used Opus 5.5 at Medium effort.

With /goal, Claude continues across turns. In Manual mode, tool approvals can interrupt the run. The /goal command needs Claude Code 2.1.139 or later, so install any available update before starting.

Remake installs its Node packages, screenshot browser, and Vercel command-line tool during setup. If Claude reports that the GitHub CLI is missing and you don’t have Homebrew, use the GitHub CLI installer.

Step 2: Pick a reference site

A single public landing page, portfolio, or product page gives you an easy first test. One Page Love, Godly, SiteInspire, and Awwwards can help you find layout ideas.

Good first project

Save for another approach

One long marketing page

Pages behind a login

Text, photos, and scroll effects

Checkout, sign-in, or banking pages

A page that loads without a bot check

Live data, maps, or chat apps

A layout that suits your content

Heavy 3D or WebGL scenes

The test used 101 GenAI, a one-page site with scroll animations. Remake also picked up its cookie banner. During the swap, check whether the banner belongs on your site.

Step 3: Run the remake

Replace the example URL with your reference page and paste the prompt into Claude Code.

❝

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

Claude reads the Remake repository, installs the engine in ~/.remake, and opens the reference in a background browser at desktop and phone sizes. It compares the screenshots and adjusts the rebuild where it falls short.

Check

Pass mark

Each still desktop and phone screen

98% of stable pixels match

Each of 24 scroll frames

95% match

Page height

Within 4 pixels

In the test, four phone screens started around 97% and reached 100% after revisions.

Once Claude pauses before deployment, review what it plans to publish. To approve the passcode-protected preview, reply:

ship it

You may see “Still waiting” messages while Claude waits. After you approve, follow the GitHub and Vercel authorization prompts. If the Git push fails after you sign in, use this prompt.

Run gh auth setup-git, then run ship again.

Look for REMAKE COMPLETE at the end of the report, along with the preview link, passcode, and private GitHub repository.

Open the preview, enter the passcode, then visit /_remake/. The proof page shows the lowest desktop, phone, and scroll-frame scores, plus how much of the content you’ve replaced. Below the scores, you can compare the original and remake side by side.

Let the page finish loading and reload once if a pair shows different sections. If the run ends at 100 turns with REMAKE NOT DONE, ask Claude which checks still fail.

Step 4: Make it yours

Open /_remake/swap/ on the preview. The swap board counts the pieces to replace as slots and shows what Claude needs from you for each group.

Put your logo, three to six of your own photos, and a short About description in one folder. In Finder, you can drag the folder into the message box to insert its path. Fill in the brackets before sending this prompt.

❝

Make my remake mine. My company is [name]. We [what you do] for [who]. My brand colors are [colors]. My logo, photos and About text are in [folder path]. Rewrite every text block in my voice at the same length, so the layout holds. Replace every picture with a new one made for my company, in the same spot, shape, light and colors, and never use their people, text or logos. Swap any paid fonts for free look-alikes. Ask me for anything else you need.

Claude writes the new copy into content.json and runs remake apply. For replacement images, Remake can choose among these routes depending on your setup.

Route

What it uses

Codex image generation

An installed, signed-in ChatGPT or Codex app

OpenAI or Gemini API

An API key you’ve configured

Stock images

Public-domain or CC0 images from Openverse or Wikimedia Commons

Generated artwork

Artwork in your brand colors when the other routes are unavailable

Remake records image credits and can replace paid fonts with similar options from Google Fonts. Review the selected images and fonts as part of the swap.

Scroll through the page on desktop and mobile. Look for clipped text, lines that run together, and icons from the reference. Tell Claude which sections need a fix. The number of slots can change as you remove sections. In the test, it fell from 244 to 148.

Step 5: Check before going live

Keep the preview behind its passcode while you review the swap board. Once it reaches 100%, go through each group and verify the result yourself.

Check the client logos, social links, footer links, and forms. Remove any sections that don’t apply to your business. Click the buttons and confirm that each takes visitors where you expect.

The visual match may drop once you change the branding and content. Use the original comparison to review the rebuild and the live preview to judge your version. The swap board tracks content replacements. Review your permission to use any remaining design or code separately before publishing.

Once you’re ready to publish, ask Claude:

The swap board reads 100%. Remove the passcode and redeploy the site.

If Claude offers to remove the proof and swap pages from the public deployment, accept so the reference screenshots and text stay local. Open the public link afterward and test it on your phone. Running ship again can restore the passcode, so check the public URL after another deployment.

Use cases

Once your first remake works, try these three jobs.

Use case #1: Add a section of your own

Ask Claude to add something your site needs, such as a collection of guides.

Add a new section to my remake, right after the [section name] section, that lists [your items]. Each card gets a title, one short line and a link. Copy the style of the existing cards.

Check the new cards at phone size and open each link.

Use case #2: Get an editable codebase

Ask Claude to convert the remake into a Next.js project you can edit section by section.

Turn my remake into a Next.js app, section by section, keeping the score passing.

Review the visual comparison after each section to catch layout changes early.

Limitations

Remake is a third-party tool for Claude Code. Its README covers Mac setup, and the ChatGPT image route described in the guide looks for the Mac apps.

The rebuild covers the visible page. Logins, databases, payments, and forms that send email need their own setup. A bot check can stop a run. With the prompt above, a single-page run can use up to 100 turns, and a full-site run can use more.

The original walkthrough lists Vercel Hobby for personal, non-commercial use and Vercel Pro at $20 per month per user for a public business site. Check the plan before you publish.

Closing

Start with one landing page and review the desktop and phone comparisons while the preview is private.

Then add your own content, open the finished site as a visitor, and test the links, buttons, and forms before you send anyone the link.

See you in the next one :)