8 October 2026

دليل · Guide9 min read

ابنِ نسختك من أي تطبيق مع سكلات Replica داخل Claude CodeRebuild Any App as Your Own with the Replica Skills in Claude Code

Install the 11 Replica skills, run them in order on an app you pay for every month, and ship a version with your own name and colours without copying its code.

Who this guide is for

Founders and creators paying for app subscriptions who want their own version

Key terms

Replica
Eleven free Claude skills under the MIT license. Each one does one job, from mapping an app to shipping your version on your own domain.
Skill
A file of instructions Claude reads and follows. You call it with a slash command such as /replica-recon.
Clean room
A way of building that studies what an app does and how people move through it, then writes everything fresh. No code, logo or copy is taken.
Slice
One part of the app you build first, usually the flow people pay for.

The steps

  1. Step 1

    Pick the app and the first slice

    Start with an app you pay for but only use one part of.

    Name that part before you run anything. In a scheduling app, the slice is booking a time from a link. Everything else comes later.

    PromptDefine the slice
    I pay a monthly subscription for [app name]. I only use it for [what you use it for]. Help me define the smallest slice I can build first that covers this, and write the flow step by step from the user's side.

    Tip: The smaller the first slice, the faster you get something that works.

  2. Step 2

    Open Claude Code in an empty folder

    Claude Code needs a paid Claude plan, and the bundled tools need Python 3.8 or newer.

    Create a new empty folder and open Claude Code in it. Everything the skills write lands in a replica folder inside your project.

    PromptIn the terminal
    mkdir my-app && cd my-app && claude
  3. Step 3

    Install the skills

    Paste the repo link into Claude Code and type install skill under it. Then restart.

    Prefer the plugin route? Use the commands below. Installed that way, the commands show up as /replica-skill:replica-recon instead of /replica-recon.

    PromptInstall
    https://github.com/Jakeschincariol/replica-skill
    
    install skill
    
    # or as a plugin:
    /plugin marketplace add Jakeschincariol/replica-skill
    /plugin install replica-skill@replica-skill
  4. Step 4

    Run Recon on the app

    Type /replica-recon with the app's link and answer its questions: which app, which part, who it is for.

    It reads the help center, pricing page, store listing and public walkthroughs, and you can click through your own account with it. Out comes recon.md with the screens, flows and data model, and features.csv with every feature.

    PromptRecon
    /replica-recon [app URL]
    
    I only want to build [the slice], for [audience]. Use public pages and my own account only.

    Tip: Read the size estimate in recon.md before you go on. It tells you honestly when an app is big.

  5. Step 5

    Plan, design and build

    Run these three in order. Each one reads what the last one wrote.

    /replica-architect picks the stack and writes the schema and API. /replica-design turns the look into tokens with your own colours and fonts. /replica-build rebuilds screen by screen and ticks off features.csv.

    PromptBuild
    /replica-architect
    /replica-design
    /replica-build
    
    Build [the slice] end to end before any other screen.
  6. Step 6

    Add the backend and test

    /replica-backend adds sign in, payments and integrations with your own keys.

    /replica-test clicks through every flow and logs bugs by severity. /replica-diff scores your version against the original and lists what is missing.

    PromptTest
    /replica-backend
    /replica-test
    /replica-diff
    
    Focus the tests on [the slice] and the hard cases: [example: two guests booking the same slot].
  7. Step 7

    Let the Entrepreneur read the complaints

    /replica-entrepreneur reads real reviews of the original, ranks what users hate and links every quote to its source. It never invents a review.

    You get a fix plan and a reason for people to switch. You can run it alone on an app you are only thinking about.

    PromptEntrepreneur
    /replica-entrepreneur
    
    Rank the complaints about [app] and suggest 3 fixes for [audience], with one positioning angle.
  8. Step 8

    Rebrand and ship

    /replica-brand gives your version a new name, palette and voice, then sweeps the code for the original's name, domain and colours.

    /replica-launch writes the landing page, pricing and store listing. /replica-deploy will not ship until the sweep is clean.

    PromptShip
    /replica-brand
    /replica-launch
    /replica-deploy

    Tip: If the deploy stops, the original's name or colours are still somewhere in your code.

  9. Step 9

    Before you sell

    Run the trademark checks /replica-brand lists and read the terms of anything you used.

    If real money is involved, talk to a lawyer before launch. The skills only read public pages and your own account, and if your account's terms forbid building a competitor, they say so and stick to public sources.

Ready prompts to copy

PromptQuick check before you build
/replica-entrepreneur

I am thinking of building my own version of [app]. Are the complaints about it strong enough to give people a real reason to switch? Give me the answer with the sample size.

The takeaway

Start with one slice, and rebuild what the app does, not what it owns.

Most value

Start building with me now

We sit together, break down your problem, and I build the AI solution with you step by step

60minutes
  • A private session with you
  • Real building during the session
  • Results you take with you when we finish
Book a build session

100% free

A free consultation about your problem

Start

The full path · Monthly subscription

Full access to every guide (29) for 249 AED/month