replica-deploy
/replica-deploy
Wdraża klon aplikacji na własną domenę: bramkę przed startem, bazę produkcyjną, rekordy DNS, płatności na żywo 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
- 2
- 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
Wdraża klon aplikacji na własną domenę: bramkę przed startem, bazę produkcyjną, rekordy DNS, płatności na żywo 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
- Invoking skills
- Tools
- 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
## Invoking skills
In Cursor, type `/` in chat and choose the skill by name. That attaches it to
one message. To keep a skill active for the whole session, start it as a
Custom Mode: Option+Enter on macOS, or Alt+Enter on Windows. You can also
name the skill in an ordinary message when the request matches its description.
## Tools
The Python tools are shared by the pack. They need Python 3.8 or newer and
the standard library only.
`SKILL_DIR` is the directory that contains this file. After `cursor/install.sh`,
that is `.cursor/skills/<name>/` in a project, or `~/.cursor/skills/<name>/`
for a user install. The tools sit beside the skill folders, in `replica-tools/`.
Set `REPLICA_HOME` to a checkout of this pack to use `tools/` there instead.
```bash
if [ -n "${REPLICA_HOME:-}" ] && [ -d "${REPLICA_HOME}/tools" ]; then
TOOLS="${REPLICA_HOME}/tools"
elif [ -n "${REPLICA_HOME:-}" ]; then
TOOLS="${REPLICA_HOME}"
else
TOOLS="$(cd "$(dirname "$SKILL_DIR")" && pwd)/replica-tools"
fi
```
Reads everything in `replica/`. Writes `replica/deploy.md` (the checklist in
`preflight.md` in this folder, 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 every check and paste the results into `deploy.md`:
```bash
npx playwright test # replica-test
python3 "$TOOLS/parity.py" replica/features.csv # must-haves done
python3 "$TOOLS/sweep.py" . --config replica/brand.json # exit 0: clean
python3 "$TOOLS/listing.py" replica/launch/listing.json # if shipping to stores
npm run build # production build passes
```
`$TOOLS` is the directory from the Tools section above.
`cursor/install.sh` fills `replica-tools/` beside the skill folders. A checkout
of this pack uses `REPLICA_HOME` pointing at the pack root, where the same
files are in `tools/`.
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.
Pliki w paczce (2)
- SKILL.md 5 KB
- preflight.md 1 KB
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 7b3e65ecdcbd (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. - 100site-deploy
Publikuje stronę na GitHub Pages lub Cloudflare Pages, konfiguruje własną domenę, rekordy DNS i sprawdza wynik po wdrożeniu. - 100swap-deploy
Wdraża produkt na własnej domenie po bramce go lub no-go: środowisko produkcyjne, rekordy DNS, certyfikaty, monitoring i kopie zapasowe. - 100deploy-frontend-domain
Podłącza własną domenę do działającej strony, tłumaczy rekordy DNS prostym językiem, sprawdza obecne DNS i weryfikuje HTTPS przed każdą zmianą. - 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.