Generates pre-order setup guides and launch timeline templates for App Store pre-orders. Use when planning a pre-order strategy for a new app launch or major update.
npx skills add https://github.com/rshankras/claude-code-apple-skills --skill pre-orders
Generate pre-order configuration guides, launch timeline templates, and marketing coordination plans for App Store pre-orders.
Use this skill when the user:
An existing app entering new storefronts can run a pre-order in just those territories — with a longer runway: the release date can be up to 365 days out (vs. 180 for an unreleased app), and any date change is capped at 365 days from when the pre-order first published. Accumulated pre-orders convert on day one in the new market — the same velocity spike a launch gets, aimed at the new market's chart entry.
⚠️ One-shot per territory: once released in a region, you can never run a pre-order there again.
Ask user via AskUserQuestion:
# Pre-Order Plan: [App Name]
## Configuration
| Setting | Value |
|---------|-------|
| Pre-Order Start | [Date] |
| Release Date | [Date] |
| Pre-Order Duration | [X weeks] |
| Price During Pre-Order | [Free / $X.99] |
| Post-Launch Price | [$X.99] |
## App Store Connect Setup
1. Go to App Store Connect > Your App
2. Under "Pricing and Availability":
- Set the release date to your planned launch date
- Enable "Pre-Order" availability
3. Under "App Information":
- App name, category, and description must be final
- Screenshots should show the final app (or close to final)
4. Submit app for review:
- App must pass review before pre-order goes live
- Prepare a TestFlight-ready build for review
## Launch Timeline
### [X] Weeks Before Launch: Pre-Order Goes Live
- [ ] Submit app for App Store review
- [ ] Prepare pre-order announcement
- [ ] Schedule social media posts
- [ ] Send press kit to media contacts
- [ ] Configure In-App Event for launch day
### [X-2] Weeks Before: Build Anticipation
- [ ] Share development updates/behind-the-scenes
- [ ] Release app preview video on social channels
- [ ] Follow up with press contacts
- [ ] Share pre-order link in email newsletter
### 1 Week Before: Final Push
- [ ] Countdown posts on social media
- [ ] Featuring nomination follow-up
- [ ] Prepare launch day communications
- [ ] Verify build is ready for release
### Launch Day
- [ ] Release the app (automatic for pre-orders)
- [ ] Publish launch In-App Event
- [ ] Send launch announcement to email list
- [ ] Post across all social channels
- [ ] Monitor reviews and respond quickly
- [ ] Track download velocity
### Launch Week
- [ ] Start Product Page Optimization test
- [ ] Monitor conversion rates
- [ ] Adjust marketing based on initial data
- [ ] Submit second featuring nomination if not featured
## Pre-Order Marketing Assets
### Landing Page
- Apple's official **localized pre-order badge** (per-storefront artwork — don't hand-roll the button)
- App preview screenshots
- Feature highlights
- Release date and countdown
### Social Media
- Announcement post with pre-order link
- 3-5 countdown posts leading to launch
- Feature highlight posts (one feature per post)
- Behind-the-scenes development content
### Email
- Pre-order announcement to existing audience
- 1-week reminder before launch
- Launch day celebration email
## Measurement
| Metric | Target | Track In |
|--------|--------|----------|
| Pre-order count | [Goal] | App Store Connect |
| Day 1 downloads | [Goal] | App Store Connect |
| First week downloads | [Goal] | App Store Connect |
| Conversion rate | [X%] | App Store Connect Analytics |
| Scenario | Recommended Duration | Reason |
|----------|---------------------|--------|
| Indie app, small audience | 2-4 weeks | Short attention span, limited reach |
| Established brand, new app | 4-8 weeks | Time for press and marketing |
| Seasonal launch | Align with season start | Holiday: early Nov, Back to school: mid-Aug |
| WWDC tie-in | Start at WWDC, launch with OS | Ride the hype wave |
| Model | During Pre-Order | After Launch | Best For |
|-------|-----------------|-------------|----------|
| Free launch | Free | Free | Freemium apps, maximum pre-orders |
| Introductory price | $0.99-2.99 | $4.99-9.99 | Create urgency, reward early adopters |
| Full price | $X.99 | $X.99 | Premium apps with strong demand |
| Free then paid | Free | $X.99 | Controversial — may frustrate expectations |
generators/in-app-events — Launch event for release daygenerators/featuring-nomination — Featuring during pre-ordergenerators/app-store-assets — Asset specs for pre-order pageapp-store/marketing-strategy — Pre-launch as part of overall strategyGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.
Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.
Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
Take rshankras/pre-orders from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.