replica-deploy
/replica-deploy
Publikuje klon aplikacji na własnej domenie po bramce kontrolnej: testy, zmienne środowiskowe, hosting, DNS, monitoring i wersje mobilne.
- Autor
- letmefind ↗
- Repozytorium
- replica-skill-cursor-grok ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 30.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 30.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Publikuje klon aplikacji na własnej domenie po bramce kontrolnej: testy, zmienne środowiskowe, hosting, DNS, monitoring i wersje mobilne.
Wyzwalacze z opisu
Oryginalny opis (EN)
Ships an app clone live on the user''s own domain: a preflight gate (tests green, parity must-haves done, rebrand sweep clean, listing linted, legal pages up), production database and env vars, the host, DNS records for the domain and for email, Stripe live mode, OAuth redirects, monitoring, and mobile builds to TestFlight and Play. Use when the user says "deploy it", "ship it", "put it live", "connect my domain", "go to production", "publish the app", or after the replica-launch skill.
Jak działa
- On this computer
- The rules
- Step 1: preflight
- Step 2: production services
- Step 3: host and domain
- Step 4: watch it
- Step 5: mobile, if there is an app
- Output
Podgląd SKILL.md
---
name: replica-deploy
description: 'Ships an app clone live on the user''s own domain: a preflight gate (tests green, parity must-haves done, rebrand sweep clean, listing linted, legal pages up), production database and env vars, the host, DNS records for the domain and for email, Stripe live mode, OAuth redirects, monitoring, and mobile builds to TestFlight and Play. Use when the user says "deploy it", "ship it", "put it live", "connect my domain", "go to production", "publish the app", or after the replica-launch skill.'
---
# replica-deploy
## On this computer
Nothing goes live without the user's explicit go. You never buy a domain,
never enter a card, never type a password, and never paste a live key. You
write the DNS records, the env var names, and the commands. The user does the
account steps. Do not send email or other messages. Show the user the records
and stop until they say go.
`parity.py`, `sweep.py`, and `listing.py` run on this computer against a
read-only checkout. Do not commit from here. `npx playwright test` and
`npm run build`, and any code change a failed check needs, go to a Cursor
cloud coding agent as a self-contained task. Do not edit the repository
yourself. Do not point any check at the original app.
Write `replica/deploy.md` under `/workspace/<project-slug>/replica/` and
include that file in the repository task so the filled checklist is committed.
Reads everything in `replica/`. Writes `replica/deploy.md` (the checklist in
`${REPLICA_HOME:-/home/box/replica-skill}/cursor/skills/replica-deploy/preflight.md`, filled in).
## The rules
- **Nothing goes live without the user's go.** Show the preflight results and
ask.
- **The user buys and signs in.** The agent never buys a domain, enters a card,
types a password or pastes a live key. The agent writes the exact DNS records,
env var names and commands; the user does the account steps.
- **Not until it is rebranded.** The sweep must be clean. No exceptions.
## Step 1: preflight
Run `parity.py`, `sweep.py`, and `listing.py` on this computer. Hand `npx playwright test` and `npm run build` to a Cursor cloud coding agent. Do not edit the repository yourself.
Run every check and paste the results into `deploy.md`:
```bash
npx playwright test # replica-test
python3 "${REPLICA_HOME:-/home/box/replica-skill}/tools/parity.py" replica/features.csv # must-haves done
python3 "${REPLICA_HOME:-/home/box/replica-skill}/tools/sweep.py" . --config replica/brand.json # exit 0: clean
python3 "${REPLICA_HOME:-/home/box/replica-skill}/tools/listing.py" replica/launch/listing.json # if shipping to stores
npm run build # production build passes
```
Run `parity.py`, `sweep.py`, and `listing.py` on this
computer with the paths above. `npx playwright test` and `npm run build`
belong to the code repository: put them in the Cursor cloud coding agent's
task. Do not run any of this against the original app, and do not edit the
repository yourself.
Plus by hand: no open S1 or S2 bugs, privacy policy and terms pages live
(listing every processor), cookie banner if you use non-essential cookies in
the EU or UK, account deletion works, the favicon, titles and OG image are
yours.
Any failure stops the deploy. Say which and why.
## Step 2: production services
- A **separate production project** for the database (never the dev one),
backups on, migrations run by the deploy, not by hand.
- Env vars set in the host for production, matching `.env.example`. Live
keys only here.
- **Stripe**: switch to live mode, recreate products and prices, add the
production webhook endpoint and its signing secret, test one real
purchase and refund it.
- **OAuth**: add the production domain to every provider's redirect URIs and
authorised origins. Google scopes that need verification must be approved,
or only test users can sign in.
- **Email**: the sending domain verified with the provider.
## Step 3: host and domain
Default: Vercel for Next.js (Netlify, Cloudflare Pages, Fly or Render
otherwise). Connect the repo so `main` deploys and pull requests get preview
URLs.
The domain, after the user buys it at any registrar:
| record | name | value |
| --- | --- | --- |
| A | @ | the host's apex IP (Vercel: shown in the domain settings) |
| CNAME | www | the host's target (Vercel: `cname.vercel-dns.com`) |
| TXT | @ or a subdomain | the host's verification value, if asked |
Email DNS from the email provider: SPF (TXT), DKIM (CNAME or TXT), and a
DMARC record starting at `v=DMARC1; p=none; rua=mailto:you@yourdomain` then
tightened to `quarantine` once reports are clean. Without these, your
confirmation emails go to spam.
Pick one canonical host (apex or www) and redirect the other. HTTPS is
automatic on the hosts above; check it.
## Step 4: watch it
Error tracking (Sentry or the host's), uptime checks on the home page and the
core flow's API, logs kept, analytics (a privacy-friendly one avoids the
cookie banner), and an alert to the user's email or phone. Then do the core
flow on the live site yourself, and ask the user to do it on their phone.
## Step 5: mobile, if there is an app
Expo: `eas build` then `eas submit` to TestFlight and Play internal testing.
Native: archive in Xcode, upload to App Store Connect; Gradle bundle to Play
Console. The user owns the developer accounts ($99 a year for Apple, $25 once
for Google). Beta first, then review with the listing from replica-launch.
## Output
`replica/deploy.md` with every check and its result, the live URL, the DNS
records set, and what to watch in the first week. The clone is now an app
with your name on it.
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · letmefind/replica-skill-cursor-grok | 100 | MIT |
| lucasouzadev/agent-kit-skill | 100 | MIT |
| letmefind/replica-skill-cursor-grok | 100 | MIT |
| dmminga1983/minga-replica | 100 | MIT |
| jakeschincariol/replica-skill | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki ac4d39d2971c (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100fxreplica-deploy
Wdraża aplikację na własnej domenie: bramkę przedpublikacyjną, bazę produkcyjną, DNS, płatności na żywo, przekierowania OAuth, monitoring i buildy mobilne. - 100recreate-ship
Wdraża klon aplikacji na domenie użytkownika: bramka gotowości, baza produkcyjna, rekordy DNS, płatności Stripe i wersje mobilne. - 100swap-deploy
Wdraża produkt na własnej domenie po bramce go lub no-go: środowisko produkcyjne, rekordy DNS, certyfikaty, monitoring i kopie zapasowe. - 100site-deploy
Publikuje stronę na GitHub Pages lub Cloudflare Pages, konfiguruje własną domenę, rekordy DNS i sprawdza wynik po wdrożeniu. - 100launch-day
Prowadzi przez listę gotowości na start produktu: domenę, SSL, zmienne produkcyjne, DNS, bazę i płatności, a także plan wycofania. - 100deploy-to-vercel
Wdraża aplikacje i strony na Vercel: łączy projekt, publikuje podglądy i wersje produkcyjne, ustawia zmienne i domeny oraz sprawdza logi.