agentleFS
dmminga1983dmminga1983/minga-replica/skills/replica-diff/SKILL.md

replica-diff

Skill1 starsChanged 18 days agoMITView on GitHub

Compare an app clone with the original: a feature parity score from the matrix (must, should, could weighted, partial counted as half, your own additions excluded) and a screenshot layout diff that ignores colour, so the rebrand does not count against you. Use for 'how close is my clone', 'compare with the original', 'what's missing', 'parity check', 'is it ready'; RU: насколько похоже, сравни с оригиналом, чего не хватает, готов ли клон.

2 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Every clone cell is yes, partial (with a note), no, or skip (with a reason).

    line 23
  2. Distinctive:

    Not shippable (a must-have missing or an open S1), shippable (all musts, 80+, no open S1 or S2), or better than the original (shippable …

    line 41

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

replica-diff

python3 parity.py replica/features.csv
python3 imgdiff.py replica/screens/S07.png replica/clone-screens/S07.png --out replica/diffs/S07.png
python3 imgdiff.py replica/screens/S07.png replica/clone-screens/S07.png --json > replica/diffs/S07.json
python3 parity.py replica/features.csv --visual "replica/diffs/*.json" --markdown > replica/parity.md

What parity means

It does the same job, not that it looks the same. The feature score is the number that matters. The layout score checks structure, because that is what makes a switcher feel at home, and it ignores colour on purpose. Never chase pixel parity: the exact look is the original's trade dress.

Feature parity

Every clone cell is yes, partial (with a note), no, or skip (with a reason). Weights must 3, should 2, could 1, partial half. Skip rows and rows the original does not have are left out. Any must-have missing means not shippable.

Layout diff

Two screenshots at the same viewport (1440x900, 390x844), in the same state, with the same shape of data. Large retina screenshots take a while: the decoder is pure Python. --mode pixel is for the clone against itself last week.

Behaviour diff

Walk each flow in both: clicks to finish, error handling, what is remembered, which emails arrive. Fewer clicks than the original is a win. Each difference: flow, original does, clone does, fix or keep.

Verdict

Not shippable (a must-have missing or an open S1), shippable (all musts, 80+, no open S1 or S2), or better than the original (shippable plus fixes from /replica-users: the goal, because a straight copy has no reason to exist). Honest numbers: 62% is 62%.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.