@leejungkiin/awkit 1.1.6 → 1.1.7

package/skills/press-and-pr/SKILL.md

@@ -0,0 +1,204 @@
+---
+name: press-and-pr
+description: When the user wants to get press coverage, media mentions, or editorial features for their app — including writing press releases, pitching journalists, getting on "best apps" lists, or building an app press kit. Use when the user mentions "press", "PR", "media coverage", "TechCrunch", "journalist", "press release", "app press kit", "get featured in media", "editorial coverage", "review from a blogger", or "app launch announcement". For Apple editorial featuring, see app-store-featured. For launch strategy, see app-launch.
+metadata:
+  version: 1.0.0
+---
+
+# Press & PR for Apps
+
+You help indie developers and app teams get genuine media coverage — which drives installs, backlinks, and App Store credibility.
+
+## Why Press Still Matters
+
+- **Web referral** in App Store Connect directly tracks installs from press links
+- **Backlinks** from high-authority sites (TechCrunch, The Verge) improve web presence
+- **Social proof** — "As seen on…" on your product page improves conversion
+- **Apple editorial** — press coverage increases editorial featuring consideration
+- **Organic amplification** — articles get shared, creating discovery beyond the original publication
+
+## Target Media Tiers
+
+### Tier 1 — High impact, harder to get
+
+| Publication | Focus | Notes |
+|-------------|-------|-------|
+| TechCrunch | Consumer tech, startups | Exclusives preferred |
+| The Verge | Consumer tech | Curated; quality bar is high |
+| Wired | Tech culture | Long-form, unique angle needed |
+| Fast Company | Innovation, productivity | Strong business angle |
+| 9to5Mac | iOS/macOS apps | App-specific, accessible |
+| MacStories | iOS apps | Very accessible for indie devs |
+
+### Tier 2 — Accessible, meaningful reach
+
+| Type | Examples |
+|------|---------|
+| App review blogs | AppAdvice, TouchArcade (games), AppShopper |
+| Niche newsletters | App-specific verticals (health, productivity, finance newsletters) |
+| YouTube channels | AppFind, MKBHD (for significant apps), niche channels |
+| Podcasts | App podcast appearances, niche shows |
+
+### Tier 3 — Start here
+
+| Type | Examples |
+|------|---------|
+| Reddit | r/iphone, r/androidapps, r/productivity (category-specific) |
+| Product Hunt | Launch day visibility |
+| Hacker News | Show HN post for technical/productivity apps |
+| Indie hackers | For indie developer community coverage |
+
+## What Makes a Story
+
+Press doesn't cover apps — they cover **stories**. Find your angle:
+
+| Angle | Example |
+|-------|---------|
+| **Numbers** | "App hit 100K downloads in 7 days with no marketing" |
+| **Problem solved** | "Solo dev built X because no existing tool did Y" |
+| **Unique data** | "Our app analyzed 10M habit logs — here's what we learned" |
+| **Category creation** | "We invented a new category of [type] app" |
+| **David vs Goliath** | Indie beating a Big Tech competitor |
+| **Timely** | Tied to a current news trend or cultural moment |
+| **Human story** | Founder's compelling personal motivation |
+
+**Test your angle:** Can you explain the story in 1 sentence that would make someone say "interesting"?
+
+## Press Kit
+
+Create a `presskit/` folder on your website or a Notion page with:
+
+```
+Press Kit Contents:
+- [ ] App name, one-liner, category
+- [ ] 3 founder photos (high-res, print-quality)
+- [ ] App icon (1024×1024px, PNG)
+- [ ] 5–10 screenshots (phone mockups, high-res)
+- [ ] App preview video (optional but impactful)
+- [ ] 3-sentence company/founder bio
+- [ ] Key stats (downloads, ratings, notable users)
+- [ ] Press quotes / prior coverage (if any)
+- [ ] App Store link + website
+- [ ] Press contact email
+```
+
+Host at: `yoursite.com/press` or a publicly shared Notion/Google Drive link.
+
+## Press Release Structure
+
+```
+FOR IMMEDIATE RELEASE
+
+[Headline — most newsworthy fact as a statement]
+[Subheadline — supporting detail]
+
+[City, Date] — [Hook sentence: what happened and why it matters]
+
+[Paragraph 1: The news — who, what, when, where]
+
+[Paragraph 2: The why — problem being solved, backstory, unique approach]
+
+[Paragraph 3: A quote from the founder]
+"[Quote that adds voice, not just restates facts]" — [Name], [Title], [Company]
+
+[Paragraph 4: Key features or data points — 3 max]
+
+[Paragraph 5: Availability, pricing, platforms]
+[App Name] is available on [iOS/Android/both] for [free/price]. Download at [App Store link].
+
+###
+
+About [Company]:
+[2–3 sentences]
+
+Media Contact:
+[Name] | [email] | [phone optional]
+```
+
+## Pitching Journalists
+
+### The Cold Pitch Email
+
+```
+Subject: [App Name] — [your angle in 8 words]
+e.g., "Habitica clone reached #1 Health with zero ad spend"
+
+Hi [First name],
+
+[1 sentence: why you're reaching out to them specifically]
+e.g., "I read your piece on [recent article] — [App Name] is related."
+
+[1 sentence: what the app does]
+[1 sentence: the story angle / most interesting stat or fact]
+[1 sentence: why now / why timely]
+
+Happy to send a promo code, press kit, or get on a quick call.
+
+[Your name]
+[App Store link]
+[Press kit link]
+```
+
+**Rules:**
+- Max 5 sentences in the pitch
+- Personalize the first line for each journalist — no mass blast
+- Don't attach files — link to your press kit
+- Send Tuesday–Thursday, 8–10am recipient's timezone
+- Follow up once after 5 business days — then move on
+
+### Finding the Right Journalists
+
+1. Search the target publication for recent app reviews in your category
+2. Note the byline — pitch that specific writer
+3. Check their Twitter/X bio for DM preference
+4. Use tools like Hunter.io for email guessing (format: first@publication.com)
+
+## Embargo Strategy
+
+For major launches, offer an embargo:
+
+- Contact journalists 1–2 weeks before launch
+- Offer exclusive access under embargo (story publishes on launch day)
+- One journalist per tier (don't offer the same exclusive to two competing outlets)
+- Provide TestFlight / Play beta access
+
+Exclusives dramatically increase pickup from Tier 1 publications.
+
+## Product Hunt Launch
+
+| Step | When | Action |
+|------|------|--------|
+| Create coming soon | 2 weeks before | Enable "coming soon" to collect followers |
+| Find a hunter | 1 week before | Ask an influential PH user to "hunt" you |
+| Prepare assets | 3 days before | Gallery, tagline, description, first comment |
+| Launch day | Tuesday–Thursday | Ship at 12:01am PST; all-day community engagement |
+| Follow-up post | Launch + 1 week | Share results as a Show HN or maker story |
+
+## Output Format
+
+### PR Plan
+
+```
+Story angle: [one sentence]
+
+Media targets:
+  Tier 1: [publication + journalist name]
+  Tier 2: [2–3 blogs/newsletters]
+  Tier 3: Product Hunt, Reddit r/[category], HN
+
+Timeline:
+  T-14: Press kit ready, press release drafted
+  T-10: Embargo pitches sent to Tier 1
+  T-7:  Follow-ups + Tier 2 pitches
+  T-0:  Launch + Product Hunt + Tier 3 posts
+  T+3:  Thank reporters who covered, share articles
+
+Press kit: [link]
+Press contact: [email]
+```
+
+## Related Skills
+
+- `app-launch` — Full launch strategy (PR is one channel within it)
+- `app-store-featured` — Press coverage supports Apple editorial consideration
+- `ua-campaign` — Complement PR with paid UA on launch week

package/skills/rating-prompt-strategy/SKILL.md

@@ -0,0 +1,184 @@
+---
+name: rating-prompt-strategy
+description: When the user wants to improve their app's star rating, increase ratings volume, optimize when and how they prompt users for a review, or recover from a bad rating period. Use when the user mentions "app rating", "star rating", "review prompt", "SKStoreReviewRequest", "In-App Review API", "ask for review", "low rating", "rating drop", "get more reviews", or "recover from 1-star". For responding to reviews, see review-management. For overall ASO health, see aso-audit.
+metadata:
+  version: 1.0.0
+---
+
+# Rating Prompt Strategy
+
+You optimize when, how, and to whom an app shows review prompts — maximizing high ratings while minimizing negative ones. Ratings are an App Store ranking signal and a conversion factor on the product page.
+
+## Why Ratings Matter for ASO
+
+- **Search ranking** — Apps with higher ratings rank better for competitive keywords
+- **Conversion** — Rating stars are visible in search results; a 4.8 beats 4.2 at a glance
+- **iOS:** Rating resets per version (you can request a reset in App Store Connect)
+- **Android:** Ratings are permanent and cumulative — one bad period is hard to recover
+
+## The Core Rule
+
+**Only prompt users who have experienced value.** Prompting too early produces low ratings. Prompting at a success moment produces 4–5 star ratings.
+
+## iOS — SKStoreReviewRequest
+
+Apple's native prompt. Rules:
+- Shows at most **3 times per year** regardless of how many times you call it
+- Apple controls the display logic — calling it doesn't guarantee it shows
+- Never prompt after an error, crash, or frustrating moment
+- Cannot customize the prompt UI
+
+```swift
+import StoreKit
+
+// Call at the right moment
+if let scene = UIApplication.shared.connectedScenes.first as? UIWindowScene {
+    SKStoreReviewController.requestReview(in: scene)
+}
+```
+
+## Android — Play In-App Review API
+
+Google's native prompt. Rules:
+- No hard limits, but Google throttles it if called too often
+- Show after a clear positive moment
+- Cannot determine if the user actually rated (privacy)
+
+```kotlin
+val manager = ReviewManagerFactory.create(context)
+val request = manager.requestReviewFlow()
+request.addOnCompleteListener { task ->
+    if (task.isSuccessful) {
+        val reviewInfo = task.result
+        val flow = manager.launchReviewFlow(activity, reviewInfo)
+        flow.addOnCompleteListener { /* proceed */ }
+    }
+}
+```
+
+## Timing Framework
+
+### The Success Moment Trigger
+
+Define 1–3 "success moments" in your app where users are most satisfied:
+
+| App Type | Good Prompt Moments | Bad Prompt Moments |
+|----------|--------------------|--------------------|
+| Fitness | After completing a workout | After skipping a session |
+| Productivity | After completing a project/task | After a failed save or sync error |
+| Games | After winning a level or beating a boss | After losing or failing |
+| Finance | After first successful transaction | After a confusing error |
+| Meditation | After completing a session | On cold open |
+| Shopping | After a successful purchase/delivery | After a failed checkout |
+
+### Session-Based Rules
+
+Only prompt users who meet all criteria:
+
+```
+Criteria to prompt:
+✓ Sessions >= 3 (not a first-time user)
+✓ Time since install >= 3 days
+✓ Has completed [activation event] at least once
+✓ No crash in last session
+✓ No negative signal (error, cancellation) in current session
+✓ Not already rated this version
+```
+
+## Pre-Prompt Survey (Recommended)
+
+Before triggering the native prompt, show a single in-app question:
+
+```
+"Are you enjoying [App Name]?"
+  [Yes, love it!]   [Not really]
+```
+
+- **"Yes"** → trigger `SKStoreReviewRequest` / Play In-App Review
+- **"Not really"** → show a feedback form (email or in-app), **do not** trigger the native prompt
+
+This filters out dissatisfied users before they can rate you 1–2 stars.
+
+**Expected improvement:** 0.3–0.8 stars on average with a pre-prompt filter.
+
+## Version-Gating (iOS)
+
+iOS allows you to reset ratings per version in App Store Connect. Use this strategically:
+
+- **Reset after a major improvement** — If you fixed the top-complained issues
+- **Do not reset** after a controversial change that users disliked
+- After a reset, run an aggressive (but filtered) prompt campaign in the first 7 days
+- Target your most engaged users first (longest session history)
+
+## Recovering from a Rating Drop
+
+### Diagnosis
+
+1. Check which version caused the drop — correlate with release dates
+2. Read the 1-star reviews for that period — find the common complaint
+3. Fix the issue in the next release
+4. Reply to every 1–3 star review (see `review-management` skill)
+
+### Recovery Campaign
+
+After the fix is shipped:
+1. Reply to negative reviews: "Fixed in version X.X — please update and let us know"
+2. Some users will update their rating after a reply
+3. Run a prompt campaign targeted at your most loyal users (highest session count)
+4. Do not prompt users who left a negative review
+
+### Timeline
+
+```
+Day 0:   Issue identified — hotfix or patch in progress
+Day 1–3: Reply to every negative review acknowledging the issue
+Day 7:   Fix shipped — reply to previous negative reviews "Fixed in X.X"
+Day 8+:  Enable prompt for sessions >= 5, no crash last 7 days
+Week 3:  Monitor rating trend — should recover 0.2–0.5 stars in 2–4 weeks
+```
+
+## Prompt Frequency
+
+| Platform | Maximum | Recommended |
+|----------|---------|-------------|
+| iOS | 3× per 365 days (Apple-enforced) | 1–2× per version |
+| Android | No hard limit (Google throttles) | 1× per 30 days per user |
+
+Never show the prompt twice in the same session.
+
+## Output Format
+
+### Rating Strategy Plan
+
+```
+Current rating: [X.X] ★  ([N] ratings)
+Platform: iOS / Android / Both
+
+Success moments identified:
+1. [Event name] — fires when [condition]
+2. [Event name] — fires when [condition]
+
+Pre-prompt survey: Yes / No
+  If yes: "Are you enjoying [App Name]?" → Yes / Not really
+
+Prompt trigger logic:
+  Sessions >= [N]
+  Days since install >= [N]
+  No crash in last [N] sessions
+  [Activation event] completed: yes
+  Already rated this version: no
+
+Expected outcome: +[X] stars over [N] weeks
+
+Recovery plan (if rating < 4.0):
+  1. [Fix] — ship by [date]
+  2. [Reply strategy] — [N] reviews to address
+  3. [Prompt campaign] — start [date], target [segment]
+```
+
+## Related Skills
+
+- `review-management` — Respond to reviews to recover rating
+- `onboarding-optimization` — Fix activation issues that drive 1-star reviews
+- `android-aso` — Play In-App Review API context
+- `retention-optimization` — Engaged users give better ratings

package/skills/retention-optimization/SKILL.md

@@ -0,0 +1,165 @@
+---
+name: retention-optimization
+description: When the user wants to reduce churn, improve user engagement, or increase lifetime value. Also use when the user mentions "retention", "churn", "users leaving", "engagement", "DAU/MAU", "user activation", or "why are users uninstalling". For onboarding-specific issues, see app-launch. For monetization, see monetization-strategy.
+metadata:
+  version: 1.0.0
+---
+
+# Retention Optimization
+
+You are an expert in mobile app retention and engagement strategy. Your goal is to diagnose retention issues and provide a prioritized plan to keep users coming back.
+
+## Initial Assessment
+
+1. Check for `app-marketing-context.md` — read it for context
+2. Ask for **current retention metrics** (Day 1, Day 7, Day 30 if available)
+3. Ask for **app category** (benchmarks vary dramatically)
+4. Ask about **monetization model** (retention strategy differs for free vs subscription)
+5. Ask about **current engagement features** (push notifications, streaks, etc.)
+
+## Retention Benchmarks
+
+### Industry Averages (Day 1 / Day 7 / Day 30)
+
+| Category | Day 1 | Day 7 | Day 30 | Good |
+|----------|-------|-------|--------|------|
+| Games | 25-30% | 10-15% | 3-5% | D1 >35%, D30 >8% |
+| Social | 30-35% | 15-20% | 8-12% | D1 >40%, D30 >15% |
+| Health & Fitness | 20-25% | 10-12% | 4-6% | D1 >30%, D30 >10% |
+| Productivity | 15-20% | 8-10% | 3-5% | D1 >25%, D30 >8% |
+| E-commerce | 15-20% | 5-8% | 2-3% | D1 >25%, D30 >5% |
+| Finance | 20-25% | 10-12% | 5-8% | D1 >30%, D30 >10% |
+| Education | 15-20% | 8-10% | 3-5% | D1 >25%, D30 >8% |
+
+## Retention Framework
+
+### 1. Activation (Day 0-1)
+
+The first session determines everything. Users who don't reach the "aha moment" in session 1 rarely return.
+
+**Diagnose:**
+- What % of users complete onboarding?
+- How long until the first value moment?
+- What's the drop-off point in the first session?
+
+**Optimize:**
+- Reduce time-to-value (show core value in < 60 seconds)
+- Remove unnecessary onboarding steps
+- Defer account creation until after value delivery
+- Use progressive disclosure (don't overwhelm)
+- Show a "quick win" in the first session
+
+### 2. Habit Formation (Day 1-7)
+
+**Diagnose:**
+- What triggers bring users back?
+- Is there a natural usage frequency?
+- What do retained users do that churned users don't?
+
+**Optimize:**
+- **Push notifications** — Personalized, value-driven, not spammy
+  - Day 1: "Welcome back — here's what you missed"
+  - Day 3: "[Specific value] is waiting for you"
+  - Day 7: "You're on a [N]-day streak!"
+- **Streaks & progress** — Visual progress indicators
+- **Daily content** — New content, challenges, or recommendations
+- **Social hooks** — Friends, leaderboards, sharing
+
+### 3. Engagement Deepening (Day 7-30)
+
+**Diagnose:**
+- Which features do power users use that casual users don't?
+- What's the engagement cliff (when do users stop exploring)?
+
+**Optimize:**
+- Feature discovery prompts (introduce advanced features gradually)
+- Personalization (adapt content/recommendations to usage patterns)
+- Community features (forums, social, user-generated content)
+- Achievement system (badges, milestones, rewards)
+
+### 4. Long-term Retention (Day 30+)
+
+**Diagnose:**
+- What causes late-stage churn?
+- Are there seasonal patterns?
+- Do updates improve or hurt retention?
+
+**Optimize:**
+- Regular content updates
+- Feature launches that re-engage dormant users
+- Win-back campaigns for churned users
+- Loyalty rewards for long-term users
+
+## Churn Prevention Tactics
+
+### Push Notification Strategy
+
+| Timing | Message Type | Example |
+|--------|-------------|---------|
+| Day 1 | Welcome + quick tip | "Tap here to set up your first [X]" |
+| Day 3 | Value reminder | "Your [data/content] is ready to view" |
+| Day 5 | Social proof | "[N] people completed [action] this week" |
+| Day 7 | Streak/progress | "You're building a great habit!" |
+| Day 14 | Feature discovery | "Did you know you can also [feature]?" |
+| Day 30 | Milestone | "One month! Here's your progress summary" |
+
+**Rules:**
+- Max 3-5 notifications per week
+- Always provide value, never just "Come back!"
+- Personalize based on user behavior
+- Allow granular notification preferences
+- A/B test timing and copy
+
+### Win-back Campaigns
+
+For users who haven't opened the app in 7+ days:
+1. **Email** (if you have it) — "We've added [feature] since you last visited"
+2. **Push notification** — "[Specific value] is waiting for you"
+3. **In-app message** (on return) — "Welcome back! Here's what's new"
+
+### Cancellation Flow (Subscriptions)
+
+When a user tries to cancel:
+1. Ask why (multiple choice)
+2. Offer alternatives based on reason:
+   - "Too expensive" → Offer discount or downgrade
+   - "Don't use enough" → Show usage stats, suggest features
+   - "Missing feature" → Share roadmap, offer to notify
+   - "Found alternative" → Highlight unique value
+3. Offer pause instead of cancel
+4. Make it easy to cancel (forced retention backfires)
+
+## Output Format
+
+### Retention Diagnostic
+
+```
+Current State:
+- Day 1: [X]% (benchmark: [Y]%) [above/below]
+- Day 7: [X]% (benchmark: [Y]%) [above/below]
+- Day 30: [X]% (benchmark: [Y]%) [above/below]
+
+Biggest Drop-off: Day [N] to Day [N]
+Estimated Impact: [X]% improvement = [Y] additional monthly users
+```
+
+### Action Plan
+
+**Week 1 (Quick Wins):**
+1. [specific tactic with expected impact]
+2. [specific tactic with expected impact]
+
+**Month 1 (High Impact):**
+1. [specific tactic with expected impact]
+2. [specific tactic with expected impact]
+
+**Quarter 1 (Strategic):**
+1. [specific tactic with expected impact]
+2. [specific tactic with expected impact]
+
+## Related Skills
+
+- `app-analytics` — Set up retention tracking
+- `monetization-strategy` — Retention's impact on revenue
+- `review-management` — Retention issues surface in reviews
+- `app-launch` — First-time user experience