replica-build
Skill399 starsChanged 40 days agoMITView on GitHub
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.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- realtahailyas/reverse-engineer-app-skillsword for word, first seen Oct 25, 2026
Other versions1 project uses a version of this.
Word for word · 1
- realtahailyas/reverse-engineer-app-skills★ 3100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
- replica-architectSkill
- replica-backendSkill
- replica-brandSkill
- replica-deploySkill
- replica-designSkill
- replica-diffSkill
- replica-entrepreneurSkill
- replica-launchSkill
- replica-reconSkill
- replica-testSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 20
Clean room: Every line of code is written here, from the recon map and the specs.
- Distinctive: line 24
Your words: Write every label, button, empty state and email fresh.
- Distinctive: line 26
Tokens only: No raw hex or pixel values in components.
- Distinctive: line 47
Read its row in the recon map: purpose, components, states, which flows pass through it.
- Distinctive: line 49
Look at the reference screenshot for layout and hierarchy.
≈ “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.
Files
replica-build
Reads replica/recon.md, replica/architecture.md, replica/design/.
Updates replica/features.csv (the clone column) and keeps
replica/build-log.md.
The rules
- Clean room. Every line of code is written here, from the recon map and the specs. Never paste the original's HTML, CSS, JavaScript, SVGs or images, never load anything from its domain or CDN, never "view source and adapt".
- Your words. Write every label, button, empty state and email fresh. Matching what a button does is parity. Matching its sentence is copying.
- Tokens only. No raw hex or pixel values in components. If a value is missing, add it to the tokens.
Step 1: the shell
Routing for every screen in the inventory (stub pages are fine), the layout (nav, header, sidebar), tokens wired in, the primitives from replica-design, and seed data so screens have something real to show. Commit.
Step 2: the vertical slice
The core loop from the recon map, end to end, before anything else. For a booking app: create an event type, open the public page, book a slot, see it on the dashboard. Ugly is fine. Working is the point. If replica-backend has not run yet, use the seed data and a fake data layer with the same function signatures, so swapping in the real one changes no screen code.
Step 3: screen by screen
Work in the order of architecture.md. For each screen:
- Read its row in the recon map: purpose, components, states, which flows pass through it.
- Look at the reference screenshot for layout and hierarchy. Not for pixels.
- Build it with the primitives. Real data from the data layer.
- Every state: empty, loading (skeletons, not spinners, if the original does), filled, error, no permission, long content (a 60 character name), mobile width.
- Basics, every time: semantic HTML, labels on inputs, keyboard reachable, visible focus, images with alt text.
- Set the matching rows in
features.csvtoyesorpartial(with a note). - Screenshot it at the same viewport as the reference into
replica/clone-screens/S07.pngfor replica-diff. - One commit per screen:
build: S07 booking page.
Definition of done, per screen
- every state from the recon map, plus empty, error and loading
- works at 390px and 1440px wide
- keyboard only: can complete the flow
- no console errors
- no hard-coded copy borrowed from the original
- features.csv updated
- screenshot saved for diff
Step 4: the build log
replica/build-log.md, one line per screen: ID, date, done or partial, what
is missing, what was harder than expected. When a feature is bigger than it
looked, say so in the log and in the chat. Do not quietly ship half of it.
When you are stuck on how something works
Go back to the original as a user: read its help article, watch its public walkthrough, use the user's own account. Do not dig into its code or network calls. Then build your own version of the behaviour.
Output
Screens built, the feature matrix updated, screenshots saved, and a summary:
screens done of total, must-haves done of total, what is next. Then
/replica-backend if the data layer is still fake, else /replica-test.
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
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.