vibes-plug 2.14.1 → 3.9.0

package/skills/session-memory-manager/SKILL.md

@@ -1,128 +1,129 @@
----
-name: session-memory-manager
-description: "Manages the entire session lifecycle: from context loading (PRD, Tech Stack) at startup, to maintaining project memory during active sessions, and creating ultra-compact checkpoints for handoff. / Mengelola siklus hidup sesi: dari pemuatan konteks awal, pemeliharaan memori proyek, hingga pembuatan checkpoint ringkas untuk handoff."
-author: "Roedy Rustam"
----
-
-# Session Memory Manager
-
-[English](#english) | [Bahasa Indonesia](#bahasa-indonesia)
-
----
-
-<a name="english"></a>
-## English
-
-### Orchestration & Integration
-Connects and orchestrates with relevant domain skills like `brainstorming` and `zero-to-prod-orchestrator` to ensure cohesive execution across the entire session lifecycle.
-
-### Description
-This skill acts as the agent's memory controller. It handles loading project context at session startup, dynamically updating the context map and learning graph during the session, and seamlessly generating ultra-compact handoff checkpoints at session end.
-
-### 1. Session Start (Ingestion)
-Activate this phase IMMEDIATELY on a new session, or when the user says "start session" or "load context". Do not answer primary requests until complete.
-
-**Workflow:**
-1. **Discover Files**: Search the root or `.docs/` using `list_dir`, `grep_search`, or `view_file` for: `CONTEXT_MAP.md`, `LEARNING_GRAPH.md`, `PRD.md`, `BLUEPRINT.md` (or `ARCHITECTURE.md`), and `CHECKPOINT.md`. Also read tech stack identifiers (`TECH_STACK.md`, `package.json`, `go.mod`, etc.).
-2. **Internalize**: Read the contents. Grasp the architectural constraints, user stylistic preferences, hard-learned lessons, and the current goal/milestone.
-3. **Acknowledge**: Briefly confirm to the user what context was loaded, stating the Tech Stack and immediate goal. Proceed to address the actual request.
-
-### 2. Active Session (Run)
-Maintain project memory actively to prevent context exhaustion and hallucination.
-
-**Maintain Context Map (`CONTEXT_MAP.md`)**
-- A highly compressed index (bullet points) of architecture, dependency graphs, and state locations.
-- **Rules**: Do not store full code; use only file paths and 1-sentence responsibilities. Use BM25/`grep_search` before modifying. Append new major components/routes immediately upon creation.
-
-**Maintain Learning Graph (`LEARNING_GRAPH.md`)**
-- **Triggers**: When the user corrects code style, states a strong preference, or after resolving a complex bug. 
-- **Rules**: Physically write lessons to the memory file under categories: User Stylistic Preferences, Hard-Learned Lessons, Architectural Decisions. Do not just promise to remember.
-- **Global Memory**: For issues spanning multiple projects, document the root cause/solution into a global context directory (e.g., `<appDataDir>/knowledge`). Inject this historical context proactively in future tasks.
-
-### 3. Session End (Handoff)
-**Triggers**: Session is very long (>30 messages or >70% context used), major milestone reached, or user says "save checkpoint" / "handoff".
-
-**Action**: Generate an ultra-compact YAML checkpoint block (<200 tokens).
-
-**Checkpoint Format**:
-```yaml
-# CHECKPOINT — [Project Name] — [Date]
-project: "[Name]"
-goal: "[One-line goal]"
-status: "[e.g., 60% — backend API done]"
-stack: "[Tech Stack]"
-last_completed:
-  - "[Most recent task]"
-next_tasks:
-  - "[Immediate next task]"
-blockers: "[Blockers or 'none']"
-key_files:
-  - "[path/to/critical.ts]"
-env_needed: "[List of vars]"
-notes: "[Critical context]"
-```
-
-**Cross-Model Handoff Prompt**:
-Use this universal template when moving across models (Gemini, Claude, GPT):
-```markdown
-## RESUME CONTEXT — [Project Name]
-**Goal**: [One-sentence goal]
-**Current Status**: [Status]
-**Tech Stack**: [Stack]
-**Completed**: [Done items]
-**Next Tasks**: 1. [Task 1] 2. [Task 2]
-**Critical Files to Read First**: [File paths & reasons]
-**Known Constraints**: [Constraints]
-**Do NOT**: [Anti-patterns to avoid]
-Start by reading the critical files, then confirm understanding before proceeding.
-```
-
-**Checkpoint Storage Hierarchy**:
-1. `CHECKPOINT.md` in project root (Primary).
-2. `.agents/CHECKPOINT.md` (Alternative).
-3. Clipboard or Supabase notes table (Cross-device).
-
----
-
-<a name="bahasa-indonesia"></a>
-## Bahasa Indonesia
-
-### Integrasi Orkestrasi
-Terhubung dan mengorkestrasi skill domain seperti `brainstorming` dan `zero-to-prod-orchestrator` untuk memastikan eksekusi kohesif selama siklus hidup sesi.
-
-### Deskripsi
-Skill ini mengatur memori agen: memuat konteks di awal sesi, memperbarui peta proyek dan grafik pembelajaran selama sesi berjalan, dan membuat checkpoint ringkas untuk perpindahan sesi (handoff).
-
-### 1. Awal Sesi (Ingestion)
-Aktifkan SEGERA pada sesi baru, atau saat diminta "mulai sesi" / "muat konteks". 
-
-**Alur Kerja:**
-1. **Temukan File**: Cari di root atau `.docs/`: `CONTEXT_MAP.md`, `LEARNING_GRAPH.md`, `PRD.md`, `BLUEPRINT.md`, `CHECKPOINT.md`, dan file identifikasi tech stack (`package.json`, dsb).
-2. **Pahami**: Baca isinya. Pahami batasan arsitektur, preferensi pengguna, pelajaran penting, dan tujuan/milestone saat ini.
-3. **Konfirmasi**: Beritahu pengguna secara singkat bahwa konteks dimuat, sebutkan Tech Stack dan tujuan langsung, lalu proses permintaan utama.
-
-### 2. Sesi Berjalan (Run)
-Pertahankan memori proyek agar tidak terjadi halusinasi dan hemat token.
-
-**Pelihara Peta Konteks (`CONTEXT_MAP.md`)**
-- Indeks super padat berisi arsitektur, lokasi file penting, dan graf dependensi.
-- **Aturan**: Jangan simpan kode lengkap, hanya path dan tanggung jawab singkat. Gunakan BM25/`grep_search` sebelum mengedit. Tambahkan entri baru saat membuat komponen/rute besar.
-
-**Pelihara Grafik Pembelajaran (`LEARNING_GRAPH.md`)**
-- **Pemicu**: Pengguna mengoreksi gaya koding, menyatakan preferensi, atau setelah mengatasi bug rumit.
-- **Aturan**: Catat langsung ke file dalam kategori: Preferensi Gaya, Pelajaran Berharga, Keputusan Arsitektur. 
-- **Memori Global**: Ekstrak solusi masalah lintas-proyek ke direktori pengetahuan global (`<appDataDir>/knowledge`). Gunakan pengetahuan masa lalu secara proaktif dengan menyebutkannya.
-
-### 3. Akhir Sesi (Handoff)
-**Pemicu**: Pesan > 30, jendela konteks > 70% terpakai, milestone tercapai, atau pengguna berkata "simpan checkpoint".
-
-**Tindakan**: Hasilkan blok YAML super ringkas (<200 token) berisi: `project`, `goal`, `status`, `stack`, `last_completed`, `next_tasks`, `blockers`, `key_files`, `env_needed`, dan `notes`.
-
-**Prompt Handoff Lintas-Model**:
-Gunakan template universal saat berpindah model:
-Berikan konteks proyek (Tujuan, Status, Stack, Tugas Selesai, Tugas Berikutnya), daftar file kritis untuk dibaca pertama kali, batasan, dan apa yang JANGAN dilakukan. Minta konfirmasi sebelum lanjut.
-
-**Hierarki Penyimpanan Checkpoint**:
-1. `CHECKPOINT.md` di root proyek (Utama).
-2. `.agents/CHECKPOINT.md` (Alternatif).
-3. Clipboard / Catatan Supabase (Lintas perangkat).
+---
+name: session-memory-manager
+description: "Manages the entire session lifecycle: from context loading (PRD, Tech Stack) at startup, to maintaining project memory during active sessions, and creating ultra-compact checkpoints for handoff. / Mengelola siklus hidup sesi: dari pemuatan konteks awal, pemeliharaan memori proyek, hingga pembuatan checkpoint ringkas untuk handoff."
+author: "Roedy Rustam"
+version: "3.0.0"
+---
+
+# Session Memory Manager
+
+[English](#english) | [Bahasa Indonesia](#bahasa-indonesia)
+
+---
+
+<a name="english"></a>
+## English
+
+### Orchestration & Integration
+Connects and orchestrates with relevant domain skills like `brainstorming` and `zero-to-prod-orchestrator` to ensure cohesive execution across the entire session lifecycle.
+
+### Description
+This skill acts as the agent's memory controller. It handles loading project context at session startup, dynamically updating the context map and learning graph during the session, and seamlessly generating ultra-compact handoff checkpoints at session end.
+
+### 1. Session Start (Ingestion)
+Activate this phase IMMEDIATELY on a new session, or when the user says "start session" or "load context". Do not answer primary requests until complete.
+
+**Workflow:**
+1. **Discover Files**: Search the root or `.docs/` using `list_dir`, `grep_search`, or `view_file` for: `CONTEXT_MAP.md`, `LEARNING_GRAPH.md`, `PRD.md`, `BLUEPRINT.md` (or `ARCHITECTURE.md`), and `CHECKPOINT.md`. Also read tech stack identifiers (`TECH_STACK.md`, `package.json`, `go.mod`, etc.).
+2. **Internalize**: Read the contents. Grasp the architectural constraints, user stylistic preferences, hard-learned lessons, and the current goal/milestone.
+3. **Acknowledge**: Briefly confirm to the user what context was loaded, stating the Tech Stack and immediate goal. Proceed to address the actual request.
+
+### 2. Active Session (Run)
+Maintain project memory actively to prevent context exhaustion and hallucination.
+
+**Maintain Context Map (`CONTEXT_MAP.md`)**
+- A highly compressed index (bullet points) of architecture, dependency graphs, and state locations.
+- **Rules**: Do not store full code; use only file paths and 1-sentence responsibilities. Use BM25/`grep_search` before modifying. Append new major components/routes immediately upon creation.
+
+**Maintain Learning Graph (`LEARNING_GRAPH.md`)**
+- **Triggers**: When the user corrects code style, states a strong preference, or after resolving a complex bug. 
+- **Rules**: Physically write lessons to the memory file under categories: User Stylistic Preferences, Hard-Learned Lessons, Architectural Decisions. Do not just promise to remember.
+- **Global Memory**: For issues spanning multiple projects, document the root cause/solution into a global context directory (e.g., `<appDataDir>/knowledge`). Inject this historical context proactively in future tasks.
+
+### 3. Session End (Handoff)
+**Triggers**: Session is very long (>30 messages or >70% context used), major milestone reached, or user says "save checkpoint" / "handoff".
+
+**Action**: Generate an ultra-compact YAML checkpoint block (<200 tokens).
+
+**Checkpoint Format**:
+```yaml
+# CHECKPOINT — [Project Name] — [Date]
+project: "[Name]"
+goal: "[One-line goal]"
+status: "[e.g., 60% — backend API done]"
+stack: "[Tech Stack]"
+last_completed:
+  - "[Most recent task]"
+next_tasks:
+  - "[Immediate next task]"
+blockers: "[Blockers or 'none']"
+key_files:
+  - "[path/to/critical.ts]"
+env_needed: "[List of vars]"
+notes: "[Critical context]"
+```
+
+**Cross-Model Handoff Prompt**:
+Use this universal template when moving across models (Gemini, Claude, GPT):
+```markdown
+## RESUME CONTEXT — [Project Name]
+**Goal**: [One-sentence goal]
+**Current Status**: [Status]
+**Tech Stack**: [Stack]
+**Completed**: [Done items]
+**Next Tasks**: 1. [Task 1] 2. [Task 2]
+**Critical Files to Read First**: [File paths & reasons]
+**Known Constraints**: [Constraints]
+**Do NOT**: [Anti-patterns to avoid]
+Start by reading the critical files, then confirm understanding before proceeding.
+```
+
+**Checkpoint Storage Hierarchy**:
+1. `CHECKPOINT.md` in project root (Primary).
+2. `.agents/CHECKPOINT.md` (Alternative).
+3. Clipboard or Supabase notes table (Cross-device).
+
+---
+
+<a name="bahasa-indonesia"></a>
+## Bahasa Indonesia
+
+### Integrasi Orkestrasi
+Terhubung dan mengorkestrasi skill domain seperti `brainstorming` dan `zero-to-prod-orchestrator` untuk memastikan eksekusi kohesif selama siklus hidup sesi.
+
+### Deskripsi
+Skill ini mengatur memori agen: memuat konteks di awal sesi, memperbarui peta proyek dan grafik pembelajaran selama sesi berjalan, dan membuat checkpoint ringkas untuk perpindahan sesi (handoff).
+
+### 1. Awal Sesi (Ingestion)
+Aktifkan SEGERA pada sesi baru, atau saat diminta "mulai sesi" / "muat konteks". 
+
+**Alur Kerja:**
+1. **Temukan File**: Cari di root atau `.docs/`: `CONTEXT_MAP.md`, `LEARNING_GRAPH.md`, `PRD.md`, `BLUEPRINT.md`, `CHECKPOINT.md`, dan file identifikasi tech stack (`package.json`, dsb).
+2. **Pahami**: Baca isinya. Pahami batasan arsitektur, preferensi pengguna, pelajaran penting, dan tujuan/milestone saat ini.
+3. **Konfirmasi**: Beritahu pengguna secara singkat bahwa konteks dimuat, sebutkan Tech Stack dan tujuan langsung, lalu proses permintaan utama.
+
+### 2. Sesi Berjalan (Run)
+Pertahankan memori proyek agar tidak terjadi halusinasi dan hemat token.
+
+**Pelihara Peta Konteks (`CONTEXT_MAP.md`)**
+- Indeks super padat berisi arsitektur, lokasi file penting, dan graf dependensi.
+- **Aturan**: Jangan simpan kode lengkap, hanya path dan tanggung jawab singkat. Gunakan BM25/`grep_search` sebelum mengedit. Tambahkan entri baru saat membuat komponen/rute besar.
+
+**Pelihara Grafik Pembelajaran (`LEARNING_GRAPH.md`)**
+- **Pemicu**: Pengguna mengoreksi gaya koding, menyatakan preferensi, atau setelah mengatasi bug rumit.
+- **Aturan**: Catat langsung ke file dalam kategori: Preferensi Gaya, Pelajaran Berharga, Keputusan Arsitektur. 
+- **Memori Global**: Ekstrak solusi masalah lintas-proyek ke direktori pengetahuan global (`<appDataDir>/knowledge`). Gunakan pengetahuan masa lalu secara proaktif dengan menyebutkannya.
+
+### 3. Akhir Sesi (Handoff)
+**Pemicu**: Pesan > 30, jendela konteks > 70% terpakai, milestone tercapai, atau pengguna berkata "simpan checkpoint".
+
+**Tindakan**: Hasilkan blok YAML super ringkas (<200 token) berisi: `project`, `goal`, `status`, `stack`, `last_completed`, `next_tasks`, `blockers`, `key_files`, `env_needed`, dan `notes`.
+
+**Prompt Handoff Lintas-Model**:
+Gunakan template universal saat berpindah model:
+Berikan konteks proyek (Tujuan, Status, Stack, Tugas Selesai, Tugas Berikutnya), daftar file kritis untuk dibaca pertama kali, batasan, dan apa yang JANGAN dilakukan. Minta konfirmasi sebelum lanjut.
+
+**Hierarki Penyimpanan Checkpoint**:
+1. `CHECKPOINT.md` di root proyek (Utama).
+2. `.agents/CHECKPOINT.md` (Alternatif).
+3. Clipboard / Catatan Supabase (Lintas perangkat).

package/skills/solidjs-expert/SKILL.md

@@ -1,80 +1,81 @@
----
-name: solidjs-expert
-description: "Expert guide for SolidJS 2 and SolidStart — fine-grained reactivity, signals, createResource, and server-first rendering / Panduan ahli SolidJS 2 dan SolidStart — reaktivitas fine-grained, signals, createResource, dan rendering server-first."
-author: "Roedy Rustam"
----
-
-# SolidJS Expert (2026 Edition)
-
-[English](#english) | [Bahasa Indonesia](#bahasa-indonesia)
-
----
-
-<a name="english"></a>
-## English
-
-### Orchestration & Integration
-- **`performance-web-vitals`**: SolidJS's top-tier runtime performance.
-- **`tailwind-expert`**: Tailwind CSS integration with SolidJS.
-- **`state-management-expert`**: Solid signals vs other state management patterns.
-- **`typescript-expert`**: Type-safe SolidJS components.
-
-### Description
-Expert guide for SolidJS 2 and SolidStart, the fine-grained reactive framework with near-zero overhead. Covers signals (`createSignal`), derived state (`createMemo`), effects (`createEffect`), resources (`createResource`), stores, context, SolidStart routing, server functions, and migration patterns from React.
-
-### Trigger Conditions
-- Building applications with SolidJS or SolidStart.
-- Choosing SolidJS for performance-critical interactive UIs.
-- Comparing SolidJS vs React for a new project.
-- Understanding fine-grained reactivity patterns.
-
----
-
-### SolidJS Core
-
-```tsx
-import { createSignal, createMemo, createEffect, createResource, For, Show } from 'solid-js';
-
-function TodoApp() {
-  const [todos, setTodos] = createSignal<{ id: number; text: string; done: boolean }[]>([]);
-  const [filter, setFilter] = createSignal<'all' | 'active' | 'done'>('all');
-
-  const filtered = createMemo(() => {
-    const f = filter();
-    return f === 'all' ? todos() : todos().filter((t) => (f === 'done' ? t.done : !t.done));
-  });
-
-  const remaining = createMemo(() => todos().filter((t) => !t.done).length);
-
-  createEffect(() => {
-    document.title = `${remaining()} todos remaining`;
-  });
-
-  return (
-    <div>
-      <h1>Todos ({remaining()} remaining)</h1>
-      <For each={filtered()}>
-        {(todo) => <div classList={{ done: todo.done }}>{todo.text}</div>}
-      </For>
-      <Show when={todos().length > 0} fallback={<p>No todos yet!</p>}>
-        <button onClick={() => setTodos([])}>Clear All</button>
-      </Show>
-    </div>
-  );
-}
-```
-
-## Orchestration & Integration
-- `performance-web-vitals`, `tailwind-expert`, `typescript-expert`
-
----
-
-<a name="bahasa-indonesia"></a>
-## Bahasa Indonesia
-
-### Deskripsi
-Panduan ahli SolidJS 2 dan SolidStart, framework reaktif fine-grained dengan overhead hampir nol. Mencakup signals, derived state, effects, resources, stores, dan routing SolidStart.
-
-### Kondisi Pemicu
-- Membangun aplikasi dengan SolidJS atau SolidStart.
-- Memilih SolidJS untuk UI interaktif yang kritis performa.
+---
+name: solidjs-expert
+description: "Expert guide for SolidJS 2 and SolidStart — fine-grained reactivity, signals, createResource, and server-first rendering / Panduan ahli SolidJS 2 dan SolidStart — reaktivitas fine-grained, signals, createResource, dan rendering server-first."
+author: "Roedy Rustam"
+version: "3.0.0"
+---
+
+# SolidJS Expert (2026 Edition)
+
+[English](#english) | [Bahasa Indonesia](#bahasa-indonesia)
+
+---
+
+<a name="english"></a>
+## English
+
+### Orchestration & Integration
+- **`performance-web-vitals`**: SolidJS's top-tier runtime performance.
+- **`tailwind-expert`**: Tailwind CSS integration with SolidJS.
+- **`state-management-expert`**: Solid signals vs other state management patterns.
+- **`typescript-expert`**: Type-safe SolidJS components.
+
+### Description
+Expert guide for SolidJS 2 and SolidStart, the fine-grained reactive framework with near-zero overhead. Covers signals (`createSignal`), derived state (`createMemo`), effects (`createEffect`), resources (`createResource`), stores, context, SolidStart routing, server functions, and migration patterns from React.
+
+### Trigger Conditions
+- Building applications with SolidJS or SolidStart.
+- Choosing SolidJS for performance-critical interactive UIs.
+- Comparing SolidJS vs React for a new project.
+- Understanding fine-grained reactivity patterns.
+
+---
+
+### SolidJS Core
+
+```tsx
+import { createSignal, createMemo, createEffect, createResource, For, Show } from 'solid-js';
+
+function TodoApp() {
+  const [todos, setTodos] = createSignal<{ id: number; text: string; done: boolean }[]>([]);
+  const [filter, setFilter] = createSignal<'all' | 'active' | 'done'>('all');
+
+  const filtered = createMemo(() => {
+    const f = filter();
+    return f === 'all' ? todos() : todos().filter((t) => (f === 'done' ? t.done : !t.done));
+  });
+
+  const remaining = createMemo(() => todos().filter((t) => !t.done).length);
+
+  createEffect(() => {
+    document.title = `${remaining()} todos remaining`;
+  });
+
+  return (
+    <div>
+      <h1>Todos ({remaining()} remaining)</h1>
+      <For each={filtered()}>
+        {(todo) => <div classList={{ done: todo.done }}>{todo.text}</div>}
+      </For>
+      <Show when={todos().length > 0} fallback={<p>No todos yet!</p>}>
+        <button onClick={() => setTodos([])}>Clear All</button>
+      </Show>
+    </div>
+  );
+}
+```
+
+## Orchestration & Integration
+- `performance-web-vitals`, `tailwind-expert`, `typescript-expert`
+
+---
+
+<a name="bahasa-indonesia"></a>
+## Bahasa Indonesia
+
+### Deskripsi
+Panduan ahli SolidJS 2 dan SolidStart, framework reaktif fine-grained dengan overhead hampir nol. Mencakup signals, derived state, effects, resources, stores, dan routing SolidStart.
+
+### Kondisi Pemicu
+- Membangun aplikasi dengan SolidJS atau SolidStart.
+- Memilih SolidJS untuk UI interaktif yang kritis performa.

package/skills/spa-orchestrator/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: spa-orchestrator
 description: "Orchestrates Single-Page Application (SPA) architecture, integrating frontend state management with API-driven backends / Mengorkestrasi arsitektur Single-Page Application (SPA), mengintegrasikan state management frontend dengan backend berbasis API."
-author: "Roedy Rustam"
+author: "Roedy Rustam"
+version: "3.0.0"
 ---
 
 # Single-Page Application (SPA) Orchestrator (2026 Edition)
@@ -14,7 +15,7 @@ author: "Roedy Rustam"
 ## English
 
 ### Orchestration & Integration
-Connects and orchestrates with relevant domain skills like `modern-web-guidance`, `brainstorming`, `zero-to-prod-orchestrator`, and `project-context-mapper` to ensure cohesive execution.
+Connects and orchestrates with relevant domain skills like `modern-web-guidance`, `brainstorming`, `zero-to-prod-orchestrator`, and `session-memory-manager` to ensure cohesive execution.
 - **MANDATORY**: Execute `modern-web-guidance` FIRST for all HTML/CSS and client-side JS tasks to ensure modern web standards.
 
 ### Description
@@ -258,7 +259,7 @@ export default defineConfig({
 ## Bahasa Indonesia
 
 ### Integrasi Orkestrasi
-Terhubung dan mengorkestrasi skill domain yang relevan seperti `modern-web-guidance`, `brainstorming`, `zero-to-prod-orchestrator`, dan `project-context-mapper` untuk memastikan eksekusi yang kohesif.
+Terhubung dan mengorkestrasi skill domain yang relevan seperti `modern-web-guidance`, `brainstorming`, `zero-to-prod-orchestrator`, dan `session-memory-manager` untuk memastikan eksekusi yang kohesif.
 - **MANDATORY**: Eksekusi `modern-web-guidance` PERTAMA KALI untuk semua tugas HTML/CSS dan JS sisi klien guna memastikan standar web modern.
 
 ### Deskripsi
@@ -304,4 +305,4 @@ Gunakan plugin `TanStackRouterVite` untuk auto-generate route tree. Konfigurasi
 4. **Terms of Reference / Terms of Service** (`/terms`)
 5. **Privacy Policy** (`/privacy-policy`)
 
-These pages must be generated with standard boilerplate content that can later be customized to fit the specific application. Do not wait for the user to ask for them; they are a strict requirement for all web projects. / **WAJIB**: Otomatis buatkan halaman standar (About, Profile, Contact, Terms, Privacy Policy) pada setiap pembuatan aplikasi/website baru dengan konten boilerplate yang bisa disesuaikan nanti.
+These pages must be generated with standard boilerplate content that can later be customized to fit the specific application. Do not wait for the user to ask for them; they are a strict requirement for all web projects. / **WAJIB**: Otomatis buatkan halaman standar (About, Profile, Contact, Terms, Privacy Policy) pada setiap pembuatan aplikasi/website baru dengan konten boilerplate yang bisa disesuaikan nanti.

package/skills/sse-websocket-streaming-expert/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: sse-websocket-streaming-expert
 description: "Expert guide for Server-Sent Events (SSE), WebSockets, and Streaming Architectures. Covers real-time data push, Socket.IO, Hono WebSocket, and AI response streaming / Panduan ahli streaming real-time."
-author: "Roedy Rustam"
+author: "Roedy Rustam"
+version: "3.0.0"
 ---
 
 # SSE, WebSocket & Streaming Expert
@@ -90,4 +91,4 @@ Saat aplikasi diskalakan ke beberapa server (horizontal scaling), pengguna yang
 ## Integrasi Orkestrasi
 - Melengkapi `js-backend-expert` atau `go-programming-expert` dengan kemampuan push real-time.
 - Sangat penting bagi `gemini-agent-booster` saat membangun antarmuka chat AI.
-- Terintegrasi dengan `api-gateway-proxy-expert` (pastikan NGINX/proxy tidak melakukan *buffering* pada koneksi streaming).
+- Terintegrasi dengan `api-gateway-proxy-expert` (pastikan NGINX/proxy tidak melakukan *buffering* pada koneksi streaming).

package/skills/state-management-expert/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: state-management-expert
 description: "Expert guide for modern client-side state management: Zustand, Jotai, Valtio, TanStack Store, Redux Toolkit, and server state patterns with TanStack Query / Panduan ahli untuk manajemen state client-side modern: Zustand, Jotai, Valtio, TanStack Store, Redux Toolkit, dan pola server state dengan TanStack Query."
-author: "Roedy Rustam"
+author: "Roedy Rustam"
+version: "3.0.0"
 ---
 
 # State Management Expert (Modern React Edition)
@@ -14,7 +15,7 @@ author: "Roedy Rustam"
 ## English
 
 ### Orchestration & Integration
-Connects and orchestrates with relevant domain skills like `brainstorming`, `zero-to-prod-orchestrator`, and `project-context-mapper` to ensure cohesive execution.
+Connects and orchestrates with relevant domain skills like `brainstorming`, `zero-to-prod-orchestrator`, and `session-memory-manager` to ensure cohesive execution.
 
 ### Description
 Expert guide for selecting and implementing the right state management solution for React and Next.js applications. Covers **Zustand 5**, **Jotai 2**, **Valtio**, **TanStack Store**, and **Redux Toolkit 2**, with clear guidance on when to use each, proper separation of server state (TanStack Query) from client state, and advanced patterns like slices, persistence, and devtools integration.
@@ -255,7 +256,7 @@ export function StoreProvider({ children, initialUser }: Props) {
 ## Bahasa Indonesia
 
 ### Integrasi Orkestrasi
-Terhubung dan mengorkestrasi skill domain yang relevan seperti `brainstorming`, `zero-to-prod-orchestrator`, dan `project-context-mapper` untuk memastikan eksekusi yang kohesif.
+Terhubung dan mengorkestrasi skill domain yang relevan seperti `brainstorming`, `zero-to-prod-orchestrator`, dan `session-memory-manager` untuk memastikan eksekusi yang kohesif.
 
 ### Deskripsi
 Panduan ahli untuk memilih dan mengimplementasikan solusi manajemen state yang tepat untuk aplikasi React dan Next.js. Mencakup **Zustand 5**, **Jotai 2**, **Valtio**, dan **Redux Toolkit 2**, dengan panduan pemilihan yang jelas, pemisahan server state (TanStack Query) dari client state, dan pola lanjutan seperti slices, persistensi, dan integrasi devtools.
@@ -275,4 +276,4 @@ Panduan ahli untuk memilih dan mengimplementasikan solusi manajemen state yang t
 - **Gunakan Jotai** untuk state atomik yang sangat granular dan reaktif.
 - **Hindari menyimpan data server di client state** — ini adalah sumber bug terbesar di aplikasi React.
 - **Selective subscription**: Selalu gunakan selector untuk menghindari re-render yang tidak perlu.
-- **DevTools**: Selalu integrasikan devtools di development untuk debugging yang efektif.
+- **DevTools**: Selalu integrasikan devtools di development untuk debugging yang efektif.

package/skills/supabase-security-expert/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: supabase-security-expert
 description: "Supabase security expert to audit RLS (Row Level Security), RBAC, relational databases, prevent data leakage, and utilize Supabase Linter / Ahli keamanan Supabase untuk audit RLS (Row Level Security), RBAC, database relasional, pencegahan kebocoran data, dan pemanfaatan Supabase Linter."
-author: "Roedy Rustam"
+author: "Roedy Rustam"
+version: "3.0.0"
 ---
 
 # Supabase Security Expert (2026 Edition — Auth v3 / PKCE)
@@ -14,7 +15,7 @@ author: "Roedy Rustam"
 ## English
 
 ### Orchestration & Integration
-Connects and orchestrates with relevant domain skills like `brainstorming`, `zero-to-prod-orchestrator`, and `project-context-mapper` to ensure cohesive execution.
+Connects and orchestrates with relevant domain skills like `brainstorming`, `zero-to-prod-orchestrator`, and `session-memory-manager` to ensure cohesive execution.
 
 ### Description
 Expert guide for auditing and hardening Supabase applications. Covers Row Level Security (RLS), Supabase Auth v3 (PKCE flow), API key hygiene, data leakage prevention, Supabase Linter, and production security checklists.
@@ -203,7 +204,7 @@ USING (bucket_id = 'user-uploads' AND auth.uid()::text = (storage.foldername(nam
 ## Bahasa Indonesia
 
 ### Integrasi Orkestrasi
-Terhubung dan mengorkestrasi skill domain yang relevan seperti `brainstorming`, `zero-to-prod-orchestrator`, dan `project-context-mapper` untuk memastikan eksekusi yang kohesif.
+Terhubung dan mengorkestrasi skill domain yang relevan seperti `brainstorming`, `zero-to-prod-orchestrator`, dan `session-memory-manager` untuk memastikan eksekusi yang kohesif.
 
 ### Deskripsi
 Panduan ahli untuk mengaudit dan mengeraskan aplikasi Supabase. Mencakup Row Level Security (RLS), Supabase Auth v3 (PKCE flow), kebersihan API key, pencegahan kebocoran data, Supabase Linter, dan checklist keamanan produksi.
@@ -246,4 +247,4 @@ Buat bucket penyimpanan privat (`public: false`) dengan batasan ukuran file dan
 - PKCE flow diaktifkan di klien Auth v3.
 - Bucket storage privat secara default.
 - Supabase Linter tidak ada isu kritis.
-- MFA diaktifkan untuk pengguna admin.
+- MFA diaktifkan untuk pengguna admin.