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
- What
- 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
- Cost
- Free
- Needs
- a recon map from replica-recon (recon.md + features.csv); a dev setup for the stack you want to build in.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: the build step of the 11-skill Replica pack: rebuild an app screen by screen from the recon map. App shell with routing and tokens first, then the core loop as an end-to-end vertical slice (ugly is fine, working is the point), then every screen with every state (empty, loading, error, mobile), one commit per screen, ticking off the feature matrix as it goes. by @Jakeschincariol, listed here with credit to its creator. Honest caveats: strictly clean-room, every line written fresh, never the original's code, assets, copy or CDN; works from the recon map, architecture and design specs, so it pairs with the other Replica skills (recon first). Keeps a build log and says out loud when a feature is bigger than it looked. Skill Harbor never reviews the code, review it yourself before use. Discovered via GitHub.
Version:
Install
Copy the install package below, then paste it into MuseCommunity-built. Skill Harbor doesn't audit code — review the source before installing.
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://github.com/Jakeschincariol/replica-skill/blob/main/replica-build/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 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.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build 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 build before installing it.