Skip to main content
skill CX Codex

replica-diff — Claude Code skill: what it does, how to install

Measures an app clone against the original by calculating feature parity scores from a matrix and diffing UI layouts without penalizing rebrands.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add Jakeschincariol/replica-skill --skill replica-diff -a claude-code
Open on GitHub

What replica-diff does

The skill evaluates app clones against original targets using two scripts written in standard-library Python. parity.py reads replica/features.csv to calculate an implementation score. It weights must-have features at 3, should-haves at 2, and could-haves at 1, counting partial work as half. Rows marked as skipped are ignored, and the script outputs the missing list in build order.

imgdiff.py handles visual layout comparison using screenshots at matching viewport sizes (1440x900 for desktop, 390x844 for mobile). It converts screens into edge maps and evaluates content inside a grid. Because it ignores colours intentionally, restyled themes do not hurt the score. Pixel-by-pixel diffing remains available under --mode pixel strictly for checking regressions against earlier clone builds.

The final verdict is written to replica/parity.md. A missing must-have or an active S1 defect marks the build as not shippable, halting deployment until core gaps are closed. You only need standard Python and your captured screenshots to run both tools.

What it helps with

  • calculate feature parity scores using weighted project matrices
  • inspect layout structural differences across screenshots without colour bias
  • generate an ordered backlog of missing features for implementation
  • verify shippable release status against must-have criteria

Example prompts for the agent

  • How close is my clone to the original based on replica/features.csv?
  • Compare the layout screenshots in replica/screens and clone-screens
  • Run a parity check and generate the replica/parity.md report

How to install replica-diff

1Skills CLI (Vercel)

npx skills add Jakeschincariol/replica-skill --skill replica-diff -a claude-code

2Manually: put the files in place

~/.claude/skills/replica-diff/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/replica-diff/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about replica-diff

How to install replica-diff in Claude Code?

Run npx skills add Jakeschincariol/replica-skill --skill replica-diff -a claude-code.

What does replica-diff do?

It calculates feature parity scores from a CSV matrix, diffs UI layouts from screenshots, and writes a shippability report into replica/parity.md.

Does replica-diff require external Python dependencies?

No, both parity.py and imgdiff.py rely entirely on Python standard library modules with no additional package installations needed.

Source text

SKILL.md · MIT
---
name: replica-diff
description: >-
  Compares an app clone against the original: a feature parity score from the
  feature matrix (weighted by must, should, could) with the missing list in
  build order, plus a screenshot layout diff that ignores colour so a rebrand
  does not count against you. Two standard-library Python tools. Use when the
  user says "how close is my clone", "compare it to the original", "what's
  missing", "parity check", "diff the screens", "is it ready", or after
  /replica-test.
---

# replica-diff

Two tools in this folder, both standard-library Python, no installs:

```bash
python3 parity.py replica/features.csv                         # feature parity + missing list
python3 imgdiff.py replica/screens/S07.png replica/clone-screens/S07.png --out diff-S07.png
python3 imgdiff.py a.png b.png --json > replica/diffs/S07.json # for parity.py --visual
python3 parity.py replica/features.csv --visual replica/diffs/*.json --markdown > replica/parity.md
```

## What parity means here

**Parity means it does the same job, not that it looks the same.** The
feature score is the number that matters: can a user do everything they could
do in the original. The layout score checks structure (is the information in
the same places, in the same hierarchy), because that is what makes a switcher
feel at home. It deliberately ignores colour, because replica-brand changes
every colour on purpose. Do not chase pixel parity with the original. Its
exact look is its trade dress, and it changes before launch.

## Step 1: feature parity

Make sure `replica/features.csv` is current: every row's `clone` column is
`yes`, `partial` (with a note), `no`, or `skip` (with a reason). Then:

```bash
python3 parity.py replica/features.csv
```

It weights must 3, should 2, could 1, counts partial as half, leaves out
`skip` rows and rows you added that the original does not have, and prints:
the score, must-haves done of total, each area weakest first, and the missing
list in build order. Must-haves not done means not shippable, and it says so.

## Step 2: layout diff

For each key screen, take two screenshots at the **same viewport** (1440x900
desktop, 390x844 mobile) in the **same state** (same data shape, same tab
open, logged in the same way). The original's come from public pages or the
user's own account, saved in `replica/screens/`. The clone's go in
`replica/clone-screens/`.

```bash
python3 imgdiff.py replica/screens/S07.png replica/clone-screens/S07.png --out replica/diffs/S07.png
```

Layout mode (default) turns both into edge maps, cuts them into a grid, and
compares where things are, scoring only cells with something in them. It
reports the score (matches 90+, close 75+, partly 50+, different), the
regions that differ (in the original's pixel coordinates, biggest first), and
a height difference if the clone's page is much longer or shorter. Retina and
non-retina screenshots compare fine: both are scaled to the same width.

`--mode pixel` is exact comparison. Use it for your own regressions (clone
today against clone last week), not against the original.

## Step 3: behaviour diff

Walk each flow in both apps and compare what the scores cannot see: clicks to
finish the core flow, what happens on errors, what is remembered between
visits, what emails arrive. Fewer clicks than the original is a win. Write
each difference as: flow, original does, clone does, fix or keep.

## Step 4: the report

`replica/parity.md`: overall score, feature score, layout score per screen,
missing features in build order, behaviour differences, and a verdict:

- **not shippable**: any must-have missing, or any open S1 bug
- **shippable**: all must-haves done, feature score 80+, no open S1 or S2
- **better than the original**: shippable, plus fixes from
  replica-entrepreneur. This is the goal. A straight copy has no reason to exist.

Give honest numbers. A clone at 62% is at 62%.

## Output

`replica/parity.md`, the diff images, and the top five things to build next.
Then `/replica-build` for the gaps, or `/replica-entrepreneur` if parity is
there.

© Jakeschincariol · MIT · Jakeschincariol/replica-skill

Similar skills

Everything for Testing and QA →

From the same set10

replica-entrepreneur Reads public reviews of the app you are cloning and turns user complaints into a fix plan and a positioning angle you can sell. CX Codex +1 634installs replica-test Tests every flow in an app clone, builds a test plan, runs end-to-end checks, and records reproducible bugs with evidence. CX Codex +1 633installs replica-design Rebuild an app clone’s design system from screenshots as tokens, styles and component specs. Use it when you need to match interface structure and component behaviour. CX Codex +1 630installs replica-build Rebuilds an app screen by screen from the recon map: shell first, then the core flow, then every screen with all its states. Useful when you need to reproduce a product in your own code. CX Codex +1 622installs replica-launch Creates launch materials for an app clone: a landing page, pricing, store copy and a launch plan. Use it after you have positioning and brand research. CX Codex +1 619installs replica-architect Plans the stack, database schema and API routes for an app clone, working from the recon map replica-recon produced. Useful once recon is done and you need a build plan. CX Codex +1 618installs replica-brand Names app clones, sets up contrast-checked palettes, writes logo briefs, and sweeps original brand remnants from code. CX Codex +1 617installs replica-deploy Prepares an app clone for release on your own domain with preflight checks, production setup and DNS guidance. Use it before going live. CX Codex +1 616installs

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor