Jakeschincariol / replica-skill

# The Replica skill
Eleven Claude skills that clone any app. Free, MIT, no signup, no API key,
nothing to connect.
One reverse-engineers the app you want to clone. One rebuilds it. One tests it
for bugs. And one is the Entrepreneur: it reads what the app's users hate and
fixes it in yours, so you have an app you can sell.
In between, the others plan the stack and the database, rebuild the design
system, wire up auth and payments, score your clone against the original, give
it a name and a brand of its own, write the landing page and the store
listing, and put it live on your domain.
**It rebuilds what an app does, never what it owns.** Features and flows,
clean-room style. Not its code, its logo, its copy or its content. The
fine print is at the bottom, and the skills enforce it.
## Install
Paste this into Claude:
 [code] 
Or as a plugin, in Claude Code:
 [code] 
Claude Code namespaces plugin skills, so installed as a plugin they show up as
`/replica-skill:replica-recon` and so on. Copy the folders instead if you want
plain `/replica-recon`:
 [code] 
Project-local instead of global: copy the same folders into your repo's
`.claude/skills/`. No Claude Code at all? Paste any single `SKILL.md` at the
top of a chat and it runs as a mode. You lose the Python tools, but the
method works.
The tools need Python 3.8 or newer. Nothing to pip install.
## The eleven
| command | what it does |
| --- | --- |
| `/replica-recon` | Reverse-engineers any app: screens, flows, components, data model. From public pages, screenshots, store listings and your own account. |
| `/replica-architect` | Plans the stack, database schema and API for your clone. |
| `/replica-design` | Rebuilds the design system: colours, type, spacing, components. As tokens, with your own assets. |
| `/replica-build` | Rebuilds the app screen by screen from the recon map. |
| `/replica-backend` | Auth, database, payments and integrations. |
| `/replica-test` | Clicks through every flow and tests it for bugs. |
| `/replica-diff` | Compares your clone against the original. A parity score and what is missing. |
| `/replica-entrepreneur` | Reads what the app's users hate in real reviews and turns it into fixes and a positioning angle. |
| `/replica-brand` | Names and rebrands your version so it is yours. |
| `/replica-launch` | Landing page, pricing and App Store listing. |
| `/replica-deploy` | Ships it live on your own domain. |
## How to use it
Run them in order. Each one reads what the last one wrote, in a `replica/`
folder in your project.
 [code] 
An example: cloning a scheduling app, the kind where you share a link and
people book a time with you.
1. **`/replica-recon`** with the app's URL. It reads the help center, the
 pricing page, the store listing and public walkthroughs, and you click
 through your own account with it. Out comes `replica/recon.md`: 18
 screens, 7 flows (guest books a meeting, host sets availability, guest
 reschedules...), the components, an inferred data model (users,