replica-architect is the second step of the Replica skill set. It reads the recon map and feature matrix written by replica-recon and produces an architecture document, a SQL schema and an ordered build plan.
It defaults to managed, documented tech (Next.js, Postgres, Stripe, Resend, Vercel) and writes one line of reasoning for each choice. If there is no recon map it stops and asks you to run recon first.
What You Get
- A
replica/architecture.mdwith the stack, one line of why per layer, and the riskiest parts - A SQL schema with ids, timestamps, owner columns, foreign key rules, indexes and access rules
- An API table of method, path, purpose, caller, input, output and flow, plus webhooks and background jobs
- A build order: vertical slice, must-haves, should-haves, then the fixes found by the entrepreneur skill
Common Use Cases
- Choosing a stack and database for a clone of an existing SaaS app
- Writing a first schema with constraints that stop two guests booking the same slot
- Listing the hard parts such as time zones, webhook retries and multi-tenancy before building
What Makes It Unique
It is driven by a recon map, so the schema and routes trace back to the flows and screens of the app being rebuilt. It sets hard rules in the database, such as exclusion constraints, and it allows only official public APIs with your own keys, never the original app’s private endpoints.
Under The Hood
The skill is instructions only and ships a template file for the output. It reads the recon files in your project and writes the architecture document and a schema file there. It does not run commands, fetch web pages or call APIs.