replica-deploy is the last step of the Replica set. It runs a preflight, fills in a deploy checklist, and walks through production database, environment variables, Stripe live mode, OAuth redirects, host, domain records and monitoring.
Nothing goes live without your go. You buy the domain and sign in to accounts; the agent writes the exact DNS records, variable names and commands.
What You Get
- A preflight run of the Playwright suite, the parity score, the rebrand sweep, the listing check and a production build
- Production setup notes: separate database, backups, env vars, Stripe live mode, OAuth redirect URIs, verified email domain
- Exact DNS records for the apex, www, host verification, SPF, DKIM and DMARC
- Monitoring: error tracking, uptime checks, analytics and an alert
- A filled
replica/deploy.mdwith every check, the live URL and what to watch in week one
Common Use Cases
- Taking a finished clone to a custom domain on Vercel or a similar host
- Blocking a launch while leftover names of the original app remain in the code
- Submitting a mobile build to TestFlight and Play internal testing
What Makes It Unique
It is a gate with fixed rules: it needs the user’s explicit go, never buys a domain, enters a card or pastes a live key, and refuses to ship until the sweep from the brand skill exits clean. It also tests one real Stripe purchase and refund.
Under The Hood
The skill’s instructions run shell commands in your project: the Playwright test run, three of the bundled Python scripts from sibling skills, and the production build. For a mobile app they name EAS build and submit, Xcode and Gradle. The agent writes the deploy checklist file and gives you DNS records and commands to apply yourself. The steps involve third-party services such as the host, Stripe, OAuth providers and email providers, which you sign in to.