← All guidesThe full lessons are inside AI Monetizers.Try it free for 7 days
Free guide · stj

Rebuild an app with Claude, then fix what its users hate.

Replica is a free pack of 11 Claude skills. It maps an app from public info, rebuilds it clean, tests it, then reads real reviews to find what to fix. This is the exact setup I used in the video.

! The original rebuild + fix Your version
Rebuild the app, then fix the one thing its users complain about most.
11skills, one job each
FreeMIT license
5skills to run your first clone
01

Install it in 1 minute

Pick the way that matches how you use Claude.

Open a new chat and paste this:

https://github.com/Jakeschincariol/replica-skill

install skill

Run this inside Claude Code:

/plugin marketplace add Jakeschincariol/replica-skill

Then open /plugin and install the Replica skills from that marketplace.

Clone the repo, then copy the replica-* folders into your skills folder:

git clone https://github.com/Jakeschincariol/replica-skill
  • All projects: ~/.claude/skills/
  • One project only: .claude/skills/ inside that project
Check it worked. Type /replica in Claude Code. You should see all 11 skills in the list.
02

The 11 skills, in order

Each one reads what the step before it wrote, so run them top to bottom.

Understandrecon
architect
design
Buildbuild
backend
Checktest
diff
Improveentrepreneur
brand
Shiplaunch
deploy
Step 1
/replica-recon

Maps the app: every screen, every user flow, the data it stores and a feature list. From public pages, screenshots, store listings and your own account.

Step 2
/replica-architect

Picks the stack, writes the database schema and plans the API from the recon map.

Step 3
/replica-design

Rebuilds the design system: colours, type, spacing and every component, with your own assets.

Step 4
/replica-build

Rebuilds the screens, core flow first, then every screen with all its states. Writes every line fresh.

Step 5
/replica-backend

Adds login, the database, Stripe payments, email and integrations through official APIs only.

Step 6
/replica-test

Clicks through every flow looking for bugs. Happy paths, edge cases and a report for each bug.

Step 7
/replica-diff

Scores how close your clone is to the original and lists what is still missing.

Step 8
/replica-entrepreneur

Reads real public reviews, ranks what users hate and what is missing, and turns it into a fix plan.

Step 9
/replica-brand

Renames and rebrands it so it is yours. New name, palette and logo brief, plus a sweep for anything left from the original.

Step 10
/replica-launch

Writes the landing page, the pricing and the App Store and Google Play listings.

Step 11
/replica-deploy

Puts it live on your own domain, after a preflight check that tests pass and the rebrand is clean.

03

Run your first clone

The fast path: 5 skills, 1 small app. Paste each prompt, swap in your app, and wait for it to finish before the next one.

What Replica creates in your project
replica/ recon.md the recon map features.csv the feature list screens/ reference screenshots, never shipped reviews.csv the reviews it collected feedback.md ranked complaints with linked quotes

Map the app

/replica-recon Map out [APP NAME]. Web version only. Just the core flow, the one thing people pay for. Use public pages, help docs and screenshots.

Writes replica/recon.md, replica/features.csv and reference screenshots in replica/screens/. It asks which app, which slice and who it is for. Answer all 3.

Rebuild it

/replica-build Build the app shell and the core flow from the recon map first. Then the rest of the screens.

Builds screen by screen and ticks off the feature list as it goes. The original's screenshots stay as reference and never go into the build.

Test it

/replica-test Click through every flow and find bugs. Give me a report with severity and steps for each one.

Writes a test plan from the recon flows, runs it, and gives you a bug list. Fix the high-severity ones before you move on.

Find what users hate

/replica-entrepreneur Read the public reviews for [APP NAME]. Tell me what users hate, what is missing and what is still unsolved. Then build the top fix into my version.

Writes replica/feedback.md with ranked themes and linked quotes. More on this below.

Make it yours

/replica-brand Give my version a new name, palette and logo brief. Then sweep the codebase for anything left from the original.

Gives name options with the trademark and domain checks to run, a new palette checked for contrast, and a leftover sweep.

04

The review skill is the reason to use this

A straight copy of an app has no reason to exist. /replica-entrepreneur finds the reason: what the original's users complain about, in their own words.

Public reviews Ranked themes Hate Missing Unsolved Your fix plan Bar lengths are illustrative. Your real counts come from the reviews it reads.

Where it reads

  • App Store and Google Play reviews
  • G2, Capterra and Trustpilot
  • Reddit and Hacker News threads like "X alternative" and "switched from X"
  • The app's own feature-request board and changelog, so you don't fix what is already fixed

What you get: 3 ranked lists

What they hateComplaints about things the app does now.
What is missingFeatures people ask for by name.
What is unsolvedProblems nobody has fixed yet.

Each item shows the problem, how many reviews mention it, how many sources, and linked quotes. Themes with fewer than 3 reviews are flagged as thin.

Read the 3 and 4 star reviews. "Love it, but..." is where the best fixes are. The skill weights low ratings and recent reviews higher, and it also lists low ratings that matched no theme. Read that list yourself.

Its rules

  • Every quote is copied exactly and linked to its source. No made-up reviews, counts or ratings.
  • It reads review pages the way a person does. No scraping sites whose terms forbid it.
  • Reviewers are research, not testimonials. Don't put their words on your landing page.

Aim for 100+ reviews across at least 3 sources for results you can trust.

05

Pick the right app first

Your first clone decides whether this feels like magic or a mess. Start small.

Good first picks

  • A simple web app: habit tracker, to-do list, notes, booking page
  • One core flow you can describe in a sentence
  • Lots of public reviews to read
  • An app you already use, so you know the flows

Skip for now

  • Banking, health or anything holding sensitive data
  • Social networks and marketplaces that need other users to work
  • "All of Notion." Pick one slice, like pages and sharing
  • Apps whose terms ban using your account to build a competitor
06

What it won't do

Straight from the repo. Know this before you build.

  • No perfect clone guarantee. Results depend on how complex the app is. Simple apps come out closest.
  • Clean-room only. It rebuilds features and flows. It never copies source code, logos, trademarks, copy or private APIs.
  • No getting past logins or paywalls. Public sources and your own account only.
  • Check before you sell. Run the trademark checks /replica-brand lists, read the terms of anything you used, and talk to a lawyer before launch if money is involved. This guide is not legal advice.
07

Your checklist

Keep going

Build this with other people

In AI Monetizers I post breakdowns like this one, and members share what they build with Claude. There's a free trial.

Join AI Monetizers