replica-recon
Reverse-engineers any app into a recon map: screen inventory, user flows, component list, inferred data model and a feature matrix, from public pages, screenshots, app store listings, help docs and the user's own account. The first step of the Replica pack. Use when the user says "clone this app", "reverse engineer X", "how does X work", "map out X", "what screens does X have", "I want to build my own version of X", "copy this app", or pastes an app's URL or App Store link and wants to rebuild it.
- Installs
- 703
- Last 24h
- +48
- Trending rank
- #3486
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/jakeschincariol/replica-skill --skill replica-recon- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads replica-recon automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
replica-recon
Everything else in the pack builds from what this skill writes. A bad recon map means a bad clone, so take the time here.
Output goes in the user's project:
replica/recon.md the recon map (template: recon-map.md in this folder)
replica/features.csv the feature matrix (template: features.csv in this folder)
replica/screens/ reference screenshots of the original. Never shipped.
The rules, before anything else
This skill rebuilds functionality and UX patterns, clean-room style. It studies what the app does and how a user moves through it. It does not take anything the app owns.
- Public sources and the user's own account only. Never log into an account that is not the user's, never ask for a password, never get past a paywall or a login by any trick.
- Reading, not scraping. No crawlers, no bulk downloads, no loops. If a browser tool is connected to the user's own browser, read pages at human speed with the user present.
- No source code, no private APIs. Do not read or save the app's JavaScript bundles, decompile its binary, or log its network calls to copy endpoints. Public API docs are fine to read.
- Check the terms. Some products' terms forbid using an account to build a competing product. If the user's account is under terms like that, say so and work from public sources only.
- Screenshots are reference. They live in
replica/screens/, are used to compare layouts, and never go into the clone.
Step 1: scope
Ask three things, or propose answers and get a yes:
- Which app, which platform. Web, iOS, Android, desktop.
- Which slice. "All of Notion" is not a project. "Notion's pages, blocks and sharing" is. Default to the core loop: the one flow users pay for.
- Who it is for. The user's own business, a niche, a product to sell.
Step 2: list the sources
Build a sources table first, with a URL on every row. In order of value:
| source | what it gives you |
|---|---|
| help center / docs | the most complete feature list there is, and the settings |
| pricing page | which features matter (they gate them) |
| changelog | what was added recently, what the team thinks is important |
| app store listing | screenshots of every key screen, the pitch, ratings |
| public walkthrough videos | real flows, click by click |
| marketing site | positioning, the core loop in their words |
| the user's own account | the real thing, every state, driven by the user |
| public API docs | the data model, almost for free |
Step 3: screen inventory
One row per screen. IDs are stable: S01, S02... Every other file refers to them.
ID | screen | route or how you get there | purpose | key components | states seen
States matter: empty, loading, filled, error, permission denied, mobile. An empty state you did not record is an empty state you will not build.
Step 4: user flows
F01, F02... Each one is a goal and the screens it passes through:
F01 Guest books a meeting
S07 booking page -> S08 pick a time -> S09 details form -> S10 confirmed
edge: no slots this week, time zone differs, slot taken while filling the form
Count the clicks on the happy path. It becomes the number to beat.
Step 5: components
Every repeated UI part: buttons, inputs, date pickers, modals, tables, toasts, nav. Name, variants, states, which screens use it. This becomes replica-design's component list.
Step 6: inferred data model
Entities, fields and relationships, each with its evidence and a confidence:
Booking id, event_type_id, start_at, end_at, guest_name, guest_email,
status (confirmed | cancelled | rescheduled), answers (json)
evidence: S09 form fields, S10 confirmation, help article "Cancel a booking"
confidence: high
Mark guesses as guesses. replica-architect turns this into a real schema.
Step 7: feature matrix
Write replica/features.csv (columns: feature, area, priority, original,
clone, notes). Priority is must / should / could. clone starts at no for
every row and gets filled in during the build. replica-diff scores it.
Step 8: what cannot be cloned
List it honestly, as skip rows with a reason: licensed content (a music
catalogue, a stock library), the network and its users, data the app owns,
partner deals, hardware, regulated licences (banking, health). "Clone any
app" means the features and the flow, not what the app owns.
Step 9: size it
Screens, flows, entities, and the hard parts (realtime, sync, payments, calendar or email integrations, offline). Give a size: S (a weekend), M (a few weeks), L (a quarter), XL (rescope it). No promises of a perfect clone.
Output
replica/recon.md and replica/features.csv, then a five-line summary: the
core loop, screen and flow counts, the three hardest parts, what is out of
scope, and the next step: /replica-architect.
FAQ
What does the replica-recon skill do?
Reverse-engineers any app into a recon map: screen inventory, user flows, component list, inferred data model and a feature matrix, from public pages, screenshots, app store listings, help docs and the user's own account. The first step of the Replica pack. Use when the user says "clone this app", "reverse engineer X", "how does X work", "map out X", "what screens does X have", "I want to build my own version of X", "copy this app", or pastes an app's URL or App Store link and wants to rebuild it.
How do I install replica-recon?
Run npx skills add https://github.com/jakeschincariol/replica-skill --skill replica-recon in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/replica-recon/ (personal) or .claude/skills/replica-recon/ (project).
Which AI agents can use replica-recon?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is replica-recon safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains replica-recon?
It is published by jakeschincariol in jakeschincariol/replica-skill. It has 703 recorded installs.
More from jakeschincariol/replica-skill
replica-entrepreneur
jakeschincariol/replica-skill
Researches the app being cloned and reads what its real users say in public reviews (App Store, Google Play, G2, Capterra, Trustpilot, Reddit, Hacker News, its own feature-request board), then ranks what they hate, what is missing and what is unsolved, turns it into a fix plan for the clone and a positioning angle you can sell. Every quote is real, verbatim and linked. Use when the user says "what do people hate about X", "read the reviews", "how do I make mine better", "find the gap", "what features are missing", "how do I position this", "make it sellable", or after /replica-diff.
replica-test
jakeschincariol/replica-skill
Clicks through every flow of an app clone and tests it for bugs: a test plan generated from the recon flows with happy paths and edge cases, Playwright end-to-end tests where possible, a browser click-through where not, and bug reports in a fixed format with severity, steps and evidence. Use when the user says "test my clone", "find bugs", "QA this", "click through everything", "write e2e tests", "does it work", or after /replica-build or /replica-backend.
replica-design
jakeschincariol/replica-skill
Rebuilds an app's design system for a clone: colour roles, type scale, spacing, radius, shadows and every component with its states, as design tokens plus component specs, with original assets instead of the target's logos, icons, illustrations or licensed fonts. Includes a WCAG contrast checker. Use when the user says "match the design", "rebuild the design system", "get the colours and fonts", "make it look like X", "design tokens for my clone", or after /replica-architect.
replica-diff
jakeschincariol/replica-skill
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-build
jakeschincariol/replica-skill
Rebuilds an app screen by screen from the recon map: app shell first, then the core flow as a vertical slice, then every screen with all its states, ticking off the feature matrix as it goes. Writes every line fresh, never the original's code, assets or copy. Use when the user says "build the clone", "build screen S07", "start building", "rebuild this screen", "implement the booking page", or after /replica-design.
replica-launch
jakeschincariol/replica-skill
Writes the launch for an app clone: the landing page built on the positioning angle, pricing set against the original's public pricing and its users' complaints, and the App Store and Google Play listing linted against the stores' limits and copycat rules. Use when the user says "landing page", "pricing", "how much should I charge", "App Store listing", "store screenshots", "launch plan", "Product Hunt", or after /replica-brand.
Popular mobile skills
design-mobile-apps
designed-by-ai/skills
Design mobile app screens with Sleek, edit Sleek projects, and implement their designs in React Native or HTML.
ios-design
uizze.sh
Design and review iOS UI/UX for iPhone apps in SwiftUI, UIKit, or React Native. Use for mobile app design, screen redesigns, navigation flows, typography, forms, keyboard and safe-area layout, and accessibility checks. Apply Apple Human Interface Guidelines and consult real product references through the optional Uizze connection.
vercel-react-native-skills
vercel-labs/agent-skills
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
animate-expo
emilkowalski/skills
Build animations in React Native and Expo, making the decisions in the order that determines whether they feel right — should it animate, which thread it runs on, which properties, spring or timing, how the gesture hands off, how it degrades. Writes the implementation with Reanimated, Gesture Handler, Expo Router and expo-haptics. Use when animating anything in an Expo app, adding gestures, sheets, screen transitions, press feedback or haptics, or fixing motion that stutters on device. For web animation use animate.
xcode-project-setup
firebase/agent-skills
Safely modifies Xcode projects (.pbxproj) to add Swift Packages and link files. Use this skill whenever an iOS project needs dependencies installed (e.g. Firebase, Alamofire).
firebase-remote-config-basics
firebase/agent-skills
Manages Firebase Remote Config templates, feature flags, loading strategies, and SDKs (Android, iOS). Use when downloading/deploying remoteconfig JSON templates, managing version history/feature flags, setting in-app defaults, fetchAndActivate(), real-time listeners, or SDK setup. Don't use for Firebase Hosting, Auth, Firestore, Data Connect, Crashlytics, or App Hosting.