Replica Skill: Rebuild the App You Pay For with Claude Code

Key takeaways

• Replica is a free, open-source (MIT) pack of 11 Claude skills by Jake Schincariol. They run in order: study an app, plan it, design it, build it, test it, compare it to the original, find what users complain about, rebrand it, and deploy it under your own name.
• It rebuilds features and flows. It does not copy source code, logos, brand names, text, or private APIs. It does not scrape behind logins or get past paywalls.
• No signup and no API key. The helper scripts need Python 3.8+ and use only the standard library. Claude Code needs a Pro plan or higher.
• Install with two commands in Claude Code: /plugin marketplace add Jakeschincariol/replica-skill, then /plugin install replica-skill@replica-skill.
• The repo is new and has a single commit. It runs Python scripts on your machine. Read the files before you install.
• It won't be a perfect copy. If you plan to sell what you build, run the trademark and domain checks and read the terms of use first. Below is the full checklist.

What this page is

This is the page behind the reel. Comment REBUILD and you land here: the repo link, the setup steps for Claude Code, what each of the 11 skills does and in what order, and the legal checklist to read before you launch anything.

Everything here comes from the Replica repository and its SKILL.md files, checked on October 12, 2026. The repo is young and can change. If something here disagrees with the README, trust the README.

What Replica is

Replica is a set of Claude skills. A skill is a folder of instructions (a SKILL.md file) that Claude loads when the task needs it. Replica's 11 skills each handle one stage of rebuilding an app, and each one reads what the previous one wrote into a replica/ folder in your project.

The idea in one line: you point it at an app, it maps what the app does, and you end up with your own app that does the same job under a new name, ideally with the problems users complain about fixed.

What it takes from the original is structure: screens, flows, the data model, spacing, and type sizes. What it never takes: code, logos, brand colors, icons, illustrations, copy, or licensed fonts. The design skill swaps licensed fonts for open ones like Inter, uses open icon sets like Lucide, and leaves the brand color as a placeholder until the brand skill gives you your own.

What you need

• Claude Code on Pro or a higher plan (pricing).
• Python 3.8 or newer for the helper scripts. No pip install.
• An account on the app you're studying (optional). Recon can work from public pages alone. If you use your account, you drive it yourself.
• A domain for the last step, when you deploy.

No Claude Code? You can paste a single skill's SKILL.md into a normal Claude chat and use it as a mode. The Python tools won't run that way, so you lose the automatic checks.

Before you install: read the files

Replica runs Python scripts on your computer. The repo is new and has a single commit. That doesn't make it unsafe, but it means there's no track record yet. Spend ten minutes looking before you install.

The README says the scripts use only the Python standard library and make no network calls. There are six of them:

The fastest way to check is to clone the repo into an empty folder and ask Claude Code to read it for you:

Read every file in this repository. For each Python script, tell me:
what it reads, what it writes, whether it makes any network calls,
whether it deletes files, and whether it runs shell commands.
Flag anything that doesn't match the README.

Then skim the SKILL.md files yourself. They're plain text, and they tell Claude exactly what to do.

Install in Claude Code

Option 1: plugin (two commands). In Claude Code, run:

/plugin marketplace add Jakeschincariol/replica-skill

/plugin install replica-skill@replica-skill

Plugin skills get a prefix, so the first one is /replica-skill:replica-recon. If the commands don't show up, run /reload-plugins or restart Claude Code.

Option 2: copy the folders (short names). If you'd rather type /replica-recon, clone the repo and copy the eleven replica-* folders into your skills folder:

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

cp -r replica-skill/replica-* ~/.claude/skills/

On Windows, copy the same folders into %USERPROFILE%\.claude\skills\ with File Explorer. To use them in one project only, copy them into that project's .claude/skills/ folder instead.

Option 3: ask Claude. Paste the repo link into Claude Code and write "install skill". Claude does the rest. Read what it runs before you approve it.

The 11 skills, in order

You can also run any skill on its own.

A few details worth knowing:

• Recon saves screenshots to replica/screens/ as reference only. They never go into your app. It won't log into anyone else's account, crawl pages in bulk, or read the app's JavaScript bundles to copy private endpoints.
• Diff says the clone is "not shippable" while must-have features are missing.
• Deploy checks nine things first: tests pass, no serious bugs open, must-have features done, the rebrand sweep is clean, the build passes, a privacy policy and terms are live, account deletion works, and the favicon, page titles, OG image, emails, and app icon are your own. The ninth is the store listing check, when you ship to an app store.

The skill worth running first: entrepreneur

Rebuilding an app as-is gives you a copy nobody needs. The entrepreneur skill is how you find a reason for your version to exist.

It works from public reviews: App Store and Google Play, G2, Capterra, and Trustpilot (including 1 to 3 star reviews), Reddit and Hacker News threads, the original's public feature-request board, and its changelog. It aims for 100+ reviews across at least three sources. A complaint that shows up fewer than three times, or from only one source, is marked thin and not presented as a trend.

What you get:

• Three ranked lists: what users hate, what's missing, and what's still unsolved.
• A fix plan of 5 to 8 items, each sized S, M, or L.
• Three positioning options, with one recommended.

Two rules it follows: every quote is word-for-word with a link, and no review is ever invented. Review quotes are research, not testimonials. Don't put them on your landing page.

The README also suggests running /replica-entrepreneur on an app you're only thinking about rebuilding. If the complaints are thin, you've saved yourself the build.

Your first run: pick a small app

Don't start with a big product. A full rebuild is a long Claude Code job, and it eats your usage. Pick an app where you only need one core flow, for example:

• a booking page
• a habit tracker
• a link-in-bio page
• a simple invoice generator

Recon asks which part of the app to study. Give it one flow, not the whole product. If it sizes the project as L or XL, pick something smaller for your first try.

A starting prompt:

/replica-recon Reverse engineer the [core flow] in [app name] for a [web / iOS / Android] product I'm building for [my own use / to sell].
Use the public help docs, pricing page, and app store screenshots.
I'll drive my own account for the live flow.
Keep it to this one flow.

When recon finishes, it tells you the next step. Run the skills in order and read each output in replica/ before moving on. Fixing a plan is cheap. Fixing a built screen isn't.

What it won't do

• Copy source code, logos, trademarks, text, or private APIs.
• Scrape pages behind a login or against a site's terms.
• Log into someone else's account or get past a paywall.
• Clone what an app owns: its content, its users, or its licenses. You can rebuild a music app's player. You can't clone its catalog.
• Guarantee a perfect copy. Results depend on how complex the app is.

If your own account's terms forbid building a competing product, recon sticks to public sources.

Legal checklist before you launch

Read this before you sell anything you build with Replica. It's a checklist, not legal advice. The README says the same.

1. Nothing copied. No code, logo, brand name, icons, illustrations, photos, or text from the original. Write every label and empty state yourself.
2. The rebrand sweep is clean. sweep.py finds no trace of the original's name, domain, or colors in your code. Then check by eye: favicon, page titles, email templates, OG image, and app icon.
3. The name is clearly different. Not similar in sound, look, or meaning. No puns on the original's name. Don't use the original's name in your ads or store listing either.
4. Trademark search. Run the screening checks the brand skill lists: USPTO (usually classes 9 and 42 for software), EUIPO or TMview, and the WIPO Global Brand Database. Add your own country's office if you sell there.
5. Domain, stores, and handles. Check that the domain is free, search the exact name on the App Store and Google Play, and check X, Instagram, TikTok, and GitHub.
6. Terms of use. Read the original app's terms, and the terms of every site you pulled reviews from.
7. Your own legal pages. A privacy policy and terms of use that list every service that handles user data. Account deletion that actually works.
8. A lawyer, if money is involved. The brand skill calls its checks "screening checks, not legal clearance." Before you spend money on a name, have a trademark lawyer run a proper search.

Before you launch, also run the vibe coding security checklist. An app Claude built fast can still ship with a key in the frontend.

FAQ

Is Replica free?

Yes. It's MIT-licensed, with no signup and no API key. You need Claude Code, which is on Pro and higher plans, and building a full app uses a lot of your plan's usage.

Will it make an exact copy of the app?

No. The README says no perfect clone is guaranteed. It rebuilds features and flows, and the diff skill tells you what's still missing.

Is it legal to sell what I build?

Rebuilding features is a different thing from copying code, brand, or content, and Replica is built to stay on the features side. Whether your product is fine depends on your name, your country, and the original's terms. Walk the checklist above, and talk to a lawyer before money is on the line.

Does it work for mobile apps?

Recon accepts web, iOS, Android, and desktop apps, and the launch skill checks App Store and Google Play listings. The README's worked example is a web app built with Next.js.

Can it get into the paid part of an app?

Only through your own account, driven by you. It won't get past a paywall, log into other accounts, or scrape behind a login.

Will I never pay for a subscription again?

That's not a promise anyone can make. For a simple tool you use alone, your own version can replace a subscription. But then you pay for hosting, and you're the one handling security, backups, and updates. For many apps, the subscription is the cheaper deal.

Try it

Pick one small app you pay for. Read the repo files, install the plugin, and run /replica-entrepreneur on it first. If the complaints give you a reason to build, run /replica-recon on one flow and follow the order from there. Walk the legal checklist before anyone else sees it.

If you'd like to look at the market before you build, these 3 competitor analysis sites show what similar apps actually earn. New to Claude Code? The Claude Code course covers the workflow from the start.