vibes-plug 2.5.0 → 2.14.1

package/skills/session-handoff-resume/SKILL.md

@@ -1,158 +0,0 @@
----
-name: session-handoff-resume
-description: "Skill to save ultra-compact project checkpoints and seamlessly resume work across accounts or new chat sessions with minimum token consumption / Skill untuk menyimpan checkpoint proyek yang super ringkas dan melanjutkan pekerjaan secara efisien saat ganti akun/sesi tanpa boros token."
-author: "Roedy Rustam"
----
-
-# Session Handoff & Resume (2026 — Cross-Model Edition)
-
-[English](#english) | [Bahasa Indonesia](#bahasa-indonesia)
-
----
-
-<a name="english"></a>
-## English
-
-### Description
-Saves ultra-compact project checkpoints and enables seamless work resumption across new chat sessions, different accounts, or different AI models (Gemini, Claude, GPT). Designed for minimum token consumption while preserving full context needed for continuation.
-
-### Trigger Conditions
-- Session is running very long and context window is nearly exhausted.
-- User wants to switch to a new chat session or different AI model.
-- User wants to save progress before closing and resume later.
-- User says "save checkpoint", "handoff", "save progress", "resume later".
-
-### Checkpoint Format (Ultra-Compact)
-
-When creating a checkpoint, output a compact YAML block under 200 tokens:
-
-```yaml
-# CHECKPOINT — [Project Name] — [Date]
-project: "[Project Name]"
-goal: "[One-line goal of the current session]"
-status: "[brief status: e.g., '60% — backend API done, frontend in progress']"
-stack: "[e.g., Next.js 15 + Hono + Supabase + Drizzle]"
-last_completed:
-  - "[Most recent task completed]"
-  - "[Second most recent]"
-next_tasks:
-  - "[Immediate next task]"
-  - "[Following task]"
-  - "[Following task]"
-blockers: "[Any known blockers or pending decisions, or 'none']"
-key_files:
-  - "[path/to/critical/file.ts]"
-  - "[path/to/another/file.ts]"
-env_needed: "[List of env vars needed, e.g., SUPABASE_URL, STRIPE_KEY]"
-notes: "[Any critical context that doesn't fit above]"
-```
-
-### Cross-Model Handoff Protocol (2026)
-
-Different AI models interpret context differently. Use this universal handoff prompt:
-
-```markdown
-## RESUME CONTEXT — [Project Name]
-
-You are resuming work on [Project Name]. Read this context carefully before taking any action.
-
-**Goal**: [One-sentence project goal]
-**Current Status**: [What's been done, what's pending]
-**Tech Stack**: [Stack details]
-**Repository**: [path or URL if available]
-
-**Completed**:
-- ✅ [Done item 1]
-- ✅ [Done item 2]
-
-**Next Tasks** (in priority order):
-1. [ ] [Immediate next task — be specific]
-2. [ ] [Second task]
-3. [ ] [Third task]
-
-**Critical Files to Read First**:
-- [file path] — [why it's critical]
-- [file path] — [why it's critical]
-
-**Known Constraints**:
-- [Constraint 1, e.g., "Use pnpm, not npm"]
-- [Constraint 2, e.g., "Admin panel must be on admin.domain.com"]
-
-**Do NOT**:
-- [Something the previous session explicitly avoided]
-- [Another anti-pattern to avoid]
-
-Start by reading the critical files listed above, then confirm you understand the current state before proceeding.
-```
-
-### Checkpoint Storage Locations
-
-| Destination | Use When |
-|---|---|
-| `CHECKPOINT.md` in project root | Primary — version-controlled |
-| `.agents/CHECKPOINT.md` | Alternative — agents-specific dir |
-| Copied to clipboard | Quick cross-session handoff |
-| Supabase notes table | Cloud-synced across devices |
-
-### Resume Protocol (For New Session)
-When the user provides a checkpoint to resume from:
-1. **Read all key files** listed in the checkpoint.
-2. **Verify current state** matches the checkpoint (check git status, recent commits).
-3. **Confirm understanding** — briefly state what you're resuming and what the first task is.
-4. **Proceed immediately** — don't ask unnecessary questions.
-
-### Automatic Checkpoint Triggers
-Proactively offer to create a checkpoint when:
-- User has been working for > 30 messages in a session.
-- The context window is > 70% consumed.
-- A major milestone is completed (e.g., "backend API is fully done").
-- The user says "I'll continue later".
-
----
-
-<a name="bahasa-indonesia"></a>
-## Bahasa Indonesia
-
-### Deskripsi
-Menyimpan checkpoint proyek yang ultra-ringkas dan memungkinkan kelanjutan pekerjaan yang mulus di sesi chat baru, akun yang berbeda, atau model AI yang berbeda (Gemini, Claude, GPT). Dirancang untuk konsumsi token minimum sambil mempertahankan konteks penuh yang diperlukan untuk kelanjutan.
-
-### Kondisi Pemicu
-- Sesi berjalan sangat lama dan context window hampir habis.
-- Pengguna ingin beralih ke sesi chat baru atau model AI yang berbeda.
-- Pengguna ingin menyimpan progres sebelum menutup dan melanjutkan nanti.
-- Pengguna berkata "simpan checkpoint", "handoff", "simpan progres", "lanjut nanti".
-
-### Format Checkpoint (Ultra-Ringkas)
-
-Saat membuat checkpoint, keluarkan blok YAML ringkas di bawah 200 token dengan field: `project`, `goal`, `status`, `stack`, `last_completed`, `next_tasks`, `blockers`, `key_files`, `env_needed`, `notes`.
-
-### Protokol Handoff Lintas-Model (2026)
-
-Model AI yang berbeda menginterpretasikan konteks secara berbeda. Gunakan prompt handoff universal saat berpindah antar model (Gemini → Claude → GPT):
-- Sertakan goal satu kalimat, status saat ini, stack, daftar tugas yang selesai (✅), dan tugas berikutnya yang diprioritaskan.
-- Sertakan file kritis yang harus dibaca terlebih dahulu oleh model baru.
-- Sertakan kendala yang diketahui dan daftar "Jangan Lakukan".
-- Minta model baru untuk mengkonfirmasi pemahaman sebelum melanjutkan.
-
-### Lokasi Penyimpanan Checkpoint
-
-| Tujuan | Gunakan Saat |
-|---|---|
-| `CHECKPOINT.md` di root proyek | Utama — dikontrol versi |
-| `.agents/CHECKPOINT.md` | Alternatif — direktori agen |
-| Disalin ke clipboard | Handoff lintas sesi cepat |
-| Tabel catatan Supabase | Tersinkronisasi cloud antar perangkat |
-
-### Protokol Resume (Untuk Sesi Baru)
-Saat pengguna memberikan checkpoint untuk dilanjutkan:
-1. **Baca semua file kritis** yang tercantum dalam checkpoint.
-2. **Verifikasi status saat ini** cocok dengan checkpoint (periksa git status, commit terbaru).
-3. **Konfirmasi pemahaman** — nyatakan singkat apa yang dilanjutkan dan apa tugas pertama.
-4. **Lanjutkan segera** — jangan ajukan pertanyaan yang tidak perlu.
-
-### Pemicu Checkpoint Otomatis
-Tawarkan secara proaktif untuk membuat checkpoint saat:
-- Pengguna telah bekerja lebih dari 30 pesan dalam satu sesi.
-- Context window > 70% terpakai.
-- Milestone besar selesai.
-- Pengguna berkata "saya akan lanjutkan nanti".

package/skills/skill_baru/SKILL.md

@@ -1,172 +0,0 @@
----
-name: skill-baru
-description: "Comprehensive template for creating new vibes-plug skills with proper structure, trigger conditions, and bilingual support / Template komprehensif untuk membuat skill vibes-plug baru dengan struktur yang tepat, kondisi pemicu, dan dukungan bilingual."
-author: "Roedy Rustam"
----
-
-# [Skill Name] — vibes-plug Skill Template
-
-[English](#english) | [Bahasa Indonesia](#bahasa-indonesia)
-
----
-
-> **HOW TO USE THIS TEMPLATE**
-> 1. Copy this entire folder (`skill_baru/`) and rename it using kebab-case (e.g., `my-new-skill/`).
-> 2. Replace all placeholder text marked with `[...]` brackets.
-> 3. Update the frontmatter `name` and `description` fields above.
-> 4. Delete this instruction block before publishing.
-> 5. Add your skill to the `brainstorming` orchestration matrix if it belongs to a domain.
-
----
-
-<a name="english"></a>
-## English
-
-### Description
-[One paragraph describing the purpose and scope of this skill. Be specific about what problems it solves and what technology versions it targets.]
-
-Example: *"Expert guide for [Technology/Domain] (v[X.Y]+). Covers [feature A], [feature B], [pattern C], and [best practice D] for production-grade TypeScript/JavaScript applications."*
-
-### Trigger Conditions
-Activate this skill when the user is:
-- [Trigger scenario 1 — be specific, e.g., "Writing X with framework Y"]
-- [Trigger scenario 2]
-- [Trigger scenario 3]
-- [Trigger scenario 4]
-
----
-
-### Core Concepts
-
-#### [Concept 1 — e.g., "Architecture Overview"]
-[Explain the foundational concept. Use tables for comparisons, bullet points for lists, and code blocks for examples.]
-
-```typescript
-// [Language] — [What this code demonstrates]
-// Replace this block with a real, runnable code example.
-const example = {
-  field: 'value',
-};
-```
-
-#### [Concept 2 — e.g., "Selection Guide"]
-
-| Criteria | Option A | Option B | Option C |
-|---|---|---|---|
-| [Criterion 1] | [Value] | [Value] | [Value] |
-| [Criterion 2] | [Value] | [Value] | [Value] |
-| **Best For** | [Use case] | [Use case] | [Use case] |
-
-**Recommendation:** [State a clear default recommendation with rationale.]
-
----
-
-### [Main Topic Section 1 — e.g., "Setup & Configuration"]
-
-#### [Sub-topic 1.1]
-```typescript
-// Example: Configuration or setup code
-```
-
-#### [Sub-topic 1.2]
-```typescript
-// Example: Core usage pattern
-```
-
----
-
-### [Main Topic Section 2 — e.g., "Best Practices"]
-
-1. **[Practice 1]:** [Explanation]
-2. **[Practice 2]:** [Explanation]
-3. **[Practice 3]:** [Explanation]
-4. **[Practice 4]:** [Explanation]
-
----
-
-### Common Pitfalls to Avoid
-
-| Anti-Pattern | Problem | Correct Approach |
-|---|---|---|
-| [Bad practice 1] | [Why it's bad] | [What to do instead] |
-| [Bad practice 2] | [Why it's bad] | [What to do instead] |
-| [Bad practice 3] | [Why it's bad] | [What to do instead] |
-
----
-
-### Integration with Other Skills (MANDATORY)
-
-> ⚠️ **Every skill MUST list at least 3 cross-references.** No skill should exist in isolation.
-
-This skill works best when combined with:
-- `[skill-name]` — [Why and when to combine]
-- `[skill-name]` — [Why and when to combine]
-- `[skill-name]` — [Why and when to combine]
-
-### Referenced By Orchestrators (MANDATORY)
-
-> ⚠️ **Update the orchestrator skills below when creating a new domain skill.**
-
-This skill should be referenced by the following orchestrators:
-- `brainstorming` — Add to the "[Domain]" row in the Skill Integration & Orchestration Matrix
-- `zero-to-prod-orchestrator` — Add to Phase [N]: [Phase Name]
-- `production-ready-hardener` — Add to Phase [N] if relevant to pre-launch audit
-
----
-
-<a name="bahasa-indonesia"></a>
-## Bahasa Indonesia
-
-### Deskripsi
-[Satu paragraf menjelaskan tujuan dan ruang lingkup skill ini. Spesifik tentang masalah apa yang dipecahkan dan versi teknologi apa yang ditargetkan.]
-
-Contoh: *"Panduan ahli untuk [Teknologi/Domain] (v[X.Y]+). Mencakup [fitur A], [fitur B], [pola C], dan [praktik terbaik D] untuk aplikasi TypeScript/JavaScript berkualitas produksi."*
-
-### Kondisi Pemicu
-Aktifkan skill ini ketika pengguna sedang:
-- [Skenario pemicu 1 — spesifik, misal: "Menulis X dengan framework Y"]
-- [Skenario pemicu 2]
-- [Skenario pemicu 3]
-- [Skenario pemicu 4]
-
-### Panduan Singkat
-
-[Ringkasan praktis berisi poin-poin utama yang harus diketahui. Merujuk ke bagian English untuk detail teknis dan contoh kode lengkap.]
-
-- **[Prinsip 1]:** [Penjelasan singkat]
-- **[Prinsip 2]:** [Penjelasan singkat]
-- **[Prinsip 3]:** [Penjelasan singkat]
-- **[Prinsip 4]:** [Penjelasan singkat]
-
-### Integrasi dengan Skill Lain (WAJIB)
-
-> ⚠️ **Setiap skill WAJIB mencantumkan minimal 3 referensi silang.** Tidak ada skill yang boleh berdiri sendiri.
-
-Skill ini bekerja paling baik dikombinasikan dengan:
-- `[nama-skill]` — [Mengapa dan kapan dikombinasikan]
-- `[nama-skill]` — [Mengapa dan kapan dikombinasikan]
-- `[nama-skill]` — [Mengapa dan kapan dikombinasikan]
-
-### Direferensikan oleh Orchestrator (WAJIB)
-
-Skill ini harus direferensikan oleh orchestrator berikut:
-- `brainstorming` — Tambahkan ke baris "[Domain]" di Matriks Orkestrasi
-- `zero-to-prod-orchestrator` — Tambahkan ke Fase [N]
-- `production-ready-hardener` — Tambahkan ke Fase [N] jika relevan
-
----
-
-## Checklist Sebelum Mempublikasikan Skill Ini
-
-- [ ] Frontmatter `name` dan `description` sudah diisi (bilingual EN/ID).
-- [ ] Semua teks `[...]` placeholder sudah diganti.
-- [ ] Ada minimal 2 contoh kode yang nyata dan dapat dijalankan.
-- [ ] Ada tabel perbandingan atau selection guide jika relevan.
-- [ ] Ada bagian "Common Pitfalls" atau anti-pattern.
-- [ ] **Bagian "Integration with Other Skills" mencantumkan minimal 3 skill.**
-- [ ] **Bagian "Referenced By Orchestrators" sudah diisi.**
-- [ ] Bagian Bahasa Indonesia sudah diterjemahkan dengan benar.
-- [ ] Blok instruksi ini sudah dihapus.
-- [ ] **Skill sudah ditambahkan ke matriks orkestrasi `brainstorming`.**
-- [ ] **Skill sudah ditambahkan ke fase yang relevan di `zero-to-prod-orchestrator`.**
-- [ ] `BLUEPRINT.md` sudah diperbarui dengan deskripsi skill baru.

package/skills/supabase-migration/SKILL.md

@@ -1,45 +0,0 @@
----
-name: supabase-migration
-description: "A skill to create or apply a Supabase database migration / Kemampuan untuk membuat atau menerapkan migrasi database Supabase."
-author: "Roedy Rustam"
----
-
-# Supabase Migration Skill
-
-[English](#english) | [Bahasa Indonesia](#bahasa-indonesia)
-
----
-
-<a name="english"></a>
-## English
-
-### Description
-When the user asks to create or apply a database migration for Supabase, follow these instructions:
-
-### Instructions
-1. **Check Environment**: Ensure `supabase/migrations` directory exists. Run `list_dir` on it if needed.
-2. **Review Available MCP Commands**: Utilize the Supabase MCP integration.
-   - For listing existing migrations, use `mcp_supabase-mcp-server_list_migrations` with `project_id`.
-   - Before executing migration queries on the server directly, confirm the SQL is correct.
-3. **Execute Command**: 
-   - Write the SQL script to a local migration file located in `supabase/migrations/` using `write_to_file`. Use standard timestamps or `supabase migration new` command to get the filename.
-   - Run `npx supabase migration up` to test locally or use the remote MCP `apply_migration` if the user wants it applied remotely.
-4. **Final Step**: Confirm with the user that the migration successfully completed.
-
----
-
-<a name="bahasa-indonesia"></a>
-## Bahasa Indonesia
-
-### Deskripsi
-Ketika pengguna meminta untuk membuat atau menerapkan migrasi database untuk Supabase, ikuti instruksi berikut:
-
-### Instruksi
-1. **Periksa Lingkungan**: Pastikan direktori `supabase/migrations` ada. Jalankan `list_dir` jika diperlukan.
-2. **Tinjau Perintah MCP yang Tersedia**: Manfaatkan integrasi Supabase MCP.
-   - Untuk mencantumkan migrasi yang ada, gunakan `mcp_supabase-mcp-server_list_migrations` dengan `project_id`.
-   - Sebelum menjalankan kueri migrasi di server secara langsung, pastikan kode SQL-nya sudah benar.
-3. **Jalankan Perintah**:
-   - Tulis skrip SQL ke file migrasi lokal yang terletak di `supabase/migrations/` menggunakan `write_to_file`. Gunakan timestamp standar atau perintah `supabase migration new` untuk mendapatkan nama file.
-   - Jalankan `npx supabase migration up` untuk menguji secara lokal atau gunakan MCP remote `apply_migration` jika pengguna ingin menerapkannya secara remote.
-4. **Langkah Terakhir**: Konfirmasikan dengan pengguna bahwa migrasi telah berhasil diselesaikan.

package/skills/token-saver/SKILL.md

@@ -1,119 +0,0 @@
----
-name: token-saver
-description: "Skill to implement token saving scheme, concise, and focused on essential changes / Skill untuk menerapkan skema penghematan token, ringkas, dan fokus pada perubahan esensial tanpa basa-basi."
-author: vibes-plug-swarm
----
-
-# Token Saver Protocol (2026 Edition)
-
-[English](#english) | [Bahasa Indonesia](#bahasa-indonesia)
-
----
-
-<a name="english"></a>
-## English
-
-### Description
-Implements token-efficient communication protocols for long-context AI coding sessions. Activates concise mode — minimizing response verbosity while maintaining precision and completeness of technical output.
-
-### Trigger Conditions
-- User asks for token-saving mode, concise responses, or minimal output.
-- Session is running long and context window is being consumed rapidly.
-- User explicitly says "be concise", "save tokens", or "minimal".
-
-### Token Budget Strategies for Long Context
-
-#### 1. Response Compression Rules (Active When Triggered)
-- **No preamble**: Skip "Of course! I'll help you with that...".
-- **No restatement**: Never repeat back what the user just said.
-- **No trailing summaries**: Don't summarize what you just did at the end.
-- **Code-first**: Show the code change immediately, explain briefly after.
-- **Diff format**: For small changes, show only the changed lines (not the full file).
-- **Bullet > prose**: Use bullet lists instead of paragraphs for explanations.
-
-#### 2. Tool Call Efficiency
-- **Batch parallel reads**: Read multiple files in a single turn (not sequentially).
-- **Targeted grep over full reads**: Use `grep_search` to find specific content before reading the whole file.
-- **Write once**: Produce correct output on first try — avoid edit-then-edit-again cycles.
-- **Skip confirmation requests**: Don't ask "Shall I proceed?" — just proceed.
-
-#### 3. Context Window Budget Awareness
-When working on a long session:
-```
-Token budget allocation (for 200K context):
-├── System prompt + skills:    ~15K
-├── Conversation history:      ~50K (truncates older turns)
-├── File contents read:        ~100K (most expensive)
-└── Response generation:       ~35K
-```
-- Prefer `grep_search` over reading full large files.
-- Summarize large files mentally; only `view_file` the specific section needed.
-- When context is nearly full, create a checkpoint with `session-handoff-resume` skill.
-
-#### 4. Output Size Minimization
-For file edits:
-```diff
-# Preferred: diff format showing only changes
-- const OLD_VALUE = 'old';
-+ const NEW_VALUE = 'new';
-```
-
-For explanations:
-```
-# Preferred: 1-sentence rationale
-Changed X to Y because Z.
-
-# Avoid: multi-paragraph explanation of an obvious change
-```
-
-#### 5. Code Generation — First Draft Quality
-Generate correct, production-ready code on the first attempt:
-- Apply all relevant best practices from skills without being asked.
-- Include error handling, types, and edge cases inline.
-- Avoid TODOs, placeholder values, or "implement this later" comments.
-
----
-
-<a name="bahasa-indonesia"></a>
-## Bahasa Indonesia
-
-### Deskripsi
-Mengimplementasikan protokol komunikasi hemat token untuk sesi coding AI yang panjang. Mengaktifkan mode ringkas — meminimalkan verbositas respons sambil mempertahankan presisi dan kelengkapan output teknis.
-
-### Kondisi Pemicu
-- Pengguna meminta mode hemat token, respons ringkas, atau output minimal.
-- Sesi sudah panjang dan context window sedang dikonsumsi dengan cepat.
-- Pengguna secara eksplisit berkata "ringkas", "hemat token", atau "minimal".
-
-### Strategi Token Budget untuk Konteks Panjang
-
-#### 1. Aturan Kompresi Respons (Aktif Saat Dipicu)
-- Tanpa pembuka: Lewati "Tentu saja! Saya akan membantu Anda dengan...".
-- Tanpa pengulangan: Jangan pernah mengulangi apa yang baru saja dikatakan pengguna.
-- Tanpa ringkasan di akhir: Jangan rangkum apa yang baru saja dilakukan.
-- Code-first: Tunjukkan perubahan kode segera, jelaskan singkat setelahnya.
-- Format diff: Untuk perubahan kecil, tunjukkan hanya baris yang berubah.
-- Poin > prosa: Gunakan daftar poin daripada paragraf.
-
-#### 2. Efisiensi Pemanggilan Tool
-- Baca beberapa file secara paralel dalam satu giliran.
-- Gunakan `grep_search` untuk menemukan konten spesifik sebelum membaca file lengkap.
-- Hasilkan output yang benar pada percobaan pertama.
-- Jangan tanyakan "Apakah saya harus melanjutkan?" — langsung lanjutkan.
-
-#### 3. Kesadaran Budget Context Window
-Alokasikan token secara bijak: batasi baca file besar, gunakan `grep_search` daripada membaca file penuh, dan buat checkpoint dengan skill `session-handoff-resume` saat konteks hampir penuh.
-
-#### 4. Minimalisasi Ukuran Output
-Gunakan format diff untuk edit file. Berikan penjelasan 1 kalimat untuk perubahan yang jelas.
-
-#### 5. Kualitas Draft Kode Pertama
-Hasilkan kode yang benar dan siap produksi pada percobaan pertama — termasuk error handling, tipe, dan edge case secara inline. Hindari TODO, nilai placeholder, atau komentar "implementasikan ini nanti".
-
----
-
-## Orchestration & Integration
-- Integrates with `zero-to-prod-orchestrator`, `session-handoff-resume`, `brainstorming`, and `ai-cost-token-optimizer`.
-
-## Integrasi Orkestrasi
-- Terintegrasi dengan `zero-to-prod-orchestrator`, `session-handoff-resume`, `brainstorming`, dan `ai-cost-token-optimizer`.