@leejungkiin/awkit 1.1.6 → 1.1.9

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/gitnexus-intelligence/SKILL.md

@@ -0,0 +1,224 @@
+---
+name: gitnexus-intelligence
+description: >-
+  Code intelligence via GitNexus knowledge graph. Auto-triggers on refactoring,
+  debugging, impact analysis, pre-commit checks, and codebase exploration.
+  Requires project to be indexed with `npx gitnexus analyze`.
+metadata:
+  stage: core
+  version: "1.0"
+  tags: [gitnexus, code-intelligence, knowledge-graph, impact-analysis, refactoring]
+agent: Orchestrator
+trigger: auto
+invocation-type: auto
+priority: 5
+---
+
+# GitNexus Intelligence v1.0 — Code-Aware Agent Skill
+
+> **Purpose:** Cung cấp architectural awareness cho AI agent thông qua knowledge graph.
+> GitNexus index codebase thành graph (symbols, relationships, execution flows),
+> expose qua MCP tools để agent hiểu blast radius TRƯỚC khi edit.
+
+---
+
+## ⚡ Prerequisites
+
+```
+CHECK: Project đã được index chưa?
+  → Tìm thư mục `.gitnexus/` trong project root
+  → Hoặc chạy: `npx gitnexus status`
+
+CHƯA INDEX:
+  → Gợi ý user: "Project chưa được GitNexus index. Chạy `npx gitnexus analyze` trước nhé."
+  → KHÔNG dùng GitNexus tools khi chưa index.
+
+INDEX STALE (tool trả warning):
+  → Cảnh báo: "GitNexus index đã cũ. Chạy `npx gitnexus analyze` để cập nhật."
+```
+
+---
+
+## 🎯 When to Activate
+
+| Trigger | Action |
+|---------|--------|
+| Trước khi edit bất kỳ function/class/method | `gitnexus_impact` → check blast radius |
+| Debug error / trace bug | `gitnexus_query` + `gitnexus_context` |
+| Explore unfamiliar code | `gitnexus_query` → execution flows |
+| Rename symbol | `gitnexus_rename` (dry_run trước) |
+| Trước commit | `gitnexus_detect_changes` |
+| Refactor / extract / split | `gitnexus_context` + `gitnexus_impact` |
+
+---
+
+## 🔧 Tools Reference (7 MCP Tools)
+
+| Tool | Purpose | When |
+|------|---------|------|
+| `gitnexus_query` | Process-grouped hybrid search (BM25 + semantic) | Tìm code theo concept |
+| `gitnexus_context` | 360° symbol view: callers, callees, processes | Deep dive vào 1 symbol |
+| `gitnexus_impact` | Blast radius analysis: d=1/2/3 with confidence | Trước khi sửa code |
+| `gitnexus_detect_changes` | Git-diff impact: mapped to affected processes | Trước commit |
+| `gitnexus_rename` | Multi-file coordinated rename via graph | Rename symbols an toàn |
+| `gitnexus_cypher` | Raw Cypher graph queries | Custom analysis |
+| `gitnexus_list_repos` | List all indexed repositories | Discover repos |
+
+> **Multi-repo:** Khi có nhiều repos indexed, thêm `repo` param: `gitnexus_query({query: "auth", repo: "my-app"})`
+
+---
+
+## 📚 Resources Reference
+
+| Resource | Content | Tokens |
+|----------|---------|--------|
+| `gitnexus://repos` | All indexed repos | ~50 |
+| `gitnexus://repo/{name}/context` | Stats + staleness check | ~150 |
+| `gitnexus://repo/{name}/clusters` | Functional areas + cohesion | ~300 |
+| `gitnexus://repo/{name}/cluster/{name}` | Area members + files | ~500 |
+| `gitnexus://repo/{name}/processes` | All execution flows | ~200 |
+| `gitnexus://repo/{name}/process/{name}` | Step-by-step trace | ~200 |
+| `gitnexus://repo/{name}/schema` | Graph schema for Cypher | ~200 |
+
+---
+
+## 📋 Workflow: Impact Analysis (Trước khi edit)
+
+```
+1. gitnexus_impact({target: "symbolName", direction: "upstream"})
+   → Xem ai depend vào symbol này
+2. READ gitnexus://repo/{name}/processes
+   → Check execution flows bị ảnh hưởng
+3. Đánh giá risk level:
+   - d=1 → WILL BREAK (direct callers) → PHẢI update
+   - d=2 → LIKELY AFFECTED → Nên test
+   - d=3 → MAY NEED TESTING → Test nếu critical path
+4. Report risk cho user trước khi sửa
+```
+
+### Risk Assessment
+
+| Affected | Risk |
+|----------|------|
+| <5 symbols, ít processes | LOW |
+| 5-15 symbols, 2-5 processes | MEDIUM |
+| >15 symbols hoặc nhiều processes | HIGH |
+| Critical path (auth, payments) | CRITICAL |
+
+---
+
+## 📋 Workflow: Debugging
+
+```
+1. gitnexus_query({query: "<error hoặc symptom>"})
+   → Tìm execution flows liên quan
+2. gitnexus_context({name: "<suspect function>"})
+   → Xem callers, callees, process participation
+3. READ gitnexus://repo/{name}/process/{processName}
+   → Trace full execution flow step-by-step
+4. gitnexus_detect_changes({scope: "compare", base_ref: "main"})
+   → Nếu là regression: xem branch đã thay đổi gì
+```
+
+---
+
+## 📋 Workflow: Exploring Code
+
+```
+1. READ gitnexus://repo/{name}/context      → Overview + staleness
+2. READ gitnexus://repo/{name}/clusters     → Functional areas
+3. gitnexus_query({query: "<concept>"})     → Execution flows
+4. gitnexus_context({name: "<symbol>"})     → Deep dive
+5. READ gitnexus://repo/{name}/process/{name} → Full trace
+```
+
+---
+
+## 📋 Workflow: Safe Refactoring
+
+### Rename Symbol
+```
+1. gitnexus_rename({symbol_name: "old", new_name: "new", dry_run: true})
+   → Preview tất cả edits (graph edits = safe, text_search = review)
+2. Review kết quả, đặc biệt text_search edits
+3. gitnexus_rename({..., dry_run: false})   → Apply
+4. gitnexus_detect_changes()                → Verify scope
+```
+
+### Extract / Split
+```
+1. gitnexus_context({name: "target"})       → All incoming/outgoing refs
+2. gitnexus_impact({target, direction: "upstream"}) → External callers
+3. Plan update order: interfaces → implementations → callers → tests
+4. Execute changes
+5. gitnexus_detect_changes()                → Verify affected scope
+```
+
+---
+
+## 📋 Workflow: Pre-Commit Check
+
+```
+1. gitnexus_detect_changes({scope: "staged"})
+   → Changed symbols, affected processes, risk level
+2. Nếu risk HIGH/CRITICAL → Cảnh báo user
+3. Verify tất cả d=1 dependents đã được update
+```
+
+---
+
+## 🚫 Rules
+
+```yaml
+always_do:
+  - PHẢI chạy gitnexus_impact TRƯỚC khi edit bất kỳ symbol nào
+  - PHẢI chạy gitnexus_detect_changes TRƯỚC khi commit
+  - PHẢI cảnh báo user khi risk = HIGH hoặc CRITICAL
+  - Ưu tiên gitnexus_query thay vì grep khi explore code
+  - PHẢI dùng gitnexus_rename (dry_run trước) khi rename
+
+never_do:
+  - KHÔNG edit function/class mà chưa check impact
+  - KHÔNG ignore HIGH/CRITICAL risk warnings
+  - KHÔNG rename bằng find-and-replace → dùng gitnexus_rename
+  - KHÔNG commit mà chưa detect_changes
+  - KHÔNG dùng GitNexus tools khi project chưa index
+```
+
+---
+
+## 🔗 Skill Relationships
+
+```
+WORKS WITH:
+  orchestrator (Gate 4 — search before building, Layer 0)
+  systematic-debugging (bổ sung structural context)
+  code-review (pre-commit blast radius check)
+  verification-gate (detect_changes = evidence)
+
+DOES NOT:
+  Tự index project (user phải chạy npx gitnexus analyze)
+  Sửa code trực tiếp (chỉ cung cấp context)
+```
+
+---
+
+## 🔍 Graph Schema Reference
+
+**Nodes:** File, Function, Class, Interface, Method, Community, Process
+
+**Edges (CodeRelation.type):** CALLS, IMPORTS, EXTENDS, IMPLEMENTS, DEFINES, MEMBER_OF, STEP_IN_PROCESS
+
+```cypher
+-- Find all callers of a function
+MATCH (caller)-[:CodeRelation {type: 'CALLS'}]->(f:Function {name: "myFunc"})
+RETURN caller.name, caller.filePath
+
+-- Find what a function calls
+MATCH (f:Function {name: "myFunc"})-[:CodeRelation {type: 'CALLS'}]->(callee)
+RETURN callee.name, callee.filePath
+```
+
+---
+
+*gitnexus-intelligence v1.0 — Code Intelligence for Antigravity*

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