Replica: clone any app with Claude Code, then fix what its users hate, Quentin IA Marketing

Replica is a pack of 11 free skills for Claude Code. One skill maps an existing app, another rebuilds it, another tests it. And the Entrepreneur reads what its users hate, so your version fixes exactly that.

This guide gives you the setup, the order to run the skills in, the skill to use first and what the pack refuses to do. Checked on November 6, 2026 against the repo, plugin validated with Claude Code 2.1.318.

Claude AI Lab

The Claude AI Lab is my Skool community where I share my Claude systems and the more advanced modules. Access is $67/month.

Join the Lab →

skills, from mapping to going live

7,841

GitHub stars on November 6, 2026

API keys needed, MIT license

✅What you need

Claude Code. Check with claude --version.

Python 3.8 or newer. It runs the pack's 6 small tools. Nothing else to install.

The address of the app to study. Its website, its App Store or Google Play listing. Your own account on the app helps, if you have one.

The code lives in the Replica GitHub repo.

Install the pack

⬇️ in a Claude Code session

🔌As a plugin, the clean way

/plugin marketplace add Jakeschincariol/replica-skill
/plugin install replica-skill@replica-skill

⚡Or in one line, paste this into Claude Code

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

install skill

🏷️Command names

Installed as a plugin, each skill carries the pack's prefix: /replica-skill:replica-recon, and so on.

For short names like /replica-recon, copy the folders into your skills instead, with the two commands below.

💻In your terminal

git clone https://github.com/Jakeschincariol/replica-skill.git
cp -r replica-skill/replica-* ~/.claude/skills/

The 11 skills

🧩 a replica/ folder in your project

🔎

replica-recon

Maps the app: screens, flows, components, data model and a feature matrix.

🏗️

replica-architect

Picks the stack, writes the database schema and the API.

🎨

replica-design

Rebuilds the design system: colors, type, spacing, components.

🛠️

replica-build

Rebuilds the app screen by screen.

🔐

replica-backend

Accounts, database, payments, integrations.

🧪

replica-test

Clicks through every flow and logs bugs by severity.

📏

replica-diff

Compares your version to the original and gives a parity score.

💡

replica-entrepreneur

Reads real user reviews and turns them into a fix plan and a sales angle.

🏷️

replica-brand

Gives your version a name, a palette and a voice.

🚀

replica-launch

Writes the landing page, the pricing and the App Store listing.

🌐

replica-deploy

Puts it live on your domain.

The 6 tools included

Python scripts with no dependencies that never touch the network: screen comparison, parity score, review ranking, contrast check, a search for any trace of the original brand, and a store listing check.

The full run

🗺️ recon, then architect, then design...

➡️The order

Run them in this order: recon, architect, design, build, backend, test, diff, entrepreneur, brand, launch, deploy.

Each skill reads what the previous one wrote in your project's replica/ folder. Nothing to copy between steps.

You can also run a single one, on its own.

💬To start

/replica-recon [ADDRESS OF THE APP TO STUDY]

📅Example: a booking app

The mapping lists the screens, the flows (guest books, host sets availability, guest reschedules) and the data model.

The architecture adds a rule so two guests can never book the same slot, and has the booking flow built first.

The tests cover time zones, a slot taken mid-booking and the double click.

The comparison gives a score and the list of what's still missing.

Going live only happens with your go, once the tests pass and the original brand is gone from the code.

Start with the Entrepreneur

💡 before you write a line of code

🎯Why this one first

An exact copy has no reason to exist. What sells your version is what the original does badly.

It reads public reviews on the App Store, Google Play, G2, Capterra, Trustpilot, Reddit and Hacker News, aiming for 100 reviews across at least three sources.

Every quote is word for word, with its link. It makes up no review and no number, and it tells you when the sample is too thin.

You get the complaints ranked, what's missing, a fix plan and a sales angle.

💬The prompt

/replica-entrepreneur Analyze [APP NAME]. I'm thinking of building my own version for [YOUR AUDIENCE]. Tell me what its users hate, what they're missing, and the angle I could sell.

Even if you build nothing

Run it on the tool your team pays the most for, or on the competitor to your offer. You walk away with the exact words of its unhappy customers, ready for your positioning and your ads.

What the pack refuses to do

⚖️ read this before you sell

🛑The built-in rules

It rebuilds features and flows, never what the app owns: not its code, its logo, its copy or its content.

It only reads public pages and your own account. If your account's terms forbid building a competitor, it tells you and sticks to public sources.

It renames your version before going live. As long as any trace of the original brand is left in the code, it won't ship.

It doesn't promise a perfect copy. A booking app takes weeks, a full spreadsheet engine isn't realistic. The mapping sizes the job before you start.

Before you sell, run the trademark checks the brand skill lists, and talk to a lawyer if money is on the line.

Where to start