← Search

Replica Design, rebuild the design system for your app clone
Development 📌 Pinned version: commit 77c9436
⚙ Needs: a recon map and screenshots from replica-recon…

Replica Design, rebuild the design system for your app clone

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.

⚠️ Unverified listing: our automated install test could not be completed for this build (its install prompt tripped a safety filter in our test system), so we have not verified its content.
At a glance
What
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.
Cost
Free
Needs
a recon map and screenshots from replica-recon; Python 3 for the contrast checker.
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

@
⌁

Install

Copy the install package below, then paste it into Muse📌 Pinned version: commit 77c9436

Prerequisites: a recon map and screenshots from replica-recon; Python 3 for the contrast checker. Install "Replica Design, rebuild the design system for your app clone" for me. It gives my agent @Jakeschincariol's design workflow, the design-system step of the Replica pack: measure colour roles, type scale, spacing, radius, shadows and layout from screenshots, write design tokens and component specs, build the primitives once in isolation, and run the WCAG contrast check until it has zero AA failures. Rebuild the system, never the original's logos, icons, illustrations, photos, licensed fonts, copy or signature brand colour. Repository: https://raw.githubusercontent.com/Jakeschincariol/replica-skill/77c9436fb3d18c3d58169efb8caf4fe906b0dc51/replica-design/SKILL.md Pinned version: install the code at commit 77c9436fb3d18c3d58169efb8caf4fe906b0dc51 exactly. 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, including the tokens.json template and contrast.py) 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: you create your own accounts and keys and put keys in .env.local, the agent writes .env.example with names only and never types a password, card or live key. 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-design". 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 the recon map and screenshots ready; run the contrast check on my tokens). 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. In Muse, invoke pack neighbour skills by name, not as /slash commands. If anything looks off, stop and ask me. After installation, ask me if I want to leave private feedback Private for now: only the Skill Harbor team sees it. Sellers may be looped in later.

🧪 Example
You ask
Illustrative example only, not a real user's result. Rebuild the design system of the app in my recon screenshots.
You get
Illustrative example only, not a real user's result. replica/design/tokens.json, tokens.css and replica/design/components.md, primitives built in isolation, and a contrast report with zero AA failures. Next step: replica-build (invoked by name in Muse).
Illustrative example based on this skill’s own documentation — not a real user’s result.
🔒 Security, provenance and what this touches
🔒 Security and provenance
📌 Pinned version: commit 77c9436
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 build before installing →

?

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.