Jakeschincariol/replica-skill

Run them in order. Each one reads what the last one wrote, in a replica/ folder in your project.

recon -> architect -> design -> build -> backend -> test -> diff -> entrepreneur -> brand -> launch -> deploy

An example: cloning a scheduling app, the kind where you share a link and people book a time with you.

1. /replica-recon with the app's URL. It reads the help center, the pricing page, the store listing and public walkthroughs, and you click through your own account with it. Out comes replica/recon.md: 18 screens, 7 flows (guest books a meeting, host sets availability, guest reschedules...), the components, an inferred data model (users, event types, availability, bookings) and features.csv. The partner marketplace is marked out of scope: that is their network, not a feature.
2. /replica-architect picks Next.js, Postgres, Stripe and Resend, writes the schema (with a constraint so two guests can never book the same slot) and orders the build: the booking flow end to end first.
3. /replica-design measures the screenshots into tokens: colour roles, type scale, 8px spacing, the date picker and slot button specs. Open icons, an open font, your own words.
4. /replica-build builds the shell, then the booking flow, then every screen with all its states, ticking off features.csv as it goes.
5. /replica-backend adds sign up, Google Calendar through Google's own API with your keys, Stripe for paid bookings, reminder emails.
6. /replica-test writes a test plan from the 7 flows, Playwright specs for the happy paths and edge cases (time zones, a slot taken mid-booking, double submit), and logs bugs by severity until no S1 or S2 is open.
7. /replica-diff scores it. Features 86, all must-haves done, booking page layout 91. Missing: round-robin for teams, the website embed.
8. /replica-entrepreneur reads 140 real reviews across the App Store, G2, Capterra and Reddit. Top complaints: per-seat price jumps, no text reminders, guests confused by time zones. Each with counts and linked quotes. Fix plan: flat pricing, SMS reminders, a time zone confirm step. Angle: booking links for small teams that hate per-seat pricing.
9. /replica-brand names it (with the trademark and domain checks to run), gives it a new palette, a logo brief and a voice, then sweeps the codebase until nothing of the original is left.
10. /replica-launch writes the landing page around the angle, sets pricing against the original's public page, and lints the store listing.
11. /replica-deploy runs the preflight (tests, parity, sweep, listing), sets up production, gives you the DNS records for your domain, and ships it when you say go.

You can also run any one on its own. /replica-entrepreneur on an app you are only thinking about cloning is a good way to find out if you should.