@leejungkiin/awkit 1.1.6 → 1.1.7

package/skills/crash-analytics/SKILL.md

@@ -0,0 +1,181 @@
+---
+name: crash-analytics
+description: When the user wants to monitor, triage, or reduce their app's crash rate — including setting up Crashlytics, prioritizing which crashes to fix first, interpreting crash data, and understanding how crashes affect App Store ranking. Use when the user mentions "crash", "crashlytics", "crash rate", "ANR", "app not responding", "crash-free sessions", "crash-free users", "symbolication", "stability", "firebase crashes", "app crashing", or "crash report". For overall analytics setup, see app-analytics.
+metadata:
+  version: 1.0.0
+---
+
+# Crash Analytics
+
+You help triage, prioritize, and reduce app crashes — and understand how crash rate affects App Store discoverability and ratings.
+
+## Why Crash Rate Is an ASO Signal
+
+- **App Store ranking** — Apple's algorithm penalizes apps with high crash rates
+- **App Store featuring** — High crash rate disqualifies editorial consideration
+- **Ratings** — Crashes are the #1 cause of 1-star reviews
+- **Retention** — A crash in the first session destroys Day 1 retention
+
+**Target:** crash-free sessions > 99.5% | crash-free users > 99%
+
+## Tools
+
+| Tool | What it provides | Setup |
+|------|-----------------|-------|
+| **Firebase Crashlytics** | Real-time crashes, ANRs, symbolicated stack traces | Add `FirebaseCrashlytics` pod/SPM package |
+| **App Store Connect** | Crash rate trend, crashes per session | Built-in, no code needed |
+| **Xcode Organizer** | Aggregated crash logs from TestFlight + App Store | Xcode → Window → Organizer → Crashes |
+| **MetricKit** | On-device diagnostics, hang rate, launch time | iOS 13+, automatic |
+
+**Recommended:** Crashlytics (real-time alerts + search) + App Store Connect (trend validation)
+
+## Crashlytics Setup
+
+### iOS (Swift)
+
+```swift
+// AppDelegate or @main App struct
+import FirebaseCore
+import FirebaseCrashlytics
+
+@main
+struct MyApp: App {
+    init() {
+        FirebaseApp.configure()
+        // Crashlytics is auto-initialized
+    }
+}
+```
+
+### Non-fatal errors (track without crashing)
+
+```swift
+// Log a non-fatal error
+Crashlytics.crashlytics().record(error: error)
+
+// Log a custom key for debugging context
+Crashlytics.crashlytics().setCustomValue(userId, forKey: "user_id")
+Crashlytics.crashlytics().setCustomValue(screenName, forKey: "current_screen")
+```
+
+### Android (Kotlin)
+
+```kotlin
+// build.gradle (app)
+implementation("com.google.firebase:firebase-crashlytics:18.x.x")
+
+// No additional code needed — auto-captures unhandled exceptions
+// For non-fatal:
+FirebaseCrashlytics.getInstance().recordException(throwable)
+```
+
+## Triage Framework
+
+Not all crashes are equal. Prioritize by impact:
+
+**Priority Score = Crash Frequency × Affected Users × User Segment Weight**
+
+| Priority | Criteria | Response time |
+|----------|---------|---------------|
+| P0 — Critical | Crashes on launch / checkout / core feature; >1% of sessions | Fix today |
+| P1 — High | Crashes in common flows; >0.1% of sessions | Fix this release |
+| P2 — Medium | Edge case crashes; <0.1% of sessions | Fix next release |
+| P3 — Low | Rare, non-blocking crashes; <0.01% of sessions | Backlog |
+
+### Crashlytics Dashboard Triage
+
+1. Sort by **"Impact"** (unique users affected), not frequency
+2. Group: `onboarding`, `checkout`, `core feature`, `background`, `launch`
+3. Assign P0/P1 to the top 3–5 issues
+4. Set a **velocity alert** in Crashlytics for any issue affecting >0.5% of users
+
+## Reading a Crash Report
+
+```
+Fatal Exception: com.example.NullPointerException
+  at com.example.UserProfileVC.loadData:87
+  at com.example.HomeVC.viewDidLoad:45
+
+Keys:
+  user_id: 12345
+  current_screen: "home"
+  app_version: "2.3.1"
+  os_version: "iOS 17.3"
+```
+
+**Steps to debug:**
+1. Open the file and line in Xcode (`UserProfileVC.swift:87`)
+2. Check what can be nil at that point
+3. Reproduce with the user context (OS version, device, screen)
+4. Write a failing test before fixing
+
+## Symbolication
+
+Crashlytics auto-symbolicates if you upload dSYMs. If you see unsymbolicated traces:
+
+```bash
+# Manually upload dSYMs
+./Pods/FirebaseCrashlytics/upload-symbols -gsp GoogleService-Info.plist -p ios MyApp.app.dSYM
+```
+
+For Bitcode-enabled builds, download dSYMs from App Store Connect → Activity → Build → dSYMs.
+
+## App Store Connect Crash Data
+
+- **App Store Connect → App Analytics → Crashes** — Crash rate trend per version
+- Compare crash rate before and after each release
+- A spike on a specific version = regression in that release
+
+**Crash rate formula:** Crashes / Sessions × 100
+
+## Release Strategy to Minimize Blast Radius
+
+Use phased releases to catch crashes before full rollout:
+
+**iOS:** App Store Connect → Version → Phased Release (7-day rollout: 1% → 2% → 5% → 10% → 20% → 50% → 100%)
+
+**Android:** Play Console → Production → Managed publishing → Rollout percentage
+
+**Rule:** Monitor Crashlytics for 24 hours at each phase. If crash rate increases >0.2%, pause rollout.
+
+## Responding to Crash-Driven 1-Star Reviews
+
+1. Identify the app version where crash-related 1-stars appeared
+2. Fix the crash
+3. Reply to each crash-related review: "Fixed in version X.X — please update"
+4. After update ships, use `rating-prompt-strategy` to recover rating
+
+## Output Format
+
+### Crash Audit Report
+
+```
+Stability Report — [App Name] v[version] ([period])
+
+Crash-free sessions: [X]%  (target: >99.5%)
+Crash-free users:    [X]%  (target: >99%)
+Top crash issues:
+
+P0 Issues (fix immediately):
+  #1 [Exception type] — [X] users, [X]% of sessions
+     File: [filename:line]
+     Cause: [hypothesis]
+     Fix: [specific action]
+
+P1 Issues (this release):
+  #2 [Exception type] — [X] users, [X]% of sessions
+     ...
+
+Action Plan:
+  Today:     Fix P0 issue #1 → release hotfix
+  This week: Fix P1 issues #2, #3 → include in v[X.X]
+  Monitoring: Set velocity alert at 0.5% session threshold
+```
+
+## Related Skills
+
+- `app-analytics` — Full analytics stack; Crashlytics is one piece
+- `rating-prompt-strategy` — Recover rating after fixing crash-driven 1-stars
+- `review-management` — Respond to crash-related reviews
+- `retention-optimization` — Crashes on Day 1 destroy retention metrics
+- `app-store-featured` — Crash rate > 2% disqualifies editorial featuring

package/skills/in-app-events/SKILL.md

@@ -0,0 +1,176 @@
+---
+name: in-app-events
+description: When the user wants to create, plan, or optimize App Store In-App Events — the event cards that appear on the Today tab, search results, and your product page. Use when the user mentions "in-app event", "App Store event", "event card", "Today tab", "live event", "challenge", "game event", "seasonal event card", or wants visibility beyond organic search. For general ASO, see aso-audit. For seasonal keyword strategy, see seasonal-aso.
+metadata:
+  version: 1.0.0
+---
+
+# In-App Events
+
+You help the user plan, write, and optimize **App Store In-App Events** — event cards that surface in search, the Today tab, and the product page, driving installs and re-engagement without paid media.
+
+## What In-App Events Are
+
+In-App Events are time-limited content cards on the App Store. They appear:
+- **Today tab** (editorial + algorithmic)
+- **Search results** (alongside app results)
+- **Your product page**
+- **Personalized recommendations** (for lapsed users)
+
+**Key advantage:** Existing users who haven't opened your app recently are notified of events. Non-users see them as discovery.
+
+## Event Types
+
+| Type | Best For | Example |
+|------|----------|---------|
+| **Challenge** | User-generated competition | "30-Day Streak Challenge" |
+| **Competition** | Ranked or scored contest | "Weekly High Score Leaderboard" |
+| **Live Event** | Real-time activity | "Live Q&A with Experts" |
+| **Major Update** | Significant new feature | "Introducing AI Coach" |
+| **Premiere** | First-time content launch | "New Series: Morning Routines" |
+| **Special Event** | Seasonal or themed moment | "Holiday Collection Unlocked" |
+
+## Event Card Specs
+
+| Field | Limit | Notes |
+|-------|-------|-------|
+| **Event name** | 30 chars | Appears prominently — keyword-conscious |
+| **Short description** | 50 chars | Below the name on cards |
+| **Long description** | 120 chars | Shown in expanded event view |
+| **Event card image** | 2160×1080px | 2:1 ratio, PNG/JPG, no text required |
+| **Badge** | — | Chosen from the 6 type badges above |
+| **Duration** | Up to 31 days | Start and end time required |
+
+Up to **10 events** can be live or scheduled at a time.
+
+## Planning Workflow
+
+### Step 1 — Event Idea Selection
+
+1. Check for `app-marketing-context.md`
+2. Evaluate event type based on app category:
+
+| App Type | Best Event Types |
+|----------|----------------|
+| Games | Challenge, Competition, Major Update |
+| Fitness | Challenge, Live Event, Major Update |
+| Productivity | Major Update, Premiere |
+| Social / Community | Live Event, Challenge |
+| Streaming / Content | Premiere, Special Event |
+| Utility | Major Update, Special Event |
+
+3. Identify the primary goal:
+   - **Re-engagement** → Use notification-triggering events (any type)
+   - **New user acquisition** → Focus on Today tab visibility (Challenge or Competition)
+   - **Feature launch** → Major Update type
+
+### Step 2 — Write Event Copy
+
+**Event name (30 chars) — rules:**
+- Lead with the user benefit or action, not your app name
+- Include relevant keywords where natural
+- ✅ "30-Day Habit Challenge" | ❌ "AppName Challenge 2026"
+
+**Short description (50 chars):**
+- Answer "what's in it for me?" in one line
+- ✅ "Build a streak and win exclusive rewards"
+
+**Long description (120 chars):**
+- Expand on the short description: what, when, and why to join
+- ✅ "Join our 30-day challenge. Complete daily habits, hit your streak, and unlock your achievement badge."
+
+### Step 3 — Event Card Image
+
+Spec: 2160×1080px, 2:1 ratio
+
+**Best practices:**
+- No text needed (name/description appear as overlay) — but a short tagline is allowed
+- High contrast, bold visual that works at small thumbnail size
+- Show the outcome or reward, not just the app UI
+- Test thumbnail at 390×195px to verify legibility
+
+### Step 4 — Submit in App Store Connect
+
+1. App Store Connect → Your App → In-App Events → `+`
+2. Fill all required fields + upload image
+3. Submit for review (typically 24–48 hours)
+4. Schedule start/end times
+
+**Submit 3–5 days before** the desired start date to account for review time.
+
+## Optimization Tips
+
+### Maximize Today Tab Placement
+
+Apple's algorithm favors events that are:
+- **Timely** — tied to real-world moments (holidays, trends, app anniversaries)
+- **High quality** — polished images, complete descriptions
+- **Engaging** — event types that drive sessions (challenges > updates)
+- **Consistent** — apps that run regular events get better recurring placement
+
+**Run at least one event per month** to maintain algorithmic eligibility.
+
+### Keyword Visibility in Search
+
+Event names and short descriptions are **indexed by the App Store search algorithm**.
+
+- Include 1–2 target keywords in the event name naturally
+- The short description can reinforce secondary keywords
+- Use `keyword-research` skill to validate which terms to include
+
+### Re-engagement Notification
+
+Users who have downloaded your app but haven't opened it recently receive a push notification for your event automatically — no opt-in required. This is the highest-value feature of In-App Events.
+
+**Make the event name the notification subject line** — write it to be compelling as a standalone message.
+
+## Output Format
+
+### Event Brief
+
+```
+📅 Event: [Name — 30 chars]
+   Type:  [Badge type]
+   Dates: [Start] → [End]
+
+Copy:
+  Short:  [50 chars]
+  Long:   [120 chars]
+
+Image direction:
+  Visual: [describe the scene/concept]
+  Style:  [photography / illustration / abstract]
+  Key element: [the reward, the action, the outcome]
+
+Goals:
+  Primary: [re-engagement / acquisition / feature launch]
+  KPIs: [sessions spike, downloads, event page views]
+
+Submit by: [date — 4 days before start]
+```
+
+### Event Calendar (monthly)
+
+```
+Week 1:  [Event name] — [type] — [dates]
+Week 2:  [No event / buffer]
+Week 3:  [Event name] — [type] — [dates]
+Week 4:  [Event name] — [type] — [dates]
+```
+
+## Common Mistakes
+
+| Mistake | Fix |
+|---------|-----|
+| App name in event name | Lead with the user benefit |
+| Generic image (screenshot of UI) | Show the reward/outcome visually |
+| Events shorter than 7 days | Minimum 7 days for Today tab consideration |
+| Submitting day-of | Submit 4–5 days early for review |
+| No recurring schedule | Run 1+ events/month for sustained placement |
+
+## Related Skills
+
+- `seasonal-aso` — Align event timing with keyword seasonal peaks
+- `screenshot-optimization` — Apply same visual best practices to event images
+- `app-store-featured` — Events increase editorial feature eligibility
+- `retention-optimization` — Track re-engagement lift from events

package/skills/keyword-research/SKILL.md

@@ -0,0 +1,141 @@
+---
+name: keyword-research
+description: When the user wants to discover, evaluate, or prioritize App Store keywords. Also use when the user mentions "keyword research", "find keywords", "search volume", "keyword difficulty", "keyword ideas", or "what keywords should I target". For implementing keywords into metadata, see metadata-optimization. For auditing current keyword performance, see aso-audit.
+metadata:
+  version: 1.0.0
+---
+
+# Keyword Research
+
+You are an expert ASO keyword researcher with deep knowledge of App Store search behavior, keyword indexing, and ranking algorithms. Your goal is to help the user discover high-value keywords and build a prioritized keyword strategy.
+
+## Initial Assessment
+
+1. Check for `app-marketing-context.md` — read it for app context, competitors, and goals
+2. Ask for the **App ID** (to understand current rankings)
+3. Ask for **target country** (default: US)
+4. Ask for **seed keywords** — 3-5 words that describe the app's core function
+5. Ask about **intent**: Are they optimizing for downloads, revenue, or brand awareness?
+
+## Research Process
+
+### Phase 1: Seed Expansion
+
+Start with the user's seed keywords and expand using multiple methods:
+
+**Apple Search Suggestions**
+- Use each seed keyword to get autocomplete suggestions
+- Try variations: "[keyword] app", "[keyword] for [audience]", "best [keyword]"
+- Note long-tail suggestions — these often have lower competition
+
+**Competitor Keywords**
+- Pull keyword rankings for top 3-5 competitors
+- Identify keywords competitors rank for that the user doesn't
+- Look for keywords where competitors rank poorly (opportunity)
+
+**Category Analysis**
+- What keywords do top apps in the category target?
+- Are there category-specific terms the user is missing?
+
+**Synonym & Related Terms**
+- Generate synonyms and related terms for each seed keyword
+- Consider how users actually describe the problem (not the solution)
+- Think about misspellings and abbreviations users might search
+
+### Phase 2: Keyword Evaluation
+
+For each keyword candidate, evaluate:
+
+| Signal | What to check | Why it matters |
+|--------|--------------|----------------|
+| **Search Volume** | Volume score (1-100) or traffic estimate | Higher volume = more potential impressions |
+| **Difficulty** | Competition score (1-100) | Lower difficulty = easier to rank |
+| **Relevance** | How closely it matches the app's function | Irrelevant traffic doesn't convert |
+| **Intent** | Is the searcher looking to download? | "how to edit photos" vs "photo editor app" |
+| **Current Rank** | Where the app currently ranks (if at all) | Easier to improve existing rank than start from zero |
+
+### Phase 3: Opportunity Scoring
+
+Calculate an **Opportunity Score** for each keyword:
+
+```
+Opportunity = (Volume × 0.4) + ((100 - Difficulty) × 0.3) + (Relevance × 0.3)
+```
+
+Where:
+- Volume: 1-100 scale
+- Difficulty: 1-100 scale (inverted — lower difficulty = higher score)
+- Relevance: 1-100 scale (manual assessment)
+
+### Phase 4: Keyword Grouping
+
+Group keywords into strategic buckets:
+
+**Primary Keywords (3-5)**
+- Highest opportunity score
+- Must appear in title or subtitle
+- These define your core positioning
+
+**Secondary Keywords (5-10)**
+- Good opportunity but lower priority
+- Target in subtitle and keyword field
+- May rotate based on performance
+
+**Long-tail Keywords (10-20)**
+- Lower volume but very specific intent
+- Fill remaining keyword field space
+- Often easier to rank for
+
+**Aspirational Keywords (3-5)**
+- High volume, high difficulty
+- Long-term targets as the app grows
+- Track but don't sacrifice primary keywords for these
+
+## Output Format
+
+### Keyword Research Report
+
+**Summary:**
+- Total keywords analyzed: [N]
+- High-opportunity keywords found: [N]
+- Estimated total monthly search volume: [N]
+
+**Top Keywords by Opportunity:**
+
+| Keyword | Volume | Difficulty | Relevance | Opportunity | Current Rank | Action |
+|---------|--------|------------|-----------|-------------|--------------|--------|
+| [keyword] | [1-100] | [1-100] | [1-100] | [score] | [rank or —] | Primary |
+
+**Keyword Strategy:**
+
+```
+Title (30 chars):     [primary keyword 1] + [primary keyword 2]
+Subtitle (30 chars):  [secondary keywords]
+Keyword Field (100):  [remaining keywords, comma-separated]
+```
+
+**Competitor Keyword Gap:**
+
+| Keyword | Your Rank | Competitor 1 | Competitor 2 | Competitor 3 | Gap? |
+|---------|-----------|-------------|-------------|-------------|------|
+
+**Recommendations:**
+1. Immediate changes to make
+2. Keywords to start tracking
+3. Content/feature opportunities based on keyword demand
+
+## Tips for the User
+
+- **Don't repeat keywords** across title, subtitle, and keyword field — Apple indexes each field separately
+- **Use singular forms** — Apple automatically indexes both singular and plural
+- **No spaces after commas** in the keyword field — save characters
+- **Avoid "app" and category names** — Apple already knows your category
+- **Update quarterly** — Search trends change with seasons and culture
+- **Track weekly** — Monitor rank changes to measure impact
+
+## Related Skills
+
+- `metadata-optimization` — Implement the keyword strategy into actual metadata
+- `aso-audit` — Broader audit that includes keyword performance
+- `competitor-analysis` — Deep dive into competitor keyword strategies
+- `localization` — Keyword research for international markets

package/skills/localization/SKILL.md

@@ -0,0 +1,165 @@
+---
+name: localization
+description: When the user wants to localize their App Store listing for international markets. Also use when the user mentions "localization", "translate my app", "international markets", "expand to new countries", "localize metadata", or "which countries should I target". For keyword research in specific markets, see keyword-research. For metadata writing, see metadata-optimization.
+metadata:
+  version: 1.0.0
+---
+
+# App Store Localization
+
+You are an expert in App Store internationalization and localization strategy. Your goal is to help the user expand to new markets by localizing their App Store presence effectively.
+
+## Initial Assessment
+
+1. Check for `app-marketing-context.md` — read it for current markets and languages
+2. Ask for the **App ID** (to see current localizations)
+3. Ask: **Is the app itself localized** (UI, content) or just the store listing?
+4. Ask: **Which markets** are they considering?
+5. Ask: **Budget** — professional translation or AI-assisted?
+
+## Market Prioritization
+
+### Tier 1 Markets (highest ROI for most apps)
+
+| Market | Language | App Store Code | Notes |
+|--------|----------|---------------|-------|
+| United States | English | en-US | Largest market |
+| United Kingdom | English | en-GB | Easy win if US is done |
+| Germany | German | de-DE | Largest EU market |
+| Japan | Japanese | ja | High ARPU, competitive |
+| France | French | fr-FR | Large EU market |
+| South Korea | Korean | ko | High smartphone penetration |
+| China | Simplified Chinese | zh-Hans | Massive but complex (needs ICP) |
+| Brazil | Portuguese | pt-BR | Largest LATAM market |
+| Canada | English/French | en-CA/fr-CA | Easy win |
+| Australia | English | en-AU | Easy win |
+
+### Tier 2 Markets (good potential)
+
+Spain (es-ES), Italy (it), Netherlands (nl), Sweden (sv), Russia (ru), Mexico (es-MX), India (en-IN/hi), Indonesia (id), Turkey (tr), Saudi Arabia (ar-SA)
+
+### How to Choose
+
+Evaluate each market on:
+
+| Factor | Weight | How to assess |
+|--------|--------|--------------|
+| Market size | 30% | iPhone user base in country |
+| Competition | 25% | How many localized competitors? |
+| Effort | 20% | Translation complexity, cultural distance |
+| Revenue potential | 15% | ARPU in the market |
+| Strategic fit | 10% | Does your app solve a local need? |
+
+## Localization Checklist
+
+### Metadata Localization
+
+For each target market:
+
+- [ ] **Title** (30 chars) — Localized with market-specific keywords
+- [ ] **Subtitle** (30 chars) — Localized with local keywords
+- [ ] **Keyword field** (100 chars) — Completely new research per market
+- [ ] **Description** (4000 chars) — Translated and culturally adapted
+- [ ] **Promotional text** (170 chars) — Localized for local events/seasons
+- [ ] **What's New** — Translated for each update
+- [ ] **Screenshots** — Text overlays translated, culturally appropriate imagery
+- [ ] **App Preview Video** — Subtitles or localized version
+
+### Critical: Keywords Are NOT Translations
+
+**The biggest localization mistake:** Translating English keywords directly.
+
+Instead:
+1. Run `keyword-research` for each target market separately
+2. Understand how locals search (different terms, different intent)
+3. Use local autocomplete suggestions
+4. Check what local competitors use in their metadata
+
+**Example:**
+- English keyword: "budget tracker"
+- German: "Haushaltsbuch" (household book) — NOT "Budget Tracker"
+- Japanese: "家計簿" (household ledger) — completely different concept
+- Spanish: "control de gastos" (expense control) — different framing
+
+### Cultural Adaptation
+
+| Element | What to check |
+|---------|--------------|
+| Screenshots | Currency symbols, date formats, number formats |
+| Colors | Cultural color associations (red = luck in China, danger in West) |
+| Imagery | Diverse representation, culturally appropriate |
+| Tone | Formal vs informal varies by culture |
+| Features | Highlight features relevant to local needs |
+| Social proof | Use local press, local user counts if possible |
+| Pricing | Local pricing expectations (purchasing power parity) |
+
+## Localization Workflow
+
+### Phase 1: Research (per market)
+
+1. Analyze top 10 apps in your category in the target market
+2. Run keyword research with local seed terms
+3. Identify local competitors and their positioning
+4. Understand local App Store trends
+
+### Phase 2: Translation & Adaptation
+
+**For metadata (title, subtitle, keywords):**
+- Use native speakers with ASO knowledge (not just translators)
+- Provide context: "This is an App Store title, must include [keyword]"
+- Review with keyword data — does the translation include high-volume terms?
+
+**For description:**
+- Professional translation with cultural adaptation
+- Not word-for-word — adapt examples, references, humor
+- Maintain the same persuasive structure
+
+**For screenshots:**
+- Translate text overlays
+- Adjust UI language if app is localized
+- Consider local design preferences
+
+### Phase 3: Launch & Monitor
+
+1. Submit localized metadata
+2. Monitor keyword rankings in each market (weekly)
+3. Track conversion rate by country
+4. Iterate based on performance data
+
+## Output Format
+
+### Localization Plan
+
+For each recommended market:
+
+```
+## [Country] — [Language]
+
+Priority: [High/Medium/Low]
+Estimated effort: [hours/days]
+Expected impact: [download increase estimate]
+
+Keywords (top 10):
+| Keyword | Volume | Difficulty | English equivalent |
+|---------|--------|------------|-------------------|
+
+Metadata:
+- Title: [localized title] ([X]/30 chars)
+- Subtitle: [localized subtitle] ([X]/30 chars)
+- Keywords: [localized keyword field] ([X]/100 chars)
+
+Cultural notes:
+- [specific adaptations needed]
+```
+
+### Market Prioritization Matrix
+
+| Market | Size | Competition | Effort | Revenue | Score | Priority |
+|--------|------|-------------|--------|---------|-------|----------|
+
+## Related Skills
+
+- `keyword-research` — Run for each target market
+- `metadata-optimization` — Write localized metadata
+- `screenshot-optimization` — Localize screenshot designs
+- `competitor-analysis` — Analyze local competitors