~/guides/REPLICA.md

Guides / Claude Code

Replica: 11 free Claude skills that rebuild an app you pay for, as your own version

Replica maps the original app, rebuilds it screen by screen, tests it, reads real reviews to fix what users hate, then rebrands and ships it. Install + order.

That app you pay for every month: Claude Code can now rebuild your own version of it. The tool is Replica, 11 free Claude skills (MIT licence); I checked its GitHub page and README on 30 October 2026. This is the full version of my REPLICA reel: how it works, how to install it, the order to run the 11 skills, and the line it will not cross.

01What you get

Replica does not copy code and it does not crack anything. It rebuilds the features and flows of the app you want to replace, then reads that app's bad reviews and fixes the things users hate in your version.

In this guide:

  1. Replica's 5 big steps: map, rebuild, test, fix the complaints, ship.
  2. The two commands that install it in Claude Code.
  3. The order of the 11 skills and what each one does.
  4. What it deliberately will not do: no copying the original's code, logo, copy or content.

02What it is: 11 skills, no copied code

Reel frame: the replica-skill README with two lines highlighted; "copy code" and "crack" strips struck through
The official README: 11 skills that rebuild what an app does, never what it owns (screenshot 30 Oct 2026).

The README is explicit: it rebuilds what an app does (features and flows), clean-room style; the original's code, logo, copy and content are off limits, and the skills enforce it. Free, MIT, no signup, no API key.

Type in Claude Code (from the official README)
/plugin marketplace add Jakeschincariol/replica-skill
/plugin install replica-skill@replica-skill

03Step 1: map every screen and flow of the original

Reel frame: a giant blocky phone shows a blueprint of six screens and flow arrows; Claw'd holds a magnifier
Step 1, recon: map the original's screens, flows and data model first.

/replica-recon works from public pages, screenshots, store listings and your own account, and writes out the screens, flows, components and an inferred data model into replica/recon.md plus a feature list. Every later skill reads that folder and continues.

First command (replace the [])
/replica-recon [URL of the app you want to replace]

04Steps 2 and 3: rebuild screen by screen, then click through every flow

Reel frame: the giant phone fills in band by band with a booking page; Claw'd holds a hammer
Step 2, illustrated: rebuilding screen by screen (the app on the phone is a ChatGPT illustration).

The README's order: architect plans the stack, schema and API → design rebuilds the design system as your own tokens → build rebuilds screen by screen → backend wires auth, database, payments and integrations.

Reel frame: three small black bug blocks on the phone screen, squashed one by one into green check marks
Step 3, illustrated: test clicks through every flow and catches bugs.

/replica-test writes a test plan from the flows recon found, clicks through every flow and logs bugs by severity. /replica-diff then compares your version with the original and gives a parity score plus what is missing.

05Step 4: read the bad reviews and fix what users hate

Reel frame: lights down, spotlight on the monitor, the README line about the Entrepreneur skill highlighted
The best step: the Entrepreneur reads what users actually hate and fixes it in yours (README screenshot).

This is the part I like most. /replica-entrepreneur gathers real reviews from the App Store, G2, Capterra and Reddit, groups the complaints with counts and linked quotes, and turns them into a fix list and a positioning angle for your version. The README's example is a booking app: per-seat price jumps, no text reminders, guests confused by time zones; so your version gets flat pricing, SMS reminders and a time-zone confirm step.

Reel frame: four sticky notes on a cork board flipping from red complaints to green "fixed"
Complaints flipping to "fixed" one by one (the note texts are my illustrative versions).

06Step 5: give it your name and ship it on your domain

Reel frame: a sign reading "你的 App" and "yourapp.com" drops in beside the giant phone showing a booking confirmation
The last step, illustrated: your own name and domain (the app screen is a ChatGPT illustration).

/replica-brand names it (with the trademark and domain checks to run), gives it a new palette and logo brief, then sweeps the code until nothing of the original is left. /replica-launch writes the landing page, pricing and store listing, and /replica-deploy runs the preflight, gives you the DNS records for your domain and ships when you say go.

The order of the 11 skills (README)
recon → architect → design → build → backend → test → diff → entrepreneur → brand → launch → deploy

07Good to know

  1. It rebuilds features and flows only, never the original's code, logo, copy or content; check trademarks yourself before you pick a name.
  2. The skills are free, but Claude Code uses your Claude plan or API credits; running all 11 steps is a big project and takes a fair amount of usage and time.
  3. The tools need Python 3.8 or newer; nothing to pip install.
  4. Only install from the official repo Jakeschincariol/replica-skill, not look-alikes.
  5. The "Slotly" app in the reel and this guide is a ChatGPT illustration, and the sticky-note complaints are my own examples.

Sources

Related guides