replica-build
Skill1 starsChanged 18 days agoMITView on GitHub
Rebuild an app clone screen by screen from the recon map: the shell first, then the core flow as a vertical slice, then every screen with all its states, ticking off the feature matrix, every line written fresh. Use for 'build the clone', 'build screen S07', 'start building', 'implement this page'; RU: собери клон, сверстай экран, начинай разработку, сделай этот экран.
2 other projects use a version of this, 2 of them edited.
Adopted by
Most recently taken up by
- realtahailyas/reverse-engineer-app-skillsedited, first seen Oct 25, 2026
- Jakeschincariol/replica-skilledited, first seen Oct 3, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 2
- Jakeschincariol/replica-skill★ 39926% same
- realtahailyas/reverse-engineer-app-skills★ 326% same
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-launchSkill
- replica-reconSkill
- replica-testSkill
- replica-usersSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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 13
Clean room: Every line is written here from the recon map and the specs.
- Distinctive: line 16
Your words: Every label, button, empty state and email written fresh.
- Distinctive: line 19
Tokens only: No raw hex or pixel values in components.
- Distinctive: line 49
When a feature is bigger than it looked, say so in the log and in the chat.
≈ “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 the clone column
of replica/features.csv and keeps replica/build-log.md.
The rules
- Clean room. Every line 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. Every label, button, empty state and email written fresh. Matching what a button does is parity; matching its sentence is copying. Russian interface text written by a native speaker's standard, not translated word for word.
- Tokens only. No raw hex or pixel values in components.
Step 1: the shell
Routing for every screen (stubs are fine), the layout, tokens wired in, the primitives, seed data with realistic fake records (no real people). Commit.
Step 2: the vertical slice
The core loop end to end before anything else. Ugly is fine, working is the point. If the backend is not there yet, a fake data layer with the same function signatures, so swapping it changes no screen code.
Step 3: screen by screen
For each screen in the order of architecture.md: read its recon row; look at the reference for
layout and hierarchy, not pixels; build it with the primitives; every state (empty, loading,
filled, error, no permission, a 60-character name, 390px wide); semantic HTML, labels, keyboard,
visible focus, alt text; update features.csv; screenshot at the reference viewport into
replica/clone-screens/S07.png; one commit per screen.
Definition of done, per screen
- every state from the recon map, plus empty, error, loading
- works at 390px and 1440px
- the flow completes with the keyboard only
- no console errors
- no copy borrowed from the original
- features.csv updated, screenshot saved
When a feature is bigger than it looked, say so in the log and in the chat. Never quietly ship half of it. Stuck on behaviour: use the original as a user (help article, walkthrough, the user's own account), never its code or network calls.
Next: /replica-backend if the data 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.