replica-architect
Jakeschincariol/replica-skill / replica-architect
plans a clone's stack, SQL schema and routes , which improves: avoids forgetting features
Details
- judge’s score
- 6/10
- place
- outside the packs
- publisher
- Jakeschincariol
- status
- new
- pinned commit
- 77c9436 on GitHub (new tab)
- skill’s last commit
- Oct 3, 2026
- repo stars
- 3,651
- main type
- Website
Judgement
Precise triggering and a useful default stack, but mostly general conventions Claude already knows. Depends on replica-recon, replica-design and replica-entrepreneur, which are missing. Narrow cloning scope.
reservations
- Depends on replica-recon, replica-design and replica-entrepreneur, not provided: the skill cannot run on its own.
- Several steps remain vague instructions (“write a line on each”) with no verifiable example.
- The architecture.md annex is an empty template; the advice on the exclusion constraint (double booking) is mentioned but not written in SQL.
- The “clone an app” framing is a niche use, hard to transfer to a typical project.
- Triggering
- 2/2
- Added value
- 1/2
- Precision
- 1/2
- Scope
- 1/2
- Quality
- 1/2
Alerts
no alerts
Neither the static scan nor the judge flagged a risk for this skill.
Original description
Plans the stack, database schema and API for an app clone, from the recon map replica-recon wrote. Picks boring, managed tech, turns the inferred data model into real SQL with indexes and access rules, lists every route by flow, and orders the build as a thin vertical slice first. Use when the user …
added on Oct 18, 2026 · license MIT