← Search

Replica Build , rebuild an app screen by screen, clean-room style
Development 🧪 Install ran in our test sandbox · Nov 11, 2026 📌 Pinned version: commit 77c9436
Install test only, on the date shown. This does not guarantee the code is safe.
⚙ Needs: a recon map from replica-recon (recon.md +…

Replica Build , rebuild an app screen by screen, clean-room style

The build step of the Replica pack: app shell first, then the core flow as a vertical slice, then every screen with all its states, every line written fresh from the recon map, ticking off the feature matrix

Version:

@

Quick answer

Replica Build is the construction step of the Replica pack, by Jakeschincariol: it rebuilds an app screen by screen from the recon map, clean-room style — every line written fresh. 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.

At a glance

What it isA building discipline for clones: a fixed order of work (shell, core slice, then screens), one commit per screen, a build log, and the feature matrix checked off as screens land.
Who it's forDevelopers who have a recon map of an app and want to rebuild it methodically instead of improvising screen by screen.
What you give itA recon map from Replica Recon (recon.md and features.csv), and a dev setup for the stack you want to build in.
What you getA working clone built in stages: the shell with routing and tokens, the core loop running end to end as a vertical slice, then each screen with its empty, loading, error and mobile states.
Works withMuse, installed from this page with the copy-paste install prompt. Strictly clean-room: never the original's code, assets, copy or CDN.
CostFree
TimeA few minutes to install. The build itself is the project: the shell and core slice come first and fast; the full screen-by-screen pass takes as long as the app's size demands.

Example — rebuilding a notes app from its recon map

An example of the build order the documentation prescribes, on a hypothetical recon map:

  • First the shell: routing, design tokens and empty screens in place, so the app exists as a navigable skeleton.
  • Then the core loop as a vertical slice — create a note, save it, see it in the list — end to end and working; plain-looking is fine at this stage, working is the point.
  • Then screen by screen, one commit each: the editor with its empty, loading and error states, the settings screen, the mobile layout — each one ticked off the feature matrix as it lands, with anything bigger than it looked said out loud in the build log.
⌁

Install

Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 77c9436

Prerequisites: a recon map from replica-recon (recon.md + features.csv); a dev setup for the stack you want to build in. Install "Replica Build , rebuild an app screen by screen, clean-room style" for me. It gives my agent @Jakeschincariol's build workflow, the build step of the Replica pack: app shell first, core flow as a vertical slice, then every screen with all its states, one commit per screen, updating the feature matrix and a build log. Strictly clean-room: every line written fresh. Repository: https://raw.githubusercontent.com/Jakeschincariol/replica-skill/77c9436fb3d18c3d58169efb8caf4fe906b0dc51/replica-build/SKILL.md Pinned version: install the code at commit 77c9436fb3d18c3d58169efb8caf4fe906b0dc51 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "replica-build". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. have a recon map ready, or run replica-recon first; choose the build stack). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.

🔒 Security, provenance and what this touches
🧭 What this touches
Based on the install prompt we scanned, this skill does not run commands, make third-party network calls, install packages, write files, or ask for API keys.
Install prompt analysis · 2026-10-13
🔒 Security and provenance
📌 Pinned version: commit 77c9436 · 2026-10-13
🧪 Install ran in our test sandbox · Nov 11, 2026
👁 Observed during the install test · Nov 11, 2026 : no network contact
🔎 Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a skill before installing →

✓

Verification certificate

Dated facts about what was checked for this listing, and how. This is not a safety certification.

Pinned version
77c9436 · 2026-10-13
Sandbox install test
Install ran in our test sandbox · Nov 11, 2026
Creator identity
Not verified
Fingerprint watch
Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Install prompt analysis
2026-10-13 : No commands, network calls, packages, file writes or API keys detected.

Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify

\u2318

The Replica series

?

Questions

How do I install a skill?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.

Where does my money go?

Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.

What does the ✓ next to a creator’s name mean?

It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.