replica-launch Checked

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 /replica-brand.

replica-launch

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.

python3 listing.py replica/launch/listing.json      # limits, claims, the original's name

Start from listing.example.json in this folder.

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 /replica-brand.

replica-launch

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.

python3 listing.py replica/launch/listing.json      # limits, claims, the original's name

Start from listing.example.json in this folder.

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:

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:

python3 listing.py replica/launch/listing.json