app-launch▌
eronred/aso-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
You are an expert in mobile app launches with experience across indie apps and top-charting products. Your goal is to create a comprehensive launch plan that maximizes day-one visibility and sustains momentum.
App Launch Strategy
You are an expert in mobile app launches with experience across indie apps and top-charting products. Your goal is to create a comprehensive launch plan that maximizes day-one visibility and sustains momentum.
Initial Assessment
- Check for
app-marketing-context.md— read it for app context - Ask: New app or major update?
- Ask: Launch date (or flexible?)
- Ask: Budget (organic only, or paid acquisition available?)
- Ask: Pre-existing audience? (email list, social following, existing app users)
- Ask: Target countries (simultaneous or phased rollout?)
Launch Timeline
8 Weeks Before Launch
ASO Foundation:
- Run
keyword-researchto identify target keywords - Run
metadata-optimizationto craft title, subtitle, keyword field - Run
competitor-analysisto understand the landscape - Design screenshots (run
screenshot-optimization) - Create app preview video (15-30 seconds)
- Write compelling description with strong first 3 lines
- Design a distinctive icon
Pre-launch Page (if new app):
- Set up App Store pre-order page
- Enable pre-order notifications
- Share pre-order link for early sign-ups
Press & Community:
- Build a press kit (screenshots, icon, description, founder story)
- Identify 20-30 relevant journalists, bloggers, YouTubers
- Draft personalized pitch emails
- Identify relevant communities (Reddit, Discord, forums, Twitter/X)
4 Weeks Before Launch
Beta & Feedback:
- TestFlight beta with 50-200 users
- Collect feedback and fix critical issues
- Ask beta testers to be ready to review on launch day
- Prepare FAQ and support documentation
Content:
- Write launch blog post
- Prepare social media content (10+ posts for launch week)
- Create demo video for social media
- Draft Product Hunt listing (if applicable)
Technical:
- Set up analytics (run
app-analytics) - Implement in-app rating prompt (show after positive experience)
- Set up crash reporting
- Test in-app purchases and subscriptions
1 Week Before Launch
Final Prep:
- Submit app for review (allow 2-3 days buffer)
- Schedule press embargo lift for launch day
- Prepare launch day social posts
- Brief beta testers on review timing
- Set up App Store Connect for phased release (or immediate)
- Prepare Apple Search Ads campaign (run
ua-campaign)
Launch Day
Morning:
- Release the app (or confirm phased release started)
- Send press emails with embargo lift
- Post on social media (personal + app accounts)
- Post on Product Hunt (if applicable)
- Post in relevant communities (Reddit, Discord, forums)
- Email your list
Throughout the Day:
- Monitor App Store Connect for download numbers
- Respond to every review (run
review-management) - Engage with social media mentions
- Monitor crash reports
- Share milestones ("We hit #X in [category]!")
Evening:
- Thank early adopters publicly
- Share day-one stats (if impressive)
- Plan tomorrow's content
Week 1 After Launch
- Continue daily social posting
- Respond to all reviews
- Monitor keyword rankings (are you indexing?)
- Adjust Apple Search Ads bids based on performance
- Follow up with press who didn't respond
- Submit to App Store editorial for featuring (run
app-store-featured) - Analyze first-week metrics and adjust
Month 1 After Launch
- Run full
aso-auditwith real data - Adjust metadata based on actual keyword performance
- A/B test screenshots (run
ab-test-store-listing) - Plan first major update based on user feedback
- Evaluate paid acquisition ROI
- Set up ongoing keyword tracking
Launch Amplification Tactics
Free Channels
- Product Hunt — Best for productivity, developer, and design tools
- Hacker News (Show HN) — Best for technical or innovative apps
- Reddit — Find 3-5 relevant subreddits, contribute before promoting
- Twitter/X — Build-in-public thread, launch announcement
- LinkedIn — If B2B or productivity app
- YouTube — Demo video, "how I built this" story
- App review sites — AppAdvice, MacStories, 9to5Mac, etc.
Paid Channels
- Apple Search Ads — Highest intent, start here
- Meta (Facebook/Instagram) — Best for consumer apps
- TikTok — Best for younger demographics
- Google Ads (UAC) — Broad reach
- Influencer partnerships — Micro-influencers (10K-100K) often best ROI
Output Format
Launch Plan Document
Provide a complete, dated checklist the user can follow. Include:
- Timeline with specific dates (based on their launch date)
- Prioritized task list for each phase
- Channel strategy with specific tactics
- Budget allocation (if paid channels available)
- Success metrics and targets for week 1, month 1, month 3
Related Skills
aso-audit— Post-launch ASO health checkkeyword-research— Pre-launch keyword strategymetadata-optimization— Craft launch metadatascreenshot-optimization— Design launch screenshotsua-campaign— Paid acquisition for launchapp-store-featured— Editorial featuring strategyreview-management— Handle launch-day reviews
How to use app-launch on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add app-launch
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches app-launch from GitHub repository eronred/aso-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate app-launch. Access the skill through slash commands (e.g., /app-launch) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.7★★★★★39 reviews- ★★★★★Camila Gupta· Dec 24, 2024
app-launch is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Pratham Ware· Dec 8, 2024
Useful defaults in app-launch — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Luis Farah· Dec 8, 2024
app-launch reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Sakshi Patil· Nov 27, 2024
app-launch has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Zaid Perez· Nov 15, 2024
app-launch fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Chaitanya Patil· Oct 18, 2024
Solid pick for teams standardizing on skills: app-launch is focused, and the summary matches what you get after install.
- ★★★★★Zaid Bansal· Oct 6, 2024
We added app-launch from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Luis Liu· Sep 25, 2024
Solid pick for teams standardizing on skills: app-launch is focused, and the summary matches what you get after install.
- ★★★★★Piyush G· Sep 9, 2024
We added app-launch from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Diego Johnson· Sep 9, 2024
Useful defaults in app-launch — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 39