Skip to main content
← Skills
Skill · Code repo

Reverse-Engineer Apps and Build Your Own Version

Analyze an existing app, rebuild its features and flows, then use real user feedback to improve your version. Replica provides eleven Claude skills spanning research, implementation, testing, branding and deployment.

@Jakeschincariol Replica
  • App development

Works with Claude Code

Requirements

  • Python 3.8+

Overview

What you get

  • Eleven skills connected by project files under replica/: recon, architect, design, build, backend, test, diff, entrepreneur, brand, launch and deploy.
  • Six standard-library Python tools for feature and layout comparison, review analysis, contrast checks, checks for the reference app’s branding, and app-store listing checks.
  • A workflow that rebuilds functionality with original code and assets, then defines improvements from linked user feedback.

Tutorial

Turn a reference app into your own product

You want to build an app like an existing product, but do not yet know its screens, data relationships or which features to implement first. Replica divides that work among eleven skills, from studying behavior to implementation, testing and improvements based on user feedback.

Reverse engineering here means understanding behavior through public pages, documentation, screenshots and your own account. Cloning means implementing those features and flows with your own code, assets and copy, rather than downloading the original’s source and renaming it.

Choose between app rebuilding and interface redesign

  • unslop improves an existing interface through nine design passes, including layout, copy and color.
  • Hallmark designs websites around content and visitor goals, and can review or redesign existing pages.
  • Replica covers application functionality, from screens and data relationships to backend work, flow testing and launch preparation.

Start with one booking flow

This tutorial uses the repository’s scheduling example at a smaller scope: a guest chooses an available time, enters their details, submits a booking and sees confirmation. Leave team routing, payments and calendar sync out of the first version.

The skills pass work through files in your project’s replica/ directory:

StageSkillsPurpose
ResearchreconMap screens, flows, features and data relationships
Planningarchitect, designPlan the stack, database and design system
Implementationbuild, backendBuild interactions, persistence, auth and integrations
Verificationtest, diffTest flows and compare against the feature list
ImprovemententrepreneurTurn linked user reviews into problems and a fix plan
Launchbrand, launch, deployCreate your identity, launch material and deployment checks

Get one complete booking flow working before expanding the scope.

Install the plugin and map the features

This route uses Claude Code’s plugin installation. The six bundled tools require Python 3.8 or newer and use only its standard library. Your app’s development environment is chosen during architecture planning. Installing the skills needs no separate service key; payments, email and calendar integrations require your own accounts and configuration.

  1. Enter these plugin commands in Claude Code’s conversation, not in your terminal:
/plugin marketplace add Jakeschincariol/replica-skill
/plugin install replica-skill@replica-skill
  1. In the project where you will build, send this request with the reference URL filled in. The practice requests on this page were written by Opuskill.
/replica-skill:replica-recon
Reference app: [public URL]
Goal: a web scheduling tool for individual use.
Scope: guests choose an available time, enter name and email, submit a booking and see confirmation.
Exclude team routing, payments and calendar sync.
Read public pages and help docs first. Map screens, flows and data relationships.
Separate observed behavior from inference. Write replica/recon.md and replica/features.csv.
List missing information and wait for my review before implementing.
  1. Open both files. Check that they cover the entire booking path and record each feature’s priority and scope. The clone column in features.csv tracks your version: update it to yes, partial, no or skip, with a reason for skipped features.

Plugin commands have the /replica-skill: prefix. The README’s unprefixed examples apply to copying the skill folders directly; keep the installation and command forms consistent.

Build a working booking flow

Once you approve the feature map, continue in the same project:

  1. Run /replica-skill:replica-architect. Ask it to read the research, respect your existing stack and plan the booking flow, database tables and endpoints needed for one complete booking. Define how available slots will be entered and which time zone the first version uses.
  2. Run /replica-skill:replica-design. Ask for layout, type, spacing and form states using original copy and suitable assets.
  3. Run /replica-skill:replica-build. Start with the booking page and interactions, and request the startup command and preview URL. If it uses mock data, this stage checks the interface and flow.
  4. Run /replica-skill:replica-backend. Connect real availability queries, booking persistence and duplicate-booking handling, without payments or external calendar sync. Prepare a set of future available slots in the agreed time zone for testing. Ask for the chosen database’s local setup or account configuration steps, then complete them before running the app.
  5. Start the app using the command it provides. Book a slot in the browser, then try booking it again and compare the outcome with your agreed rules.

Next, request testing and feature comparison:

/replica-skill:replica-test
Read the booking flow. Test successful submission, missing required fields,
duplicate submission and a slot that has already been taken.
Record reproduction steps, fix the bugs and update feature status.
/replica-skill:replica-diff
Check the agreed scope in replica/features.csv and list unfinished must-haves.
Do not replace the item-by-item check with a total score.
Keep out-of-scope features marked skip with reasons.

The feature score measures completion of the list, not whether you have fully reproduced a product. Layout comparison checks structure and deliberately ignores color, which changes with your own branding.

Choose one improvement from user feedback

First make a small change to the working flow:

/replica-skill:replica-build
Change only the booking confirmation step to show the date, time and time zone clearly.
Keep the existing booking fields, submission endpoint and page layout.
Do not add payments or calendar sync.
Update the feature list and retest booking and duplicate submission.

Then run /replica-skill:replica-entrepreneur to research real feedback:

Research public user reviews of [reference app].
Keep each review’s source URL, original text and date, and state the sample size.
Find problems relevant to individual scheduling. Distinguish recurring complaints from single opinions.
If evidence is insufficient, list the gaps instead of inventing reviews.
Write a fix plan and let me choose one improvement before implementation.

Read replica/feedback.md and replica/fixes.md. Select a well-supported improvement within your scope, then take it through build, backend and test.

Adapt the workflow and prepare to launch

Replace the scheduling example with this starting brief:

/replica-skill:replica-recon
Reference app: [URL and public materials]
Audience: [who will use it]
First-version core flow: [start, main actions, finish]
Required features: [what must work]
Excluded features: [what is outside this version]
Existing stack and project: [what you already have]
Write the recon map and feature list first. Wait for scope approval before planning and building.

Once the core flow works, use brand for your own name, palette and copy, launch for the landing page and pricing, and deploy for launch checks. Each plugin command uses the same /replica-skill: prefix.

Deployment uses your hosting, database, domain and any chosen service accounts. Ask the assistant to list the changes and check results, then approve the launch. Walk through the core flow on the live site.