@musashishao/agent-kit 1.9.0 → 1.9.1

package/.agent/workflows/dashboard.md

@@ -1,6 +1,7 @@
 ---
 description: Create and view visual project dashboards.
 description_vi: Tạo và xem bảng điều khiển (dashboard) trực quan cho dự án.
+description_en: Create and view visual project dashboards.
 ---
 
 # /dashboard - Visual Project Overview

package/.agent/workflows/debug.md

@@ -1,6 +1,7 @@
 ---
 description: Debug command. Activates DEBUG mode to systematically investigate issues.
 description_vi: Lệnh gỡ lỗi. Kích hoạt chế độ DEBUG để điều tra các vấn đề một cách hệ thống.
+description_en: Debug command. Activates DEBUG mode to systematically investigate issues.
 ---
 
 # /debug - Systematic Problem Investigation
@@ -15,6 +16,19 @@ This command activates DEBUG mode for systematic investigation of issues, errors
 
 ---
 
+## 🔴 VIBES PRE-FLIGHT (MANDATORY)
+
+Before debugging:
+1. **V** - Define success: "Bug fixed when [specific verification passes]"
+2. **I** - Capture intent: What is the *expected* behavior?
+3. **B** - Bifurcation: Is it a code bug, config issue, or environment problem?
+4. **E** - Emergence: Check for side effects from AI-generated code
+5. **S** - Safety: Will the fix introduce new issues?
+
+> ⚠️ **HALT** if symptom is unclear. Use `@[skills/intent-capture]` first.
+
+---
+
 ## Behavior
 
 When `/debug` is triggered:

package/.agent/workflows/deploy.md

@@ -1,6 +1,7 @@
 ---
 description: Production deployment command. Performs pre-flight checks and executes deployment.
 description_vi: Lệnh triển khai sản phẩm. Thực hiện kiểm tra trước khi bay và thực thi triển khai.
+description_en: Production deployment command. Performs pre-flight checks and executes deployment.
 ---
 
 # /deploy - Production Deployment
@@ -27,6 +28,19 @@ This command handles production deployment with pre-flight checks, deployment ex
 
 ---
 
+## 🔴 VIBES PRE-FLIGHT (MANDATORY)
+
+Before deploying:
+1. **V** - Define success: "Health check returns 200 OK on production URL"
+2. **I** - Capture intent: What is being deployed and why?
+3. **B** - Bifurcation: Preview vs Production? Rollback strategy?
+4. **E** - Emergence: Check for unexpected AI-generated changes in bundle
+5. **S** - Safety: All Tier 3 actions require explicit user confirmation
+
+> ⚠️ **HALT** if VIBES check is incomplete.
+
+---
+
 ## Pre-Deployment Checklist
 
 Before any deployment:

package/.agent/workflows/enhance.md

@@ -1,6 +1,7 @@
 ---
 description: Add or update features in an existing application. Used for iterative development.
 description_vi: Thêm hoặc cập nhật tính năng trong ứng dụng hiện có. Được sử dụng cho phát triển lặp.
+description_en: Add or update features in an existing application. Used for iterative development.
 ---
 
 # /enhance - Update Application
@@ -15,6 +16,32 @@ This command adds features or makes updates to existing application.
 
 ### Steps:
 
+## 💾 Git Checkpoint (Safety First)
+
+Before starting work:
+1. [ ] **Clean working tree?** (Run `git status`)
+2. [ ] **On correct branch?** (Not `main` or `master`)
+3. [ ] **Latest pulled?** (Run `git pull`)
+
+> 🔴 **STOP** if git state is dirty. Ask user to commit or stash first.
+
+---
+
+## 🔴 VIBES PRE-FLIGHT (MANDATORY)
+
+Before enhancing:
+1. **V** - Define success: "Feature works and tests pass"
+2. **I** - Capture full intent using `@[skills/intent-capture]`
+3. **B** - Identify bifurcations: Additive vs Breaking change?
+4. **E** - Set scope boundaries to prevent creep
+5. **S** - Confirm impact on existing features
+
+> ⚠️ **HALT** if VIBES check is incomplete.
+
+---
+
+### Steps:
+
 1. **Understand Current State**
    - Load project state with `session_manager.py`
    - Understand existing features, tech stack
@@ -58,8 +85,25 @@ This command adds features or makes updates to existing application.
 
 ---
 
+## 📝 Decision Logging (MANDATORY)
+
+After EVERY clarifying question is answered, log to `.agent/memory/decisions.md`:
+
+```markdown
+## Session: [YYYY-MM-DD HH:MM]
+
+### Q: [Question asked]
+**A:** [User's answer]
+**Impact:** [How this affects implementation]
+```
+
+> 🔴 **NEVER assume. Wait for user confirmation before major changes.**
+
+---
+
 ## Caution
 
 - Get approval for major changes
 - Warn on conflicting requests (e.g., "use Firebase" when project uses PostgreSQL)
 - Commit each change with git
+

package/.agent/workflows/gamekit-init.md

@@ -0,0 +1,177 @@
+---
+description: "Initialize a new game project with Spec Ecosystem structure."
+description_vi: "Khởi tạo dự án game mới với cấu trúc Spec Ecosystem."
+description_en: "Initialize a new game project with Spec Ecosystem structure."
+---
+
+# /gamekit.init - Game Project Initialization
+
+Initialize a new game project with the complete Spec Ecosystem documentation structure.
+
+---
+
+## 🎯 Purpose
+
+Set up the foundation for professional game development:
+1. Create project constitution (principles)
+2. Set up decision log
+3. Prepare folder structure for specs and plans
+
+---
+
+## 📋 Workflow Steps
+
+### Step 1: Gather Project Info
+
+Using `explained-qa` skill, ask:
+
+```markdown
+### ❓ Tên dự án game của bạn?
+
+> 💡 **Giải thích:** Tên này sẽ được dùng để đặt tên file (SPEC-{name}.md, PLAN-{name}.md).
+> Nên dùng tên ngắn, không dấu, dễ nhớ.
+
+**Ví dụ:** dungeon-crawler, space-shooter, idle-farm
+```
+
+### Step 2: Define Constitution
+
+Create `.agent/memory/constitution.md`:
+
+```markdown
+### ❓ Nguyên tắc quan trọng nhất cho dự án này?
+
+> 💡 **Giải thích:** Constitution là "hiến pháp" của dự án - những nguyên tắc AI phải tuân theo.
+> Ví dụ: "Performance is king" hoặc "Mobile-first always".
+
+**Gợi ý:**
+| Option | Mô tả |
+|--------|-------|
+| (A) Performance First | Tối ưu hiệu năng trên hết |
+| (B) Player Experience First | Trải nghiệm người chơi quan trọng nhất |
+| (C) Rapid Iteration | Ship nhanh, fix sau |
+| (D) Quality Over Speed | Làm kỹ, không vội |
+| (E) Custom | Tự định nghĩa |
+```
+
+### Step 3: Create Folder Structure
+
+// turbo
+```bash
+# Create spec ecosystem folders
+mkdir -p docs/specs
+mkdir -p docs/plans
+
+# Ensure memory folder exists
+mkdir -p .agent/memory
+```
+
+### Step 4: Initialize Decision Log
+
+Create `.agent/memory/decisions.md`:
+
+```markdown
+# Decision Log - [Project Name]
+
+> Ghi nhận tất cả quyết định trong quá trình phát triển.
+> AI phải đọc file này TRƯỚC KHI hỏi câu hỏi mới.
+
+---
+
+## Project Initialized: [DATE]
+
+### Project Constitution
+- **Principle:** [From Step 2]
+- **Rationale:** "[User's reasoning]"
+
+---
+
+<!-- New decisions will be appended below -->
+```
+
+### Step 5: Create Constitution File
+
+Create `.agent/memory/constitution.md`:
+
+```markdown
+# Project Constitution - [Project Name]
+
+> Nguyên tắc cốt lõi hướng dẫn mọi quyết định trong dự án.
+
+---
+
+## Core Principle
+
+**[Selected principle from Step 2]**
+
+---
+
+## Implementation Guidelines
+
+Based on the core principle:
+
+| Situation | Decision Rule |
+|-----------|---------------|
+| Performance vs Features | [Based on principle] |
+| Code Quality vs Speed | [Based on principle] |
+| Polish vs Ship | [Based on principle] |
+
+---
+
+## Tech Stack Preferences
+
+(To be filled during /gamekit.spec)
+
+---
+
+*Created: [DATE]*
+*Last Updated: [DATE]*
+```
+
+---
+
+## 📁 Output Structure
+
+After running `/gamekit.init`:
+
+```
+project/
+├── docs/
+│   ├── specs/         # SPEC files go here
+│   └── plans/         # PLAN files go here
+├── .agent/
+│   └── memory/
+│       ├── constitution.md   [NEW]
+│       ├── decisions.md      [NEW]
+│       └── session.json      [Existing]
+```
+
+---
+
+## ⏭️ Next Steps
+
+```markdown
+✅ Project initialized!
+
+**Cấu trúc đã sẵn sàng:**
+- `docs/specs/` - Folder cho specifications
+- `docs/plans/` - Folder cho implementation plans
+- `.agent/memory/decisions.md` - Decision log
+- `.agent/memory/constitution.md` - Project principles
+
+**Bước tiếp theo:**
+1. Chạy `/gamekit-spec` để tạo game specification + GDD
+2. Hoặc `/orchestrate` nếu cần multi-agent từ đầu
+```
+
+---
+
+## 🔗 Related Commands
+
+| Command | When to Use |
+|---------|-------------|
+| `/gamekit-spec` | After init, to create specification + GDD |
+| `/gamekit-plan` | After spec approved |
+| `/gamekit-tasks` | After plan approved |
+| `/gamekit-qa` | After implementation, for playtesting |
+| `/gamekit-launch` | When ready to publish |

package/.agent/workflows/gamekit-launch.md

@@ -0,0 +1,338 @@
+---
+description: "Mobile game launch workflow. From pre-launch to App Store submission and post-launch monitoring."
+description_vi: "Workflow ra mắt game mobile. Từ chuẩn bị trước launch đến submit App Store và theo dõi sau launch."
+description_en: "Mobile game launch workflow. From pre-launch to App Store submission and post-launch monitoring."
+---
+
+# /gamekit-launch - Mobile Game Launch Workflow
+
+Complete workflow to launch your mobile game to iOS App Store and Google Play.
+
+---
+
+## Prerequisites
+
+- Completed, tested game build
+- Apple Developer Account ($99/year)
+- Google Play Developer Account ($25 one-time)
+- App icons, screenshots, descriptions ready
+
+---
+
+## Input
+
+```
+/gamekit-launch [PROJECT_PATH]
+
+Examples:
+/gamekit-launch Projects/MyCatGame
+/gamekit-launch .  (current directory)
+```
+
+---
+
+## Workflow Overview
+
+```
+┌─────────────────────────────────────────────────────────────┐
+│  PHASE 1: PRE-LAUNCH AUDIT       │ unity-mobile-master     │
+├─────────────────────────────────────────────────────────────┤
+│  PHASE 2: STORE ASSETS           │ ai-asset-factory        │
+├─────────────────────────────────────────────────────────────┤
+│  PHASE 3: BUILD & SIGN           │ unity-mobile-master     │
+├─────────────────────────────────────────────────────────────┤
+│  PHASE 4: STORE SUBMISSION       │ devops-engineer         │
+├─────────────────────────────────────────────────────────────┤
+│  PHASE 5: MARKETING PREP         │ marketing-specialist    │
+├─────────────────────────────────────────────────────────────┤
+│  PHASE 6: LAUNCH DAY             │ orchestrator            │
+├─────────────────────────────────────────────────────────────┤
+│  PHASE 7: POST-LAUNCH            │ game-developer          │
+└─────────────────────────────────────────────────────────────┘
+```
+
+---
+
+## Phase 1: Pre-Launch Audit
+
+### Step 1.1: Quality Checklist
+Using `unity-mobile-master`:
+
+- [ ] All core mechanics working
+- [ ] No game-breaking bugs
+- [ ] Tutorial completes properly
+- [ ] Save/load functioning
+- [ ] All IAP products verified
+- [ ] Ads showing correctly
+- [ ] Analytics events firing
+
+### Step 1.2: Performance Check
+// turbo
+```bash
+# Profile build on device
+adb shell dumpsys cpuinfo | grep "game_process"
+```
+
+### Step 1.3: Compliance Review
+- [ ] Privacy policy URL set
+- [ ] Age rating questionnaire completed
+- [ ] COPPA compliance (if targeting kids)
+- [ ] Gacha rates disclosed
+
+---
+
+## Phase 2: Store Assets
+
+### Step 2.1: Generate Screenshots
+Using `ai-asset-factory`:
+
+| Platform | Size | Count |
+|----------|------|-------|
+| iOS (6.5" iPhone) | 1284 × 2778 | 5-10 |
+| iOS (12.9" iPad) | 2048 × 2732 | 5 |
+| Android (Phone) | 1080 × 1920 | 4-8 |
+| Android (Tablet) | 1920 × 1080 | 2-4 |
+
+### Step 2.2: App Icon
+- iOS: 1024 × 1024 (no alpha)
+- Android: 512 × 512 (adaptive icon)
+
+### Step 2.3: Feature Graphic (Android)
+- Size: 1024 × 500
+- Used in Play Store header
+
+### Step 2.4: Store Descriptions
+
+```markdown
+## Short Description (80 chars)
+[Hook that grabs attention]
+
+## Full Description (4000 chars max)
+[Features, gameplay, what makes it special]
+
+## Keywords (iOS only)
+[comma,separated,keywords]
+
+## What's New (for updates)
+[Changelog for this version]
+```
+
+---
+
+## Phase 3: Build & Sign
+
+### Step 3.1: Android Build
+// turbo
+```bash
+# Create release keystore (first time only)
+keytool -genkey -v -keystore release.keystore \
+  -alias mykey -keyalg RSA -keysize 2048 -validity 10000
+```
+
+Using `unity-mobile-master`:
+```
+Player Settings:
+- Scripting Backend: IL2CPP
+- Target Architectures: ARM64
+- Build App Bundle (AAB): Yes
+- Minify: Release
+
+Build:
+- BuildOptions.None (Release)
+- Sign with keystore
+```
+
+// turbo
+```bash
+# Build AAB
+Unity -quit -batchmode -projectPath . \
+  -executeMethod BuildPipeline.BuildAndroidProd
+```
+
+### Step 3.2: iOS Build
+Using `unity-mobile-master`:
+```
+Player Settings:
+- Signing Team ID: YOUR_TEAM_ID
+- Automatic Signing: Yes
+- Scripting Backend: IL2CPP
+```
+
+// turbo
+```bash
+# Build Xcode project
+Unity -quit -batchmode -projectPath . \
+  -executeMethod BuildPipeline.BuildiOS
+
+# Open in Xcode
+open Builds/iOS/Unity-iPhone.xcworkspace
+```
+
+In Xcode:
+1. Select "Generic iOS Device"
+2. Product → Archive
+3. Distribute App → App Store Connect
+4. Upload
+
+---
+
+## Phase 4: Store Submission
+
+### Step 4.1: Google Play Console
+
+1. **Create App**
+   - Enter app details
+   - Select category
+   - Set content rating
+
+2. **Production Track**
+   - Upload AAB
+   - Fill store listing
+   - Submit for review
+
+3. **Review Time**: 1-7 days
+
+### Step 4.2: App Store Connect
+
+1. **Create App**
+   - Enter bundle ID
+   - Select primary language
+   - Add pricing
+
+2. **App Information**
+   - Upload screenshots
+   - Fill metadata
+   - Set availability
+
+3. **Build**
+   - Upload from Xcode
+   - Add What's New
+   - Submit for review
+
+4. **Review Time**: 1-3 days (usually)
+
+---
+
+## Phase 5: Marketing Prep
+
+### Step 5.1: Social Media Assets
+Using `ai-asset-factory`:
+- [ ] Instagram posts (1080 × 1080)
+- [ ] Twitter header (1500 × 500)
+- [ ] YouTube thumbnail (1280 × 720)
+
+### Step 5.2: Press Kit
+Create folder with:
+- [ ] High-res logo
+- [ ] Screenshots (full res)
+- [ ] Game trailer (if available)
+- [ ] Press release text
+- [ ] Developer bio
+
+### Step 5.3: Promotional Copy
+Using `marketing-specialist`:
+- [ ] Launch announcement
+- [ ] Email for mailing list
+- [ ] Reddit/forum posts
+
+---
+
+## Phase 6: Launch Day
+
+### Pre-Launch (Day Before)
+- [ ] Double-check store pages look correct
+- [ ] Prepare social posts
+- [ ] Email list ready
+- [ ] Discord/community notified
+
+### Launch Day Checklist
+- [ ] Release app (manual or scheduled)
+- [ ] Post on social media
+- [ ] Send email blast
+- [ ] Post on relevant subreddits
+- [ ] Submit to game listing sites
+- [ ] Monitor crash reports
+
+### Post-Launch (Same Day)
+- [ ] Respond to first reviews
+- [ ] Monitor analytics dashboard
+- [ ] Check monetization working
+- [ ] Fix any critical bugs immediately
+
+---
+
+## Phase 7: Post-Launch Monitoring
+
+### Daily (First Week)
+Using `game-developer`:
+
+| Metric | Check |
+|--------|-------|
+| **Installs** | Daily new installs |
+| **D1 Retention** | % back next day |
+| **Crashes** | Crashlytics/Firebase |
+| **Revenue** | Daily ARPU |
+| **Reviews** | New ratings |
+
+### Weekly (First Month)
+- [ ] D7 retention review
+- [ ] ARPU/ARPPU analysis
+- [ ] Funnel analysis
+- [ ] User feedback review
+- [ ] Plan first update
+
+### Actions Based on Data
+| Signal | Action |
+|--------|--------|
+| Low D1 | Fix tutorial/onboarding |
+| High crashes | Emergency hotfix |
+| Low conversion | Adjust IAP pricing |
+| Bad reviews | Address common complaints |
+
+---
+
+## Output Checklist
+
+After `/gamekit-launch` completes:
+
+- [ ] Android AAB signed and uploaded
+- [ ] iOS archive uploaded to App Store Connect
+- [ ] Both store listings complete
+- [ ] Screenshots for all device sizes
+- [ ] Privacy policy linked
+- [ ] Marketing assets ready
+- [ ] Analytics dashboard configured
+- [ ] First-week monitoring plan set
+
+---
+
+## Troubleshooting
+
+| Issue | Solution |
+|-------|----------|
+| Google Play rejected | Check policy violation email |
+| Apple rejected | Read Resolution Center |
+| Keystore lost | Cannot update; need new app |
+| Wrong bundle ID | Cannot change; start over |
+| Crashes on release | Check Proguard/IL2CPP stripping |
+
+---
+
+## Post-Submission Timeline
+
+```
+Day 0: Submit
+Day 1-3: Under review
+Day 3-7: Approved (usually)
+Day 7: If rejected, fix and resubmit
+Day 14: Live on both stores
+
+First update: 2-4 weeks after launch
+- Bug fixes
+- Balance adjustments
+- First content update
+```
+
+---
+
+> **Tip:** Soft launch in limited countries first (Canada, Australia) to test monetization before worldwide release.