How to use the Replica Launch Kit agent skill

What the replica-launch skill makes the agent do

Agent skills are folders of instructions and files that Claude loads when a task matches them. This one covers the launch stage of an app clone. It reads research from earlier steps in the project, including the product angle in replica/fixes.md, the original app's public pricing, and user complaints from feedback.md, along with replica/brand.md and replica/brand.json.

From that material it writes replica/launch/ with four files: landing.md, pricing.md, listing.json and launch-plan.md. The landing page is written section by section, starting with a hero and ending with a call to action. Pricing is set out as a table with three tiers at most.

• Landing page: hero, problem, how it works, features tied to fixes, pricing, FAQ and final call to action
• Pricing: the original's public pricing and two or three alternatives, reviewer comments on price and billing, and a proposed model
• Store listing: fields for the App Store and Google Play, checked by a script
• Launch plan: waitlist or beta list, analytics, places where the original's unhappy users talk, and a first 10 users plan

How to install the replica-launch skill

Download the ZIP for the skill from our page. Then choose one of the two install routes below.

For a personal skill that works in all your projects, unzip the download into ~/.claude/skills/. For a skill that only applies to one project, unzip it into that project's .claude/skills/ folder. Either way the skill folder should contain SKILL.md, listing.py and listing.example.json.

If you use the Claude apps instead, open Settings, go to Capabilities, then Skills, and upload the skill there.

• Personal install: ~/.claude/skills/
• Project install: .claude/skills/ inside your project
• Claude apps: Settings → Capabilities → Skills

How to trigger the skill with natural requests

You do not need a special command. The skill's description lists phrases that should bring it in, so ordinary requests work. Phrases it responds to include 'landing page', 'pricing', 'how much should I charge', 'App Store listing', 'store screenshots', 'launch plan' and 'Product Hunt'. It is also meant to run after the /replica-brand step.

Be specific about what you need and point the agent at the project's replica files, so it can read the research that already exists.

• Write the landing page for my app based on replica/fixes.md and the brand files.
• How much should I charge? Compare with the original's public pricing and the billing complaints in feedback.md.
• Draft the App Store and Google Play listing text and check it.
• Make a launch plan that starts with a waitlist and includes Product Hunt.

Run the listing checker before you submit

The bundled script listing.py checks your store listing. Start from listing.example.json in the skill folder, fill in your own listing as replica/launch/listing.json, then run the checker from the project folder. It needs only Python 3 and its standard library, so there are no packages to install.

The checker counts characters the way a person does and compares them with the store limits. For the App Store, the limits it checks are name 30, subtitle 30, promotional text 170, keywords 100 and description 4000. For Google Play they are title 30, short description 80 and full description 4000. It also flags ranking and price claims in short fields, emoji, wasted keyword characters, and any name listed in the avoid field, including the original app's name. It exits with code 1 when it finds an error, so it can be used in a script.

• Checks App Store limits: name, subtitle, promotional text, keywords and description
• Checks Google Play limits: title, short description and full description
• Flags ranking claims, price claims in short fields, emoji and wasted keyword characters
• Flags any name from the avoid list, including the original app's name
• Exits with code 1 on an error

What you need before you start

The skill expects the earlier steps of the surrounding workflow to have run. Without the research files the agent has nothing grounded to write from. A Stripe account is optional, and only needed if you want the pricing products created; you create those yourself. The companion skills replica-design and replica-deploy are referenced in the instructions and are optional.

• Python 3 (standard library only, no packages to install)
• Prior files: replica/fixes.md, replica/brand.md, replica/brand.json and feedback.md research
• Optional: a Stripe account for pricing products, which you create yourself
• Optional: the replica-design and replica-deploy companion skills

Safety notes: scripts and network access

The skill runs scripts. The bundled listing.py is the script it uses for checks, and the skill's documentation says to run it on your listing file. This skill is listed as not using the network, so the checker does not contact any server. Read the script before running it, as you would with any code you did not write yourself.

The skill also has rules about content. It will not invent testimonials, user counts, star ratings, press logos or 'trusted by' rows. It also will not use reviewers' quotes as endorsements, because the original app's reviews count as research only. Do not copy another company's app or branding. The skill itself warns that this breaks Apple's Guideline 4.1 (Copycats) and can lead to takedowns.

• Runs scripts: yes, listing.py checks the listing file you give it
• Uses network: no
• Will not write fake testimonials, user counts or press logos
• Will not use reviewer quotes as testimonials
• Warns against copying another app's branding (App Store Guideline 4.1)

Tips for getting useful results

The skill's own advice is to lead with your fixes rather than matching the original's features, since parity is only the price of entry. Make your fixes and brand visible in the first lines of the description and in the screenshots. Use real beta users only with their permission.

Treat the checker as a first pass. The skill says to verify limits and screenshot sizes in App Store Connect and Play Console when you upload, because they change. The checker only covers the rules it lists, so it is not legal or store-policy advice.

• Lead with the fixes from fixes.md, not parity features
• Keep pricing to three tiers at most, named by who they are for
• Check screenshot sizes and limits in App Store Connect and Play Console at upload time
• Use an empty proof section rather than a made-up one