replica-launch
/replica-launch
Pisze stronę startową klonu aplikacji na bazie kąta pozycjonowania, z cenami i opisami sklepowymi sprawdzonymi pod kątem limitów.
- 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
Pisze stronę startową klonu aplikacji na bazie kąta pozycjonowania, z cenami i opisami sklepowymi sprawdzonymi pod kątem limitów.
Wyzwalacze z opisu
Oryginalny opis (EN)
Writes the launch for an app clone: the landing page built on the positioning angle, pricing set against the original''s public pricing and its users'' complaints, and the App Store and Google Play listing linted against the stores'' limits and copycat rules. Use when the user says "landing page", "pricing", "how much should I charge", "App Store listing", "store screenshots", "launch plan", "Product Hunt", or after the replica-brand skill.
Jak działa
- On this computer
- The rules
- Step 1: landing page
- Step 2: pricing
- Step 3: store listing
- Step 4: launch plan
- Output
Podgląd SKILL.md
---
name: replica-launch
description: 'Writes the launch for an app clone: the landing page built on the positioning angle, pricing set against the original''s public pricing and its users'' complaints, and the App Store and Google Play listing linted against the stores'' limits and copycat rules. Use when the user says "landing page", "pricing", "how much should I charge", "App Store listing", "store screenshots", "launch plan", "Product Hunt", or after the replica-brand skill.'
---
# replica-launch
## On this computer
Write the launch documents under `/workspace/<project-slug>/replica/launch/`.
Pricing research uses web search and the public pricing pages. Record the
date you read each price. Reviews stay research. Do not quote them as
testimonials, and do not invent proof.
Building the landing page inside the repository is a task for a Cursor cloud
coding agent. Do not edit the repository yourself. The task includes
`landing.md`, the brand voice, and the contrast rule.
You do not submit the app to a store and you do not spend money. The user does
that. Never send a launch post or an email unless the user has explicitly
asked you to send that exact message.
Reads `replica/fixes.md` (the angle and the evidence), `replica/brand.md`,
and `replica/brand.json`. Writes `replica/launch/`: `landing.md`,
`pricing.md`, `listing.json`, `launch-plan.md`.
```bash
python3 "${REPLICA_HOME:-/home/box/replica-skill}/tools/listing.py" replica/launch/listing.json # limits, claims, the original's name
```
Start from `${REPLICA_HOME:-/home/box/replica-skill}/cursor/skills/replica-launch/listing.example.json`.
## The rules
- **No fake proof.** No invented testimonials, user counts, star ratings,
press logos or "trusted by" rows. An empty proof section is better than a
fake one. Real beta users, with permission, are fine.
- **No reviewer quotes as testimonials.** The original's reviews are research.
- **The original's name stays out** of your app name, store listing, keywords
and ads. Apple and Google reject it, and it invites a takedown.
## Step 1: landing page
`landing.md`, section by section, then build it in the project.
Write the document under `/workspace/<project-slug>/replica/launch/`. Building the page in the repository is a task for a Cursor cloud coding agent. Do not edit the repository yourself.
1. **Hero**: the angle as a headline (what you do, for whom), one line under
it, one button. Screenshot of the real product.
2. **The problem**: the top two "hate" themes, in plain words. Paraphrase,
do not quote reviewers.
3. **How it works**: three steps, from the core flow.
4. **Features**: each tied to a fix from `fixes.md`. Lead with the fixes,
not the parity features. Parity is the price of entry.
5. **Pricing**: the table from step 2.
6. **FAQ**: the real objections, including "can I import from {{category}}
tools?" if you built an importer.
7. **Final call to action.**
Copy in the brand voice. Run replica-design's contrast check on the page.
## Step 2: pricing
`pricing.md`:
- The original's public pricing page and 2 or 3 alternatives, in one table,
with the URL and the date read. Prices change, so the date matters.
- What reviewers said about price and billing, from `feedback.md`, with counts.
- The model: free plan or trial, per seat or flat, monthly and annual
(annual usually 2 months free).
- Three tiers at most. Name them by who they are for.
- Fix the billing complaints in the product: one-click cancel, clear renewal
emails, no surprise per-seat jumps.
- The Stripe products and prices to create (the user creates them).
## Step 3: store listing
Fill `listing.json`, then:
```bash
python3 "${REPLICA_HOME:-/home/box/replica-skill}/tools/listing.py" replica/launch/listing.json
```
It checks App Store limits (name 30, subtitle 30, promotional text 170,
keywords 100, description 4000) and Google Play's (title 30, short
description 80, full 4000), counts characters the way a person does, flags
ranking and price claims in short fields, emoji, wasted keyword characters,
and **any name from `avoid`** anywhere in the listing. Exit 1 on an error.
Apple's App Review Guideline 4.1 (Copycats) rejects apps that simply copy a
popular app or make minor changes to another app's name or UI. Your fixes
and your own brand are what get you through review, so make them visible in
the screenshots and the first lines of the description.
Also prepare: screenshots at the current required sizes (check App Store
Connect and Play Console when you upload, they change), privacy labels and
the data safety form, privacy policy and support URLs, age rating, and review
notes with a demo account the reviewer can use.
## Step 4: launch plan
`launch-plan.md`: a waitlist or beta list before launch, analytics and error
tracking live, where the original's unhappy users talk (the Reddit threads
and communities from the research), a Product Hunt or Hacker News post that
leads with the fix, and the first 10 users to talk to by hand.
## Output
`replica/launch/` complete, the landing page built, `listing.py` passing.
Next: the replica-deploy skill.
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 b2cd5c0a2ef9 (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
- 100recreate-launch
Przygotowuje start klonu aplikacji: stronę lądowania, cenę względem publicznych cen oryginału i opis w App Store oraz Google Play. - 100fxreplica-launch
Przygotowuje start klonu aplikacji: stronę lądowania, ceny oraz treści do sklepów App Store i Google Play. - 100swap-launch
Przygotowuje stronę sprzedażową, cennik, opis w sklepie i szkice stron prawnych dla produktu, a opis sprawdza skryptem pod kątem limitów. - 100replica-brand
Przygotowuje brief logo, zasady głosu i paletę kolorów dla klonu aplikacji oraz narzędzie przeglądające kod pod kątem śladów oryginału. - 100replica-brand
Tworzy własną nazwę, paletę i głos marki dla klonu aplikacji, sprawdza wolne domeny i znaki towarowe oraz szuka pozostałości po oryginale. - 90store-listing
Pisze i wgrywa opisy aplikacji w Google Play i App Store: tytuły, opisy, słowa kluczowe i zrzuty ekranu, w limitach sklepów.