Replica Architect, plan the stack, database and API for your app clone
Plans the stack, database schema and API for an app clone, from the recon map replica-recon wrote.
- What
- Plans the stack, database schema and API for an app clone, from the recon map replica-recon wrote.
- Cost
- Free
- Needs
- a recon map from replica-recon (recon.md + features.csv).
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: the planning step of the 11-skill Replica pack. Replica Architect reads your recon map and turns the inferred data model into a real plan: a boring, managed stack with one line of why per layer, a SQL schema with indexes and access rules, every API route listed by flow, and a build order that starts with a thin vertical slice. It refuses to plan from memory, so if there is no recon map it stops and points you to Replica Recon first. Only official, public APIs with your own keys are used, never the original app's private endpoints. By @Jakeschincariol, listed here with credit to its creator. Skill Harbor never reviews the code of a listed skill, so review it yourself before use.
Version:
Install
Copy the install package below, then paste it into Muse📌 Pinned version: commit 77c9436Prerequisites: a recon map from replica-recon (recon.md + features.csv). Install "Replica Architect, plan the stack, database and API for your app clone" for me. It gives my agent @Jakeschincariol's architecture workflow, the planning step of the Replica pack: pick a boring, managed stack with one line of why per layer, turn the inferred data model into real SQL with indexes and access rules, list every API route by flow, flag the parts that bite, and order the build as a thin vertical slice first. Only official, public APIs with my own keys, never the original app's private endpoints. Repository: https://raw.githubusercontent.com/Jakeschincariol/replica-skill/77c9436fb3d18c3d58169efb8caf4fe906b0dc51/replica-architect/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 architecture.md template) 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-architect". 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 ready, or run replica-recon first; pick a stack if I have a preference). 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.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
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.