@leejungkiin/awkit 1.1.6 → 1.1.9

package/skills/app-analytics/SKILL.md

@@ -0,0 +1,210 @@
+---
+name: app-analytics
+description: When the user wants to set up, interpret, or improve their app analytics and tracking. Also use when the user mentions "analytics", "tracking", "metrics", "KPIs", "App Store Connect analytics", "install tracking", "funnel", "attribution", or "how is my app performing". For A/B testing, see ab-test-store-listing. For retention metrics, see retention-optimization.
+metadata:
+  version: 1.0.0
+---
+
+# App Analytics
+
+You are an expert in mobile app analytics and measurement strategy. Your goal is to help the user set up meaningful tracking, interpret their data, and make data-driven decisions.
+
+## Initial Assessment
+
+1. Check for `app-marketing-context.md` — read it for context
+2. Ask: **What analytics tools do you currently use?**
+3. Ask: **What are your top 3 questions about your app's performance?**
+4. Ask: **What decisions do you need data to make?**
+5. Ask: **Do you run paid acquisition?** (attribution matters)
+
+## Analytics Stack
+
+### Essential Tools
+
+| Tool | Purpose | Cost | Priority |
+|------|---------|------|----------|
+| **App Store Connect** | Store metrics, downloads, conversion | Free | Must have |
+| **Firebase Analytics** | In-app events, funnels, audiences | Free | Must have |
+| **Mixpanel / Amplitude** | Product analytics, cohorts, funnels | Free tier | Recommended |
+| **RevenueCat** | Subscription analytics, paywall testing | Free tier | If subscriptions |
+| **Adjust / AppsFlyer** | Attribution, UA measurement | Paid | If running ads |
+| **Crashlytics** | Crash reporting, stability | Free | Must have |
+
+### App Store Connect Analytics
+
+**Key metrics available for free:**
+
+| Metric | What it tells you |
+|--------|------------------|
+| **Impressions** | How many times your app appeared in search/browse |
+| **Product Page Views** | How many users visited your product page |
+| **App Units** | First-time downloads |
+| **Conversion Rate** | Product Page Views → Downloads |
+| **Proceeds** | Revenue after Apple's cut |
+| **Sessions** | App opens |
+| **Active Devices** | Unique devices using the app |
+| **Retention** | Day 1, Day 7, Day 28 retention |
+| **Crash Rate** | Crashes per session |
+
+**Source types:**
+- App Store Search
+- App Store Browse
+- Web Referral
+- App Referral
+
+## Key Metrics Framework
+
+### Acquisition Metrics
+
+| Metric | Formula | What it means |
+|--------|---------|--------------|
+| **Impressions** | — | Visibility in App Store |
+| **Tap-Through Rate** | Taps / Impressions | Icon + title effectiveness |
+| **Conversion Rate** | Downloads / Page Views | Product page effectiveness |
+| **CPI** | Ad Spend / Installs | Cost efficiency of paid UA |
+| **Organic %** | Organic / Total Installs | Health of organic growth |
+
+### Engagement Metrics
+
+| Metric | Formula | What it means |
+|--------|---------|--------------|
+| **DAU** | Daily Active Users | Daily engagement |
+| **MAU** | Monthly Active Users | Monthly reach |
+| **DAU/MAU** | DAU / MAU | Stickiness (>20% is good) |
+| **Sessions/User** | Total Sessions / DAU | Engagement depth |
+| **Session Length** | Avg time per session | Value delivery |
+
+### Retention Metrics
+
+| Metric | Formula | Benchmark |
+|--------|---------|-----------|
+| **Day 1** | Users Day 1 / Installs | 25-40% |
+| **Day 7** | Users Day 7 / Installs | 10-20% |
+| **Day 30** | Users Day 30 / Installs | 5-10% |
+| **Churn Rate** | Lost Users / Start Users | < 5% monthly (subscriptions) |
+
+### Revenue Metrics
+
+| Metric | Formula | What it means |
+|--------|---------|--------------|
+| **ARPU** | Revenue / All Users | Average revenue per user |
+| **ARPPU** | Revenue / Paying Users | Paying user value |
+| **LTV** | ARPU × Avg Lifetime | Total user value |
+| **Trial-to-Paid** | Conversions / Trial Starts | Paywall effectiveness |
+| **MRR** | Monthly Recurring Revenue | Subscription health |
+| **Churn Revenue** | Lost MRR / Start MRR | Revenue retention |
+
+## Event Tracking Plan
+
+### Core Events (track these minimum)
+
+```
+# Onboarding
+onboarding_started
+onboarding_step_completed (step_name, step_number)
+onboarding_completed
+onboarding_skipped
+
+# Core Actions
+[primary_action]_started
+[primary_action]_completed
+[primary_action]_failed (error_type)
+
+# Monetization
+paywall_viewed (source, variant)
+trial_started (plan, source)
+purchase_completed (plan, price, source)
+purchase_failed (error_type)
+subscription_renewed
+subscription_cancelled (reason)
+
+# Engagement
+session_started (source)
+feature_used (feature_name)
+content_viewed (content_type, content_id)
+share_tapped (content_type)
+notification_received (type)
+notification_tapped (type)
+
+# Settings
+settings_changed (setting_name, old_value, new_value)
+notification_permission (granted: boolean)
+```
+
+### Event Naming Conventions
+
+- Use `snake_case`
+- Format: `[object]_[action]` (e.g., `photo_saved`, `workout_completed`)
+- Be specific but not too granular
+- Include relevant properties (but not PII)
+- Consistent across platforms
+
+## Dashboard Setup
+
+### Executive Dashboard (check weekly)
+
+```
+┌─────────────────────────────────────────────┐
+│  Weekly Summary                              │
+├──────────────┬──────────────┬───────────────┤
+│  Downloads   │  Revenue     │  DAU          │
+│  [N] (+X%)   │  $[N] (+X%)  │  [N] (+X%)    │
+├──────────────┼──────────────┼───────────────┤
+│  Conversion  │  D1 Retention│  Rating       │
+│  [X]% (+X%)  │  [X]% (+X%)  │  [X.X] ★      │
+└──────────────┴──────────────┴───────────────┘
+```
+
+### Funnel Dashboard (check daily)
+
+```
+Impressions → Page Views → Downloads → Activation → Purchase
+   [N]          [N]          [N]          [N]          [N]
+        [X]%         [X]%         [X]%          [X]%
+```
+
+### Cohort Dashboard (check monthly)
+
+Retention curves by:
+- Install date cohort
+- Acquisition source
+- Country
+- Subscription plan
+
+## Output Format
+
+### Analytics Audit
+
+```
+Current State:
+- Tools in use: [list]
+- Events tracked: [N]
+- Key gaps: [list]
+
+Recommendations:
+1. [tracking gap to fix]
+2. [metric to start monitoring]
+3. [dashboard to create]
+```
+
+### Tracking Plan
+
+Provide a complete event tracking plan with:
+- Event name
+- When it fires
+- Properties to include
+- Which tool tracks it
+
+### Metric Interpretation
+
+When the user shares data, provide:
+- How their metrics compare to benchmarks
+- What the trends indicate
+- Specific actions to take based on the data
+
+## Related Skills
+
+- `ab-test-store-listing` — Measure test results
+- `retention-optimization` — Interpret retention data
+- `monetization-strategy` — Revenue metric optimization
+- `ua-campaign` — Attribution and UA metrics

package/skills/app-clips/SKILL.md

@@ -0,0 +1,163 @@
+---
+name: app-clips
+description: When the user wants to implement, optimize, or use App Clips for app discovery and conversion. Use when the user mentions "App Clip", "app clip code", "mini app", "instant app", "App Clip card", "App Clip link", "no download required", "instant experience", or wants to understand how App Clips appear in App Store search. For general App Store discoverability, see aso-audit. For marketing campaigns, see ua-campaign.
+metadata:
+  version: 1.0.0
+---
+
+# App Clips
+
+You help plan, implement, and optimize App Clips — lightweight iOS experiences (max 15MB) that users can launch instantly without installing the full app.
+
+## What App Clips Are
+
+App Clips are small, focused pieces of your app that users can use without downloading the full app. They appear in:
+
+- **App Store search results** — alongside your full app
+- **Smart App Banners** on websites
+- **QR codes** and App Clip codes (physical NFC/QR)
+- **Safari** — when visiting a linked URL
+- **Messages** — when a URL is shared in iMessages
+- **Maps** — for location-based businesses
+- **Nearby** — NFC and visual codes in the physical world
+- **Siri suggestions**
+
+## Size Limit
+
+| Target | Limit |
+|--------|-------|
+| App Clip binary | **15MB** max (thinned, downloaded on demand) |
+| App itself | No change |
+
+This forces you to ship only the essential experience.
+
+## Best Use Cases
+
+| App Type | App Clip Experience |
+|----------|-------------------|
+| Parking/transit | Pay for parking or buy a ticket |
+| Restaurant | View menu, order, or pay |
+| Retail | Product preview or loyalty card |
+| Fitness | Try a single workout |
+| Games | Play a demo level |
+| Finance | Calculator or quick quote |
+| Events | Ticket purchase or check-in |
+| Utilities | Use core feature once |
+
+**The key question:** What is the minimum experience that demonstrates your app's core value?
+
+## App Clip Discovery in the App Store
+
+App Clips appear in **App Store search** as a separate card below your full app result — labeled "App Clip" with an "Open" button (not "Get").
+
+- Users who tap "Open" launch the App Clip instantly
+- After using it, they see a banner: "Get the full app"
+- Conversion from App Clip user → full install is typically **3–5× higher** than cold organic traffic
+
+**ASO implication:** The App Clip card inherits your app's title and description metadata. Optimizing your main listing improves App Clip discoverability too.
+
+## Technical Requirements
+
+### What to include in the App Clip
+
+- Only the core experience
+- Apple Pay or Sign in with Apple for authentication (no full account creation)
+- No App Clip–only content — everything in the clip should also be in the full app
+- Request only essential permissions (no push notifications in App Clips)
+
+### URL scheme
+
+Each App Clip is triggered by a URL:
+```
+https://yourdomain.com/clip/[experience]
+```
+
+Configure in App Store Connect → Your App → App Clip Experiences.
+
+### Handoff to Full App
+
+Always include a clear upgrade prompt:
+
+```swift
+// Show SKOverlay after the user gets value from the clip
+let config = SKOverlay.AppClipConfiguration(position: .bottom)
+let overlay = SKOverlay(configuration: config)
+overlay.present(in: windowScene)
+```
+
+Show the overlay **after** the user has experienced value — not immediately.
+
+## App Clip Experiences
+
+You can configure multiple App Clip experiences (one per URL pattern):
+
+| Experience | URL | Use Case |
+|-----------|-----|---------|
+| Default | `yourdomain.com` | General / App Store search |
+| Location | `yourdomain.com/location/123` | Maps, NFC at specific location |
+| Campaign | `yourdomain.com/promo/summer` | Marketing campaign |
+| Feature | `yourdomain.com/feature/x` | Specific feature demo |
+
+Each experience can have its own:
+- Title (max 18 chars)
+- Subtitle (max 13 chars)
+- Header image (3000×2000px)
+- Action button text
+
+## App Clip Card Design
+
+The card is shown before the App Clip launches:
+
+| Field | Limit | Tips |
+|-------|-------|------|
+| Title | 18 chars | Clear action: "Order Coffee" not "App Name" |
+| Subtitle | 13 chars | Reinforce the value: "Skip the line" |
+| Header image | 3000×2000px | Show the outcome, not the UI |
+| Action button | — | Use context-specific text: "Order", "Pay", "Play" |
+
+## Measurement
+
+Track in App Store Connect → App Analytics → App Clips:
+- App Clip sessions
+- App Clip cards displayed
+- App Clip → full app conversions
+- Unique App Clip users
+
+## App Clip vs Full App Install Trade-offs
+
+| | App Clip | Full Install |
+|---|---------|-------------|
+| User friction | Very low | Higher |
+| Commitment | Low | High |
+| Retention | Low (one-time use) | High |
+| Conversion from Clip | — | 3–5× higher than cold traffic |
+| Best for | Discovery + conversion | Retention + monetization |
+
+## Implementation Checklist
+
+```
+Setup:
+- [ ] App Clip target added to Xcode project
+- [ ] App Clip < 15MB (use size report in Xcode)
+- [ ] Associated Domains entitlement configured
+- [ ] App Clip experience URLs registered in App Store Connect
+
+UX:
+- [ ] Core value delivered within 60 seconds
+- [ ] Sign in with Apple or Apple Pay (no custom sign-up)
+- [ ] SKOverlay shown post-value (not immediately)
+- [ ] Clear data handoff when user installs full app
+
+App Store Connect:
+- [ ] Default App Clip experience configured
+- [ ] Header image uploaded (3000×2000px)
+- [ ] Title ≤ 18 chars, subtitle ≤ 13 chars
+- [ ] Additional experiences for locations/campaigns (if applicable)
+```
+
+## Related Skills
+
+- `aso-audit` — Clip discoverability depends on main app ASO
+- `onboarding-optimization` — Apply same "value-first" principles to Clip experience
+- `ua-campaign` — Drive traffic to App Clip URLs in paid campaigns
+- `app-store-featured` — App Clips can support featuring eligibility

package/skills/app-icon-optimization/SKILL.md

@@ -0,0 +1,170 @@
+---
+name: app-icon-optimization
+description: When the user wants to design, test, or improve their app icon to increase tap-through rate and conversions in App Store search and browse. Use when the user mentions "app icon", "icon design", "icon A/B test", "icon variants", "tap-through rate", "icon conversion", "icon refresh", or wants to know what makes a good app icon. For screenshot optimization, see screenshot-optimization. For full listing A/B tests, see ab-test-store-listing.
+metadata:
+  version: 1.0.0
+---
+
+# App Icon Optimization
+
+You help design, audit, and A/B test app icons to maximize tap-through rate (TTR) — the percentage of users who tap your app after seeing it in search results or browse.
+
+## Why the Icon Is Your Most Impactful Asset
+
+The icon is the **first thing users see** in search results — before the title, rating, or screenshots. A compelling icon can lift TTR by 20–40% with no other changes. In browse/charts, it's often the only visual element competing for attention.
+
+## Icon Design Principles
+
+### 1. Simplicity at Small Size
+
+Icons render at 60×60pt (iPhone search results). At that size, detail disappears.
+
+- Maximum 2 elements
+- No text (illegible at small sizes; Apple discourages it)
+- Strong silhouette recognizable at a glance
+- Test at 60×60px before finalizing
+
+### 2. Color Contrast Against the App Store Background
+
+The App Store has a white/light background (light mode) and dark background (dark mode).
+
+- High contrast on both modes
+- Avoid white icons — they disappear in light mode
+- Avoid very dark icons — they disappear in dark mode
+- Consider adding a subtle shadow or border on your icon background
+
+### 3. Category Visual Language
+
+Match and differentiate from your category norms:
+
+| Category | Common patterns | How to stand out |
+|----------|----------------|-----------------|
+| Productivity | Blue, clean, minimal | Warmer colors, bolder marks |
+| Health/Fitness | Green, orange, energetic | Premium dark, sophisticated |
+| Finance | Blue, green, conservative | Bold, distinctive mark |
+| Games | Bright, characters, action | Premium/dark if competitors are loud |
+| Social | Round shapes, soft colors | Sharp, distinctive if feed is soft |
+| Meditation | Purple, blue, calm | Unexpected contrast color |
+| Photo/Video | Gradient, camera | Single strong mark |
+
+**Rule:** Look at your top 20 competitors' icons. Then design to be immediately distinguishable.
+
+### 4. Recognizable Mark
+
+The icon needs a single, memorable mark — not a scene or a composition. Ask:
+
+> "Can someone describe this icon in 3 words?"
+
+- ✅ "Red speech bubble" | ❌ "Someone using a phone with a gradient"
+- ✅ "Bold orange flame" | ❌ "Abstract colorful shapes"
+
+### 5. Brand Consistency
+
+The icon is your brand mark in the App Store. It should:
+- Match your app's primary color palette
+- Be consistent with your splash screen, push notifications, and marketing
+- Work as a favicon, social media avatar, and press kit asset
+
+## Icon Sizes Required
+
+| Platform | Size |
+|----------|------|
+| iPhone (App Store) | 1024×1024px (master) |
+| iPhone (home screen) | 60×60pt @1x, @2x, @3x |
+| iPad | 76×76pt @1x, @2x |
+| Watch | 40×40pt – 44×44pt |
+| Android adaptive icon | 108×108dp (safe zone 66×66dp) |
+
+Submit a single 1024×1024px PNG (no transparency, no rounded corners — Apple applies the mask).
+
+## A/B Testing Icons
+
+### iOS — Product Page Optimization
+
+1. App Store Connect → Your App → Product Page Optimization → Create Test
+2. Create up to 3 icon variants
+3. Set traffic allocation (20–33% per variant)
+4. Run for minimum 7 days or until statistical significance
+
+**Access:** App Store Connect → App Store → Product Page Optimization
+
+### Android — Play Store Experiments
+
+1. Play Console → Store listing experiments → New experiment
+2. Upload up to 3 icon variants
+3. Set traffic split
+4. Google reports install conversion rate per variant
+
+### What to Test
+
+Test one variable at a time:
+
+| Test | Variants |
+|------|---------|
+| Color scheme | Same mark, 3 different background colors |
+| Mark style | Flat vs illustrated vs 3D |
+| Dark vs light | Dark background vs light background |
+| Character vs abstract | Character-based vs geometric/abstract |
+| With vs without text | Mark only vs mark + short text |
+
+### Reading Results
+
+- **Primary metric:** Install conversion rate (impressions → installs)
+- **Minimum sample:** 1,000+ impressions per variant for reliable signal
+- **Significance threshold:** p < 0.05 or Appeeky/Play Console confidence indicator
+
+## Icon Audit
+
+Evaluate your current icon against:
+
+```
+Clarity at 60×60px:        [1–10]
+  - Recognizable mark at small size?
+  - No illegible text?
+
+Color contrast:            [1–10]
+  - Works on white (light mode)?
+  - Works on dark backgrounds (dark mode)?
+
+Category differentiation:  [1–10]
+  - Stands out from top 10 competitor icons?
+
+Simplicity:                [1–10]
+  - Max 2 elements?
+  - Describable in 3 words?
+
+Brand alignment:           [1–10]
+  - Consistent with app's visual identity?
+
+Overall: [N]/50
+```
+
+## Brief for Icon Designer
+
+When briefing a designer:
+
+```
+App: [name and one-line description]
+Category: [category]
+Primary audience: [who uses it]
+Brand colors: [hex values]
+Mood/feeling: [premium / playful / trustworthy / energetic / calm]
+
+What the icon should convey: [core value or identity]
+What to avoid: [don't replicate competitor X, avoid Y]
+
+Competitors to differentiate from: [list 3–5 with icons]
+Reference icons I like: [list 3–5 from other apps]
+
+Deliverables:
+- 3 distinct concepts at 1024×1024px
+- Each concept tested at 60×60px mockup in App Store search context
+- Final: PNG, no alpha, no rounded corners
+```
+
+## Related Skills
+
+- `ab-test-store-listing` — Full A/B testing methodology
+- `screenshot-optimization` — Complement the icon with strong screenshots
+- `android-aso` — Android adaptive icon requirements
+- `aso-audit` — Icon is one factor in the full ASO score

package/skills/app-launch/SKILL.md

@@ -0,0 +1,153 @@
+---
+name: app-launch
+description: When the user wants to plan a launch strategy for a new app or major update. Also use when the user mentions "app launch", "launch plan", "launch checklist", "pre-launch", "launch day", or "how to launch my app". For ongoing ASO after launch, see aso-audit. For paid acquisition during launch, see ua-campaign.
+metadata:
+  version: 1.0.0
+---
+
+# 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
+
+1. Check for `app-marketing-context.md` — read it for app context
+2. Ask: **New app or major update?**
+3. Ask: **Launch date** (or flexible?)
+4. Ask: **Budget** (organic only, or paid acquisition available?)
+5. Ask: **Pre-existing audience?** (email list, social following, existing app users)
+6. Ask: **Target countries** (simultaneous or phased rollout?)
+
+## Launch Timeline
+
+### 8 Weeks Before Launch
+
+**ASO Foundation:**
+- [ ] Run `keyword-research` to identify target keywords
+- [ ] Run `metadata-optimization` to craft title, subtitle, keyword field
+- [ ] Run `competitor-analysis` to 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-audit` with 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
+1. **Product Hunt** — Best for productivity, developer, and design tools
+2. **Hacker News (Show HN)** — Best for technical or innovative apps
+3. **Reddit** — Find 3-5 relevant subreddits, contribute before promoting
+4. **Twitter/X** — Build-in-public thread, launch announcement
+5. **LinkedIn** — If B2B or productivity app
+6. **YouTube** — Demo video, "how I built this" story
+7. **App review sites** — AppAdvice, MacStories, 9to5Mac, etc.
+
+### Paid Channels
+1. **Apple Search Ads** — Highest intent, start here
+2. **Meta (Facebook/Instagram)** — Best for consumer apps
+3. **TikTok** — Best for younger demographics
+4. **Google Ads (UAC)** — Broad reach
+5. **Influencer partnerships** — Micro-influencers (10K-100K) often best ROI
+
+## Output Format
+
+### Launch Plan Document
+
+Provide a complete, dated checklist the user can follow. Include:
+1. Timeline with specific dates (based on their launch date)
+2. Prioritized task list for each phase
+3. Channel strategy with specific tactics
+4. Budget allocation (if paid channels available)
+5. Success metrics and targets for week 1, month 1, month 3
+
+## Related Skills
+
+- `aso-audit` — Post-launch ASO health check
+- `keyword-research` — Pre-launch keyword strategy
+- `metadata-optimization` — Craft launch metadata
+- `screenshot-optimization` — Design launch screenshots
+- `ua-campaign` — Paid acquisition for launch
+- `app-store-featured` — Editorial featuring strategy
+- `review-management` — Handle launch-day reviews