@leejungkiin/awkit 1.7.0 → 1.7.4

package/skills/spec-gate/SKILL.md

@@ -62,12 +62,16 @@ OPTIONAL: TECH-SPEC.md, existing DB schema, NeuralMemory context
 
 ## 🔄 PROCESS (8 Phases)
 
-### Phase 1: Context Gathering (Silent)
+### Phase 1: Context Gathering & Planning Route (Silent)
 - **Kiro check first** → .kiro/specs/design.md → AUTO-PASS Gate 2
+- **Claude Planner check (New):** Invoke `claude-planner` skill to delegate planning to Claude CLI.
+  - If Claude CLI is installed & authenticated: Execute script to create `implementation_plan.md` via Claude Opus.
+  - If Claude CLI is missing/expired: Fall back immediately to planning using the current active model.
 - Fallback: Read BRIEF.md → extract entities, relationships, rules
 - Read .project-identity, TECH-SPEC.md, NeuralMemory
 
 ### Phase 2: Data Model Design
+- Use either the plan generated by Claude (if successful) or model-generated plan.
 - Per entity: Fields, Indexes, Relationships, Constraints
 - Template → `templates/design-templates.md`
 
@@ -121,7 +125,7 @@ always_do:
 TRIGGERED BY: orchestrator (Gate 2 check fail)
 DEPENDS ON: brainstorm-agent output (Gate 1 must pass)
 FEEDS INTO: symphony-enforcer (Gate 3)
-WORKS WITH: nm-memory-sync
+WORKS WITH: nm-memory-sync, claude-planner
 ```
 
 ---

package/skills/symphony-enforcer/SKILL.md

@@ -67,6 +67,14 @@ THREE-PHASE MAPPING (Gate 4 — COMPLEX tasks với UI):
 - Phase C all features done   → report_progress(90%) → Gate 5
 ```
 
+## State Handoff Protocol (Context-Rich Tasks)
+
+```
+BẮT BUỘC lưu context vào task description (`-d`) để tránh quét lại project:
+- Khi tạo task: Kèm `Files:` và `Anchor:` symbol.
+- Khi dừng/pause task: BẮT BUỘC chạy `symphony task update <id> -d "Files: ... | Anchor: ... | State: ..."` để lưu state hiện tại.
+```
+
 ## XML Task Spec trong Implementation Plans
 
 ```xml

package/skills/symphony-enforcer/examples/mindful-stop.md

@@ -26,6 +26,7 @@ AI duy trì state xuyên suốt session:
   iteration_map = {}       # feature_name → count
   tasks_completed = 0      # count tasks done trong session
   last_gate_completed = "" # "phase_c" | "gate_5" | ""
+  goal_mode = false        # true khi /goal, active Codex goal, hoặc user nói rõ "goal mode"
 ```
 
 ---
@@ -91,6 +92,7 @@ Khi nhận request chứa trigger keyword:
 2. `last_gate_completed` = "phase_c" hoặc "gate_5"
 
 ```
+IF goal_mode → SKIP REST STOP (note ngắn, tiếp tục goal)
 IF NOT mindful_enabled OR NOT milestone_rest → SKIP (TP4 chạy như cũ)
 
 Khi trigger:

package/skills/symphony-enforcer/examples/three-phase.md

@@ -11,6 +11,7 @@ AI PHẢI duy trì trạng thái phase hiện tại xuyên suốt Gate 4:
 current_phase = "A" | "B" | "C" | "none"
 phase_b_confirmed = false | true
 checkpoint_count = 0
+goal_mode = true | false
 ```
 
 ## Auto-Detection: Khi nào kích hoạt Three-Phase?
@@ -31,6 +32,14 @@ Nếu CẢ HAI điều kiện thỏa:
    → Hiển thị Phase Announcement Block
 ```
 
+## Goal Mode Override
+
+Khi `goal_mode = true` (`/goal`, active Codex goal, hoặc user nói rõ "goal mode"):
+- Three-Phase vẫn chạy, nhưng checkpoint KHÔNG được đặt `BlockedOnUser=true`.
+- Phase B tự verify bằng best-effort visual/build checks rồi chuyển Phase C.
+- Phase C checkpoint được batch/tự verify; chỉ dừng nếu safety, destructive action, data-loss risk, hoặc blocker thật sự.
+- AI PHẢI ghi assumption ngắn vào progress/task state trước khi đi tiếp.
+
 ## Phase Announcement Block (BẮT BUỘC)
 
 Khi kích hoạt Three-Phase, AI PHẢI hiển thị:
@@ -65,6 +74,12 @@ auto_triggers:
     signal: Tất cả [UI] tasks đã done
     action: |
       - ⛔ TRIGGER TP1.7 (Checkpoint)
+      - NẾU goal_mode=true:
+        + Tự verify best-effort (build/render/screenshot nếu khả dụng).
+        + Ghi assumption vào task state.
+        + TỰ ĐỘNG CHUYỂN SANG PHASE C (BlockedOnUser=false).
+        + KHÔNG chờ "APPROVE UI".
+        + Bỏ qua các bước manual bên dưới.
       - Đọc `.project-identity` -> `automation.autoQA`
       - NẾU `true` (Autonomous Dev-QA Loop): 
         + Tự start App / render ngầm Component.
@@ -106,6 +121,7 @@ auto_triggers:
   - Bỏ qua TP1.7
   - Chạy Auto-verification khi `autoVerification: false`
   - Chờ user test thủ công khi `autoVerification: true`
+  - Goal mode mà dừng chờ approval ở Phase B/C
 
 ✅ BẮT BUỘC:
   - Luôn announce phase transition rõ ràng

package/skills/symphony-enforcer/examples/trigger-points.md

@@ -81,6 +81,7 @@ File patterns:
 ## TP1.7: Flexible Checkpoint (Manual vs Auto)
 
 **Cấu hình Mode Verification:**
+- Goal mode (`/goal`, active Codex goal, hoặc user nói rõ "goal mode") → checkpoint không chặn. AI tự verify/batch test, ghi assumption, rồi đi tiếp (BlockedOnUser=false).
 - `{"autoVerification": true}` → **Auto Device Checkpoint (ADC)**: Dùng Maestro tự build & chụp screenshot. Tiến thẳng (BlockedOnUser=false).
 - `{"autoVerification": false}` (hoặc không khai báo) → **Manual Checkpoint**: Dừng chờ user test (BlockedOnUser=true). **MẶC ĐỊNH an toàn**.
 
@@ -91,7 +92,12 @@ File patterns:
 **Action (Tùy theo Mode):**
 ```
 1. Report progress trước: symphony_report_progress(current_task, progress)
-2. Kiểm tra cờ `autoVerification` trong .project-identity.
+2. Nếu goal mode đang bật:
+   - Announce ngắn: "Goal mode: checkpoint tự verify, tiếp tục."
+   - Chạy best-effort verification phù hợp.
+   - Ghi assumption/risk vào task state.
+   - Continue với BlockedOnUser=false.
+3. Nếu không ở goal mode, kiểm tra cờ `autoVerification` trong .project-identity.
 
 === TRƯỜNG HỢP 1: autoVerification = false (Default Manual) ===
    - Announce "🧪 MANUAL USER TEST CHECKPOINT #{N}"

package/skills/unity-game-development/SKILL.md

@@ -0,0 +1,231 @@
+---
+name: unity-game-development
+description: "Expert Unity game development instructions covering MonoBehaviour caching, ScriptableObjects architecture, memory/performance optimizations (no Update instantiations/Find), object pooling, physics FixedUpdate coordination, editor script isolation, and unity-mcp integrations. Keywords: Unity, C#, MonoBehaviour, ScriptableObject, physics, fixedUpdate, compiler directives, object pooling, mobile build, performance profiling."
+version: 1.0.0
+trigger: conditional
+activation_keywords:
+  - "Unity"
+  - "MonoBehaviour"
+  - "ScriptableObject"
+  - "unity game"
+  - "C#"
+  - "FixedUpdate"
+  - "object pool"
+---
+
+# Unity Game Development Skill
+
+Expert pair-programming rules and standards for building scalable, high-performance Unity games.
+
+## Core Workflow
+
+1. **Analyze Requirements** — Identify genre, target platform (mobile, console, web), target performance (30/60/120 FPS), and multiplayer requirements.
+2. **Design Architecture** — Structure component relations, separate pure data configs (ScriptableObjects) from runtime execution (MonoBehaviours), and plan physics layer masks.
+3. **Implement** — Build features using optimized C# patterns, caching components in `Awake()`, and managing scene hierarchies cleanly.
+4. **Optimize** — Profile script CPU execution time and GPU rendering overhead.
+   - ⚠️ **Validation Checkpoint**: Run Unity Profiler (CPU Usage & GPU Usage). Verify frame times stay stably $\le$ 16.6ms (60 FPS) on target hardware. Eliminate GC Allocations in hot paths.
+5. **Test** — Validate multiplayer sync (latency/desync) and ensure memory footprints do not cause out-of-memory crashes on target platforms.
+
+---
+
+## 📐 Coding Conventions & C# Standards
+
+- **Naming Styles**:
+  - `PascalCase` for classes, methods, properties, and public fields.
+  - `camelCase` for local variables and method parameters.
+  - Private class fields MUST be prefixed with `m_` (e.g., `m_Speed`) or `_` (e.g., `_speed`) for immediate visibility.
+- **Access Modifiers**:
+  - Keep fields `private` by default. Use `[SerializeField]` to expose private fields to the Unity Inspector instead of making them `public`.
+- **Component Caching**:
+  - Always cache components (e.g., `Rigidbody`, `Collider`, `Animator`) in `Awake()` or `Start()`. NEVER call `GetComponent<T>()` in `Update()`, `FixedUpdate()`, or `LateUpdate()`.
+
+---
+
+## 🛠️ MonoBehaviour Caching & Lifecycle Template
+
+```csharp
+using UnityEngine;
+
+[RequireComponent(typeof(Rigidbody))]
+public class PlayerController : MonoBehaviour
+{
+    [Header("Movement Settings")]
+    [SerializeField] private float m_MoveSpeed = 5f;
+    [SerializeField] private Transform m_Target;
+
+    // Cached references
+    private Rigidbody m_Rb;
+    private Animator m_Animator;
+
+    private void Awake()
+    {
+        // Cache references immediately
+        m_Rb = GetComponent<Rigidbody>();
+        m_Animator = GetComponent<Animator>();
+    }
+
+    private void Start()
+    {
+        // Initialize targets or lookups
+        if (m_Target == null)
+        {
+            var playerObj = GameObject.FindGameObjectWithTag("Player");
+            if (playerObj != null)
+            {
+                m_Target = playerObj.transform;
+            }
+        }
+    }
+
+    private void FixedUpdate()
+    {
+        if (m_Target == null) return;
+
+        // Perform physics manipulation in FixedUpdate using fixedDeltaTime
+        Vector3 direction = (m_Target.position - transform.position).normalized;
+        m_Rb.MovePosition(transform.position + direction * m_MoveSpeed * Time.fixedDeltaTime);
+    }
+
+    private void OnDisable()
+    {
+        // Clean up coroutines, listeners, and event subscriptions to avoid memory leaks
+        StopAllCoroutines();
+    }
+}
+```
+
+---
+
+## 📦 Data-Driven Design with ScriptableObjects
+
+Separate logic from static configuration data. Use `ScriptableObject` instances (`.asset` files) to store config data.
+
+```csharp
+// Configuration definition
+[CreateAssetMenu(fileName = "WeaponConfig", menuName = "Configs/Weapon")]
+public class WeaponConfig : ScriptableObject
+{
+    public string weaponName;
+    public int baseDamage;
+    public float fireRate;
+    public GameObject projectilePrefab;
+    public AudioClip fireSFX;
+}
+
+// MonoBehaviour execution
+public class WeaponManager : MonoBehaviour
+{
+    [SerializeField] private WeaponConfig m_Config;
+    private float m_NextFireTime;
+
+    public void Fire()
+    {
+        if (Time.time < m_NextFireTime) return;
+
+        // Execute behavior using config data
+        Instantiate(m_Config.projectilePrefab, transform.position, transform.rotation);
+        m_NextFireTime = Time.time + (1f / m_Config.fireRate);
+    }
+}
+```
+
+---
+
+## ⚡ Memory & Performance Optimization
+
+- **Zero Instantiations in Game Loop**:
+  - Never call `Instantiate()`, `Destroy()`, `new List()`, or allocate arrays inside `Update()` or `FixedUpdate()`. Use **Object Pools**.
+- **Avoid Raycast Allocation**:
+  - Use `Physics.RaycastNonAlloc` instead of `Physics.RaycastAll` to avoid garbage collection pressure.
+- **CompareTag Method**:
+  - Use `other.CompareTag("Player")` instead of `other.tag == "Player"`. The latter allocates string memory under the hood.
+
+### Object Pooling Pattern
+
+Use Unity's built-in `UnityEngine.Pool` or a simple custom implementation:
+
+```csharp
+using System.Collections.Generic;
+using UnityEngine;
+
+public class ProjectilePool : MonoBehaviour
+{
+    [SerializeField] private GameObject m_Prefab;
+    [SerializeField] private int m_InitialSize = 20;
+
+    private Queue<GameObject> m_Pool = new Queue<GameObject>();
+
+    private void Start()
+    {
+        for (int i = 0; i < m_InitialSize; i++)
+        {
+            GameObject obj = Instantiate(m_Prefab, transform);
+            obj.SetActive(false);
+            m_Pool.Enqueue(obj);
+        }
+    }
+
+    public GameObject Get()
+    {
+        if (m_Pool.Count > 0)
+        {
+            GameObject obj = m_Pool.Dequeue();
+            obj.SetActive(true);
+            return obj;
+        }
+        return Instantiate(m_Prefab); // Fallback expansion
+    }
+
+    public void ReturnToPool(GameObject obj)
+    {
+        obj.SetActive(false);
+        m_Pool.Enqueue(obj);
+    }
+}
+```
+
+---
+
+## 🔒 Editor Scripting & Conditional Compilation
+
+Always isolate Editor-only scripts (e.g. Inspector customizations) to prevent build compile failures:
+- Place Editor scripts inside a directory named `Editor/`.
+- Or wrap Editor-only code blocks using compiler directives:
+```csharp
+#if UNITY_EDITOR
+using UnityEditor;
+#endif
+
+public class CustomTool : MonoBehaviour
+{
+    public void ResetProgress()
+    {
+        // ...
+    }
+}
+
+#if UNITY_EDITOR
+[CustomEditor(typeof(CustomTool))]
+public class CustomToolEditor : Editor
+{
+    public override void OnInspectorGUI()
+    {
+        DrawDefaultInspector();
+        CustomTool tool = (CustomTool)target;
+        if (GUILayout.Button("Reset Progress"))
+        {
+            tool.ResetProgress();
+        }
+    }
+}
+#endif
+```
+
+---
+
+## 🔌 Unity MCP Integration (Advanced)
+
+To inspect scenes, nodes, and modify properties programmatically inside the editor:
+1. Ensure the Unity Editor is running the [Unity MCP Server](https://github.com/justinpbarnett/unity-mcp).
+2. Configure Cursor/Claude `mcp_config.json` with the relay connection.
+3. Use the MCP tools prefixed with `mcp__unity__` to query the active hierarchy.

package/skills/verification-gate/SKILL.md

@@ -33,7 +33,9 @@ BEFORE claiming any status or expressing satisfaction:
    - If NO: State actual status with evidence
    - If YES: State claim WITH evidence
 5. ONLY THEN: Make the claim
-6. AUTO-COMMIT: Build 0 errors → git add → git commit → git push (non-force)
+6. AUTO-COMMIT (TÙY CHỌN — Mặc định TẮT):
+   - Chỉ tự động commit nếu `automation.git.autoCommit: true` được bật trong `.project-identity`.
+   - Nếu được bật: Build 0 errors → git add → git commit → git push (non-force)
    - Do NOT ask user permission for regular commits
    - Use conventional commit message (fix:/feat:/refactor:)
    - If push fails → git pull --rebase && git push (retry once)
@@ -99,7 +101,7 @@ If you catch yourself thinking any of these, STOP and run verification:
 
 **Build:**
 ```
-✅ [Run build] → [See: BUILD SUCCEEDED] → auto git add+commit+push → "Build passes, committed & pushed"
+✅ [Run build] → [See: BUILD SUCCEEDED] → (nếu bật auto git) auto git add+commit+push → "Build passes, committed & pushed"
 ❌ "Linter passed so build is fine"
 ❌ Build succeeded but forgot to commit
 ```

package/skills/video-edit/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: video-edit
+description: "Biên tập video dọc (9:16) từ EDL JSON: cắt shot, nhạc nền, captions PNG (không dùng drawtext), decor overlays, guardrail chống timeline vô hạn."
+version: 0.1.0
+trigger: conditional
+activation_keywords:
+  - "biên tập video"
+  - "render video"
+  - "dựng video"
+  - "caption video"
+  - "edit video"
+---
+
+## Usage
+
+```bash
+python ~/.gemini/antigravity/skills/video-edit/scripts/video_edit.py render \
+  --edl <path-to-edl.json> \
+  --project-root <repo-root> \
+  --out <output.mp4> \
+  --preset cinematic \
+  --crf 23 \
+  --badge tip --badge-duration 3
+```
+
+## Requirements
+
+- ffmpeg + ffprobe on PATH
+- Python + Pillow (PIL)
+- Fonts in `<repo-root>/assets/fonts/` (fallback to macOS Arial)
+- Optional overlays in `<repo-root>/assets/overlays/`
+
+## Notes
+
+- Không dùng `drawtext` để tránh lỗi thiếu filter trên một số bản ffmpeg.
+- Guardrails: mỗi PNG overlay input được giới hạn `-t`, và output bị `trim` + `-shortest` để không bao giờ kéo dài vô hạn.