vibes-plug 2.5.0 → 2.11.0

package/skills/post-quantum-crypto-migrator/SKILL.md

@@ -1,57 +1,57 @@
----
-name: post-quantum-crypto-migrator
-description: "FinTech future-proofing. Scans and migrates classical encryption to NIST-approved Post-Quantum Cryptography (PQC) / Migrasi ke Kriptografi Pasca-Kuantum (PQC) yang disetujui NIST untuk sistem FinTech."
-author: vibes-plug-swarm
----
-
-# Post-Quantum Cryptography Migrator
-
-[English](#english) | [Bahasa Indonesia](#bahasa-indonesia)
-
----
-
-<a name="english"></a>
-## English
-
-### Description
-An advanced security architect skill designed to future-proof FinTech, SaaS, and Payment integrations (such as DOKU) against the impending threat of Quantum Computers breaking classical encryption (RSA/ECC). It scans codebases for vulnerable cryptographic algorithms and migrates them to NIST-approved Post-Quantum Cryptography (PQC) algorithms, such as CRYSTALS-Kyber (for Key Encapsulation) and CRYSTALS-Dilithium/SPHINCS+ (for Digital Signatures).
-
-### Trigger Conditions
-- During security audits or Phase 6 (Automated Testing & Security Audit).
-- When upgrading high-security financial payment gateways or generating JWT/Session tokens.
-- Explicit user request to make the application "Quantum-Proof".
-
-### Operating Protocol
-1. **Cryptographic Discovery**: Audits all usage of `crypto`, `bcrypt`, `RSA`, `ECDSA`, and `HMAC` operations.
-2. **Hybrid Migration Plan**: Recommends hybrid implementations (combining classical ECC with PQC algorithms like Kyber-512) to comply with modern standards while maintaining backward compatibility.
-3. **Implementation**: Swaps vulnerable implementations with PQC-ready libraries (e.g., OQS - Open Quantum Safe, or modernized webcrypto wrappers supporting Kyber).
-4. **Validation**: Ensures the expanded key sizes and signature sizes of PQC algorithms do not break database schemas or HTTP header limits.
-
-## Orchestration & Integration
-- Enforces extreme security standards alongside `authentication-identity-expert`.
-- Hardens `doku-payment-gateway` and `saas-billing` payload encryption to banking-grade PQC standards.
-- Integrates with `database-orm-expert` to update schema lengths (PQC keys are significantly larger than RSA).
-
----
-
-<a name="bahasa-indonesia"></a>
-## Bahasa Indonesia
-
-### Deskripsi
-Keterampilan arsitek keamanan tingkat lanjut yang dirancang untuk melindungi integrasi FinTech, SaaS, dan Sistem Pembayaran (seperti DOKU) dari ancaman Komputer Kuantum yang kelak mampu membobol enkripsi klasik (RSA/ECC). Agen ini memindai basis kode untuk mencari algoritma kriptografi yang rentan, lalu memigrasikannya ke standar Kriptografi Pasca-Kuantum (PQC) yang disetujui NIST, seperti CRYSTALS-Kyber (untuk *Key Encapsulation*) dan CRYSTALS-Dilithium/SPHINCS+ (untuk Tanda Tangan Digital).
-
-### Kondisi Pemicu
-- Selama audit keamanan atau Fase 6 (Pengujian Otomatis & Audit Keamanan).
-- Saat memperbarui *payment gateway* keuangan berskala tinggi atau membuat token JWT/Sesi.
-- Permintaan eksplisit dari pengguna untuk membuat aplikasi *"Quantum-Proof"* (Tahan-Kuantum).
-
-### Protokol Operasi
-1. **Penemuan Kriptografi**: Mengaudit seluruh penggunaan operasi `crypto`, `bcrypt`, `RSA`, `ECDSA`, dan `HMAC`.
-2. **Rencana Migrasi Hibrida**: Merekomendasikan implementasi hibrida (menggabungkan algoritma klasik ECC dengan algoritma PQC seperti Kyber-512) untuk mematuhi standar modern sembari menjaga kompatibilitas ke belakang (*backward compatibility*).
-3. **Implementasi**: Menukar implementasi yang rentan dengan pustaka yang mendukung PQC (misalnya, OQS - Open Quantum Safe, atau *wrapper webcrypto* modern yang mendukung Kyber).
-4. **Validasi**: Memastikan ukuran kunci dan ukuran *signature* algoritma PQC yang lebih besar tidak merusak skema database atau melampaui batas header HTTP.
-
-## Integrasi Orkestrasi
-- Menegakkan standar keamanan ekstrem berdampingan dengan `authentication-identity-expert`.
-- Memperkeras enkripsi *payload* `doku-payment-gateway` dan `saas-billing` ke standar PQC kelas perbankan.
-- Terintegrasi dengan `database-orm-expert` untuk memperbarui panjang skema kolom database (karena ukuran kunci PQC jauh lebih besar dari RSA).
+---
+name: post-quantum-crypto-migrator
+description: "FinTech future-proofing. Scans and migrates classical encryption to NIST-approved Post-Quantum Cryptography (PQC) / Migrasi ke Kriptografi Pasca-Kuantum (PQC) yang disetujui NIST untuk sistem FinTech."
+author: "Roedy Rustam"
+---
+
+# Post-Quantum Cryptography Migrator
+
+[English](#english) | [Bahasa Indonesia](#bahasa-indonesia)
+
+---
+
+<a name="english"></a>
+## English
+
+### Description
+An advanced security architect skill designed to future-proof FinTech, SaaS, and Payment integrations (such as DOKU) against the impending threat of Quantum Computers breaking classical encryption (RSA/ECC). It scans codebases for vulnerable cryptographic algorithms and migrates them to NIST-approved Post-Quantum Cryptography (PQC) algorithms, such as CRYSTALS-Kyber (for Key Encapsulation) and CRYSTALS-Dilithium/SPHINCS+ (for Digital Signatures).
+
+### Trigger Conditions
+- During security audits or Phase 6 (Automated Testing & Security Audit).
+- When upgrading high-security financial payment gateways or generating JWT/Session tokens.
+- Explicit user request to make the application "Quantum-Proof".
+
+### Operating Protocol
+1. **Cryptographic Discovery**: Audits all usage of `crypto`, `bcrypt`, `RSA`, `ECDSA`, and `HMAC` operations.
+2. **Hybrid Migration Plan**: Recommends hybrid implementations (combining classical ECC with PQC algorithms like Kyber-512) to comply with modern standards while maintaining backward compatibility.
+3. **Implementation**: Swaps vulnerable implementations with PQC-ready libraries (e.g., OQS - Open Quantum Safe, or modernized webcrypto wrappers supporting Kyber).
+4. **Validation**: Ensures the expanded key sizes and signature sizes of PQC algorithms do not break database schemas or HTTP header limits.
+
+## Orchestration & Integration
+- Enforces extreme security standards alongside `authentication-identity-expert`.
+- Hardens `doku-payment-gateway` and `saas-billing` payload encryption to banking-grade PQC standards.
+- Integrates with `database-orm-expert` to update schema lengths (PQC keys are significantly larger than RSA).
+
+---
+
+<a name="bahasa-indonesia"></a>
+## Bahasa Indonesia
+
+### Deskripsi
+Keterampilan arsitek keamanan tingkat lanjut yang dirancang untuk melindungi integrasi FinTech, SaaS, dan Sistem Pembayaran (seperti DOKU) dari ancaman Komputer Kuantum yang kelak mampu membobol enkripsi klasik (RSA/ECC). Agen ini memindai basis kode untuk mencari algoritma kriptografi yang rentan, lalu memigrasikannya ke standar Kriptografi Pasca-Kuantum (PQC) yang disetujui NIST, seperti CRYSTALS-Kyber (untuk *Key Encapsulation*) dan CRYSTALS-Dilithium/SPHINCS+ (untuk Tanda Tangan Digital).
+
+### Kondisi Pemicu
+- Selama audit keamanan atau Fase 6 (Pengujian Otomatis & Audit Keamanan).
+- Saat memperbarui *payment gateway* keuangan berskala tinggi atau membuat token JWT/Sesi.
+- Permintaan eksplisit dari pengguna untuk membuat aplikasi *"Quantum-Proof"* (Tahan-Kuantum).
+
+### Protokol Operasi
+1. **Penemuan Kriptografi**: Mengaudit seluruh penggunaan operasi `crypto`, `bcrypt`, `RSA`, `ECDSA`, dan `HMAC`.
+2. **Rencana Migrasi Hibrida**: Merekomendasikan implementasi hibrida (menggabungkan algoritma klasik ECC dengan algoritma PQC seperti Kyber-512) untuk mematuhi standar modern sembari menjaga kompatibilitas ke belakang (*backward compatibility*).
+3. **Implementasi**: Menukar implementasi yang rentan dengan pustaka yang mendukung PQC (misalnya, OQS - Open Quantum Safe, atau *wrapper webcrypto* modern yang mendukung Kyber).
+4. **Validasi**: Memastikan ukuran kunci dan ukuran *signature* algoritma PQC yang lebih besar tidak merusak skema database atau melampaui batas header HTTP.
+
+## Integrasi Orkestrasi
+- Menegakkan standar keamanan ekstrem berdampingan dengan `authentication-identity-expert`.
+- Memperkeras enkripsi *payload* `doku-payment-gateway` dan `saas-billing` ke standar PQC kelas perbankan.
+- Terintegrasi dengan `database-orm-expert` untuk memperbarui panjang skema kolom database (karena ukuran kunci PQC jauh lebih besar dari RSA).

package/skills/prd-architect/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: prd-architect
 description: "Mandatory guardrail skill that enforces creating a comprehensive Product Requirements Document (PRD), ERD, and Documentation before generating code for new projects / Skill khusus untuk memaksa pembuatan Product Requirements Document (PRD), ERD, dan Dokumentasi secara otomatis sebelum mulai coding pada setiap proyek baru."
-author: "Roedy Rustam"
+author: "Roedy Rustam"
 ---
 
 # PRD Architect (2026 — PRD-as-Code Edition)
@@ -13,6 +13,9 @@ author: "Roedy Rustam"
 <a name="english"></a>
 ## English
 
+### Orchestration & Integration
+Connects and orchestrates with relevant domain skills like `brainstorming`, `zero-to-prod-orchestrator`, and `project-context-mapper` to ensure cohesive execution.
+
 ### Description
 Mandatory guardrail that enforces creating a comprehensive Product Requirements Document (PRD), Entity Relationship Diagram (ERD), and general Documentation before generating code for any new project. Introduces **PRD-as-Code** — a structured Markdown format designed to be machine-readable by AI agents and version-controlled alongside code.
 
@@ -151,6 +154,9 @@ projects ──has_many──> tasks
 <a name="bahasa-indonesia"></a>
 ## 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.
+
 ### Deskripsi
 Guardrail wajib yang memaksa pembuatan secara otomatis Product Requirements Document (PRD) komprehensif, Entity Relationship Diagram (ERD), dan Dokumentasi sebelum membuat kode untuk proyek baru apapun. Memperkenalkan **PRD-as-Code** — format Markdown terstruktur yang dirancang agar dapat dibaca mesin oleh agen AI dan dikontrol versi bersama kode.
 

package/skills/proactive-background-watcher/SKILL.md

@@ -1,62 +1,68 @@
----
-name: proactive-background-watcher
-description: "Grants the AI the ability to act proactively using native cron/timer scheduling. The agent can monitor systems, poll APIs, or watch logs in the background and self-trigger without waiting for user prompts."
+---
+name: proactive-background-watcher
+description: "Grants the AI the ability to act proactively using native cron/timer scheduling. The agent can monitor systems, poll APIs, or watch logs in the background and self-trigger without waiting for user prompts."
 author: "Roedy Rustam"
----
-
-# Proactive Background Watcher (Sentinel Agent)
-
-[English](#english) | [Bahasa Indonesia](#bahasa-indonesia)
-
----
-
-<a name="english"></a>
-## English
-
-### Description
-Standard LLM chat interfaces (like Claude or ChatGPT) are purely reactive—they do nothing until the user types a prompt. This skill gives Antigravity the "superpower" of proactivity. By utilizing the native `schedule` tool, the agent can set up background cron jobs or timers to monitor logs, poll APIs, or check CI/CD pipelines. If an anomaly is detected, the agent wakes up autonomously and alerts the user or fixes the issue.
-
-### Trigger Conditions
-Activate this skill when:
-- The user says "let me know when the deployment finishes."
-- The user asks to "monitor the server for errors."
-- The user wants a daily summary of new GitHub issues.
-
-### Core Concepts
-
-#### 1. The Sentinel Loop
-1. **Schedule:** Use the `schedule` tool. Set either a `DurationSeconds` (e.g., check again in 5 minutes) or a `CronExpression` (e.g., run every hour `0 * * * *`). Set `IsDaemon=true` if it's a long-running background watcher.
-2. **Sleep:** End your turn. The system will automatically wake you up when the timer/cron fires.
-3. **Execute:** When woken up by the timer prompt, execute your checks (e.g., read a log file, curl an API).
-4. **Evaluate:** If everything is normal, go back to sleep (or set a new timer). If an anomaly is found, notify the user immediately with an alert.
-
-#### 2. Agent Constraints
-- **Do not spam the user.** If a background check passes normally, do not write a message to the user. Only alert the user if action is required or a long-running task finally completes.
-- **Always provide a clear Prompt in the schedule tool:** e.g., "Timer fired: Check Vercel deployment status now."
-
----
-
-### Integration with Other Skills (MANDATORY)
-- `cron-scheduler-expert` — Provides the code-level knowledge for building app-level crons, while this skill is for the *agent's own* native scheduling.
-- `ci-cd-devops-architect` — Useful when the agent needs to watch GitHub Actions or Vercel pipelines.
-
-### Referenced By Orchestrators (MANDATORY)
-- `brainstorming` — Add to "Discovery & Audit".
-- `zero-to-prod-orchestrator` — Phase 7 (Deployment & Monitoring).
-
----
-
-<a name="bahasa-indonesia"></a>
-## Bahasa Indonesia
-
-### Deskripsi
-LLM biasa (seperti Claude) sepenuhnya reaktif—diam sampai pengguna mengetik. Skill ini memberi Anda "kekuatan super" proaktif (Sentinel). Menggunakan tool `schedule`, Anda dapat menjadwalkan tugas *background* untuk memantau log, mengecek status *deployment*, atau mengawasi API secara berkala. Anda bisa "bangun sendiri" tanpa disuruh jika menemukan error.
-
-### Kondisi Pemicu
-- Saat pengguna berkata "tolong kabari saya kalau *build*-nya sudah selesai."
-- Saat pengguna meminta Anda mengawasi log error produksi.
-
-### Panduan Singkat
-- **Gunakan Tool `schedule`:** Anda bisa mengatur waktu tunggu (`DurationSeconds`) atau jadwal rutin (`CronExpression`).
-- **Tidur & Bangun Otomatis:** Setelah mengatur jadwal, hentikan pemanggilan tool. Sistem akan membangunkan Anda secara otomatis saat waktunya tiba.
-- **Jangan Cerewet (No Spam):** Jika Anda terbangun karena alarm dan mengecek log ternyata tidak ada error, **jangan** beri tahu pengguna. Biarkan pengguna bekerja dengan tenang. Hanya lapor jika ada error atau tugas besar telah selesai.
+---
+
+# Proactive Background Watcher (Sentinel Agent)
+
+[English](#english) | [Bahasa Indonesia](#bahasa-indonesia)
+
+---
+
+<a name="english"></a>
+## English
+
+### Orchestration & Integration
+Connects and orchestrates with relevant domain skills like `brainstorming`, `zero-to-prod-orchestrator`, and `project-context-mapper` to ensure cohesive execution.
+
+### Description
+Standard LLM chat interfaces (like Claude or ChatGPT) are purely reactive—they do nothing until the user types a prompt. This skill gives Antigravity the "superpower" of proactivity. By utilizing the native `schedule` tool, the agent can set up background cron jobs or timers to monitor logs, poll APIs, or check CI/CD pipelines. If an anomaly is detected, the agent wakes up autonomously and alerts the user or fixes the issue.
+
+### Trigger Conditions
+Activate this skill when:
+- The user says "let me know when the deployment finishes."
+- The user asks to "monitor the server for errors."
+- The user wants a daily summary of new GitHub issues.
+
+### Core Concepts
+
+#### 1. The Sentinel Loop
+1. **Schedule:** Use the `schedule` tool. Set either a `DurationSeconds` (e.g., check again in 5 minutes) or a `CronExpression` (e.g., run every hour `0 * * * *`). Set `IsDaemon=true` if it's a long-running background watcher.
+2. **Sleep:** End your turn. The system will automatically wake you up when the timer/cron fires.
+3. **Execute:** When woken up by the timer prompt, execute your checks (e.g., read a log file, curl an API).
+4. **Evaluate:** If everything is normal, go back to sleep (or set a new timer). If an anomaly is found, notify the user immediately with an alert.
+
+#### 2. Agent Constraints
+- **Do not spam the user.** If a background check passes normally, do not write a message to the user. Only alert the user if action is required or a long-running task finally completes.
+- **Always provide a clear Prompt in the schedule tool:** e.g., "Timer fired: Check Vercel deployment status now."
+
+---
+
+### Integration with Other Skills (MANDATORY)
+- `cron-scheduler-expert` — Provides the code-level knowledge for building app-level crons, while this skill is for the *agent's own* native scheduling.
+- `ci-cd-devops-architect` — Useful when the agent needs to watch GitHub Actions or Vercel pipelines.
+
+### Referenced By Orchestrators (MANDATORY)
+- `brainstorming` — Add to "Discovery & Audit".
+- `zero-to-prod-orchestrator` — Phase 7 (Deployment & Monitoring).
+
+---
+
+<a name="bahasa-indonesia"></a>
+## 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.
+
+### Deskripsi
+LLM biasa (seperti Claude) sepenuhnya reaktif—diam sampai pengguna mengetik. Skill ini memberi Anda "kekuatan super" proaktif (Sentinel). Menggunakan tool `schedule`, Anda dapat menjadwalkan tugas *background* untuk memantau log, mengecek status *deployment*, atau mengawasi API secara berkala. Anda bisa "bangun sendiri" tanpa disuruh jika menemukan error.
+
+### Kondisi Pemicu
+- Saat pengguna berkata "tolong kabari saya kalau *build*-nya sudah selesai."
+- Saat pengguna meminta Anda mengawasi log error produksi.
+
+### Panduan Singkat
+- **Gunakan Tool `schedule`:** Anda bisa mengatur waktu tunggu (`DurationSeconds`) atau jadwal rutin (`CronExpression`).
+- **Tidur & Bangun Otomatis:** Setelah mengatur jadwal, hentikan pemanggilan tool. Sistem akan membangunkan Anda secara otomatis saat waktunya tiba.
+- **Jangan Cerewet (No Spam):** Jika Anda terbangun karena alarm dan mengecek log ternyata tidak ada error, **jangan** beri tahu pengguna. Biarkan pengguna bekerja dengan tenang. Hanya lapor jika ada error atau tugas besar telah selesai.