vibes-plug 2.11.0 → 3.9.0

package/skills/pdf-document-generation-expert/SKILL.md

@@ -1,91 +1,92 @@
----
-name: pdf-document-generation-expert
-description: "Expert guide for PDF generation and document processing (React PDF, Puppeteer, jsPDF, pdf-lib) / Panduan ahli generasi PDF dan pemrosesan dokumen (React PDF, Puppeteer, jsPDF, pdf-lib)."
-author: "Roedy Rustam"
----
-
-# PDF & Document Generation Expert (2026 Edition)
-
-[English](#english) | [Bahasa Indonesia](#bahasa-indonesia)
-
----
-
-<a name="english"></a>
-## English
-
-### Orchestration & Integration
-- **`email-notification-expert`**: PDF attachments in transactional emails.
-- **`saas-billing`**: Invoice and receipt PDF generation.
-- **`file-upload-media-expert`**: PDF storage and CDN delivery.
-
-### Description
-Expert guide for generating PDFs and processing documents in web applications. Covers React PDF (@react-pdf/renderer), Puppeteer HTML-to-PDF, jsPDF, pdf-lib, invoice generation, report templates, digital signatures, and document parsing.
-
-### Trigger Conditions
-- Generating invoices, receipts, or reports as PDFs.
-- Converting HTML pages to downloadable PDFs.
-- Building document templates with dynamic data.
-- Implementing digital signatures on PDF documents.
-
----
-
-### Library Selection
-
-| Library | Approach | Server/Client | Best For |
-|---------|----------|---------------|----------|
-| @react-pdf/renderer | React components → PDF | Both | Complex layouts |
-| Puppeteer | HTML → PDF (headless Chrome) | Server | Pixel-perfect from HTML |
-| jsPDF | Programmatic canvas | Client | Simple client-side PDFs |
-| pdf-lib | Low-level PDF manipulation | Both | Modify existing PDFs |
-
-```tsx
-// React PDF — Invoice generation
-import { Document, Page, Text, View, StyleSheet, renderToBuffer } from '@react-pdf/renderer';
-
-const styles = StyleSheet.create({
-  page: { padding: 40, fontSize: 12 },
-  header: { fontSize: 24, marginBottom: 20, color: '#8B5CF6' },
-  row: { flexDirection: 'row', justifyContent: 'space-between', marginBottom: 8 },
-  total: { fontSize: 16, fontWeight: 'bold', borderTopWidth: 1, paddingTop: 8, marginTop: 16 },
-});
-
-function InvoicePDF({ invoice }) {
-  return (
-    <Document>
-      <Page size="A4" style={styles.page}>
-        <Text style={styles.header}>Invoice #{invoice.number}</Text>
-        {invoice.items.map((item, i) => (
-          <View key={i} style={styles.row}>
-            <Text>{item.description}</Text>
-            <Text>${item.amount.toFixed(2)}</Text>
-          </View>
-        ))}
-        <View style={styles.total}>
-          <Text>Total: ${invoice.total.toFixed(2)}</Text>
-        </View>
-      </Page>
-    </Document>
-  );
-}
-
-// Server-side render to buffer
-export async function generateInvoicePDF(invoice) {
-  return await renderToBuffer(<InvoicePDF invoice={invoice} />);
-}
-```
-
-## Orchestration & Integration
-- `email-notification-expert`, `saas-billing`, `file-upload-media-expert`
-
----
-
-<a name="bahasa-indonesia"></a>
-## Bahasa Indonesia
-
-### Deskripsi
-Panduan ahli untuk menghasilkan PDF dan memproses dokumen di aplikasi web. Mencakup React PDF, Puppeteer HTML-to-PDF, jsPDF, dan pdf-lib.
-
-### Kondisi Pemicu
-- Menghasilkan invoice, struk, atau laporan sebagai PDF.
-- Mengkonversi halaman HTML ke PDF yang bisa diunduh.
-- Membangun template dokumen dengan data dinamis.
+---
+name: pdf-document-generation-expert
+description: "Expert guide for PDF generation and document processing (React PDF, Puppeteer, jsPDF, pdf-lib) / Panduan ahli generasi PDF dan pemrosesan dokumen (React PDF, Puppeteer, jsPDF, pdf-lib)."
+author: "Roedy Rustam"
+version: "3.0.0"
+---
+
+# PDF & Document Generation Expert (2026 Edition)
+
+[English](#english) | [Bahasa Indonesia](#bahasa-indonesia)
+
+---
+
+<a name="english"></a>
+## English
+
+### Orchestration & Integration
+- **`email-notification-expert`**: PDF attachments in transactional emails.
+- **`saas-billing`**: Invoice and receipt PDF generation.
+- **`file-upload-media-expert`**: PDF storage and CDN delivery.
+
+### Description
+Expert guide for generating PDFs and processing documents in web applications. Covers React PDF (@react-pdf/renderer), Puppeteer HTML-to-PDF, jsPDF, pdf-lib, invoice generation, report templates, digital signatures, and document parsing.
+
+### Trigger Conditions
+- Generating invoices, receipts, or reports as PDFs.
+- Converting HTML pages to downloadable PDFs.
+- Building document templates with dynamic data.
+- Implementing digital signatures on PDF documents.
+
+---
+
+### Library Selection
+
+| Library | Approach | Server/Client | Best For |
+|---------|----------|---------------|----------|
+| @react-pdf/renderer | React components → PDF | Both | Complex layouts |
+| Puppeteer | HTML → PDF (headless Chrome) | Server | Pixel-perfect from HTML |
+| jsPDF | Programmatic canvas | Client | Simple client-side PDFs |
+| pdf-lib | Low-level PDF manipulation | Both | Modify existing PDFs |
+
+```tsx
+// React PDF — Invoice generation
+import { Document, Page, Text, View, StyleSheet, renderToBuffer } from '@react-pdf/renderer';
+
+const styles = StyleSheet.create({
+  page: { padding: 40, fontSize: 12 },
+  header: { fontSize: 24, marginBottom: 20, color: '#8B5CF6' },
+  row: { flexDirection: 'row', justifyContent: 'space-between', marginBottom: 8 },
+  total: { fontSize: 16, fontWeight: 'bold', borderTopWidth: 1, paddingTop: 8, marginTop: 16 },
+});
+
+function InvoicePDF({ invoice }) {
+  return (
+    <Document>
+      <Page size="A4" style={styles.page}>
+        <Text style={styles.header}>Invoice #{invoice.number}</Text>
+        {invoice.items.map((item, i) => (
+          <View key={i} style={styles.row}>
+            <Text>{item.description}</Text>
+            <Text>${item.amount.toFixed(2)}</Text>
+          </View>
+        ))}
+        <View style={styles.total}>
+          <Text>Total: ${invoice.total.toFixed(2)}</Text>
+        </View>
+      </Page>
+    </Document>
+  );
+}
+
+// Server-side render to buffer
+export async function generateInvoicePDF(invoice) {
+  return await renderToBuffer(<InvoicePDF invoice={invoice} />);
+}
+```
+
+## Orchestration & Integration
+- `email-notification-expert`, `saas-billing`, `file-upload-media-expert`
+
+---
+
+<a name="bahasa-indonesia"></a>
+## Bahasa Indonesia
+
+### Deskripsi
+Panduan ahli untuk menghasilkan PDF dan memproses dokumen di aplikasi web. Mencakup React PDF, Puppeteer HTML-to-PDF, jsPDF, dan pdf-lib.
+
+### Kondisi Pemicu
+- Menghasilkan invoice, struk, atau laporan sebagai PDF.
+- Mengkonversi halaman HTML ke PDF yang bisa diunduh.
+- Membangun template dokumen dengan data dinamis.

package/skills/performance-web-vitals/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: performance-web-vitals
 description: "Expert guide for Web Performance optimization: Core Web Vitals (LCP, INP, CLS), bundle analysis, image optimization, rendering strategies, and Lighthouse score improvement / Panduan ahli untuk optimasi performa web: Core Web Vitals (LCP, INP, CLS), analisis bundle, optimasi gambar, strategi rendering, dan peningkatan skor Lighthouse."
-author: "Roedy Rustam"
+author: "Roedy Rustam"
+version: "3.0.0"
 ---
 
 # Web Performance & Core Web Vitals Expert
@@ -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 measuring, diagnosing, and optimizing web application performance with a focus on **Core Web Vitals** (LCP, INP, CLS), JavaScript bundle optimization, image and font loading strategies, rendering performance, and achieving high Lighthouse scores. Covers Next.js 15, React 19, and modern browser APIs.
@@ -308,7 +309,7 @@ onTTFB(sendToAnalytics);
 ## 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 mengukur, mendiagnosis, dan mengoptimalkan performa aplikasi web dengan fokus pada **Core Web Vitals** (LCP, INP, CLS), optimasi JavaScript bundle, strategi loading gambar dan font, performa rendering, dan mencapai skor Lighthouse yang tinggi.
@@ -335,4 +336,4 @@ Panduan ahli untuk mengukur, mendiagnosis, dan mengoptimalkan performa aplikasi
 - **INP**: Pecah long task dengan `scheduler.yield()`, gunakan `useTransition` React 19, virtualisasi list panjang.
 - **CLS**: Reservasi ruang untuk gambar dengan `aspect-ratio`, hindari penyisipan konten di atas konten yang sudah ada.
 - **Bundle**: Analisis bundle, gunakan dynamic import, tree-shaking, dan named imports.
-- **Monitoring**: Implementasikan `web-vitals` library untuk melaporkan metrik ke analytics secara real-time.
+- **Monitoring**: Implementasikan `web-vitals` library untuk melaporkan metrik ke analytics secara real-time.

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

@@ -1,7 +1,8 @@
 ---
 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"
+author: "Roedy Rustam"
+version: "3.0.0"
 ---
 
 # Post-Quantum Cryptography Migrator
@@ -54,4 +55,4 @@ Keterampilan arsitek keamanan tingkat lanjut yang dirancang untuk melindungi int
 ## 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).
+- 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,10 +1,11 @@
 ---
 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"
+description: "Updated to cover both pre-code PRD/ERD/Docs generation AND post-code continuous documentation updates / Diperbarui untuk mencakup pembuatan PRD/ERD/Docs pra-kode DAN pembaruan dokumentasi kontinu pasca-kode."
+author: "Roedy Rustam"
+version: "3.0.0"
 ---
 
-# PRD Architect (2026 — PRD-as-Code Edition)
+# PRD Architect & Documentation Lifecycle (2026 Edition)
 
 [English](#english) | [Bahasa Indonesia](#bahasa-indonesia)
 
@@ -14,26 +15,29 @@ 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 with `brainstorming`, `zero-to-prod-orchestrator`, `session-memory-manager` to ensure cohesive execution and documentation updates.
 
 ### 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.
+A mandatory lifecycle guardrail covering two distinct phases:
+- **Phase 1 (Pre-Code):** Enforces creating a comprehensive Product Requirements Document (PRD), ERD, and general Documentation before generating code. Introduces PRD-as-Code — machine-readable and version-controlled.
+- **Phase 2 (Post-Code / Maintenance):** Automatically maintains project documentation after every successful build or feature implementation, updating `CHANGELOG.md`, `BLUEPRINT.md`, `PROGRESS.md`, and Architecture Decision Records (ADRs).
 
 ### Trigger Conditions
-- A user requests building a new application, SaaS, or major feature from scratch.
-- There is no existing PRD, BLUEPRINT.md, or product specification.
-- The project scope is unclear or ambiguous.
-- The user says "build me...", "create a...", "I want to make..." for a new project.
+- **Phase 1:** User requests building a new app/SaaS/feature from scratch; no existing PRD/blueprint; unclear scope.
+- **Phase 2:** A feature, bug fix, or refactor is successfully implemented; user asks to "update docs" or "save progress"; a significant architectural decision is made; milestone completion.
 
-### Why PRD Before Code
-1. **Prevents scope creep**: Defines boundaries before any line of code is written.
-2. **Aligns AI output**: AI agents generate significantly better code when given a structured spec.
-3. **Enables traceability**: Each implemented feature can be traced back to a PRD requirement.
-4. **Reduces rework**: Catches architectural decisions early (DB choice, auth flow, integrations).
-5. **Version-controlled spec**: PRD lives in the repo — changes are tracked and reviewable.
+### Phase 1: Pre-Code Requirements & Enforcement
+**Why PRD Before Code:** Prevents scope creep, aligns AI output, enables traceability, reduces rework, version-controlled.
 
-### PRD-as-Code Template
+#### Enforcement Protocol
+1. **Detect**: When user requests a new project build.
+2. **Pause**: Do NOT generate any code.
+3. **Generate Assets**: Automatically create `PRD.md`, `ERD.md`, `DOKUMENTASI.md`, and `ROADMAP.md` (or `PROGRESS.md`).
+4. **Review**: Present to user for approval/edits.
+5. **Confirm**: Proceed to code generation ONLY after approval.
+6. **Reference**: Cite these documents in all subsequent decisions.
 
+#### PRD-as-Code Template (12 Sections)
 ```markdown
 # Product Requirements Document (PRD)
 **Project**: [Project Name]
@@ -43,111 +47,111 @@ Mandatory guardrail that enforces creating a comprehensive Product Requirements
 **Last Updated**: YYYY-MM-DD
 
 ---
-
 ## 1. Executive Summary
 [2-3 sentences: What is this product? Who is it for? What problem does it solve?]
 
 ## 2. Problem Statement
-**Problem**: [Clear description of the problem being solved]
-**Target Users**: [Specific user segments]
-**Current Pain Points**:
-- Pain point 1
-- Pain point 2
+**Problem**: [Clear description]
+**Target Users**: [Specific segments]
+**Current Pain Points**: [List]
 
 ## 3. Goals & Success Metrics
 | Goal | Metric | Target |
 |---|---|---|
-| Reduce churn | Monthly churn rate | < 5% |
-| Improve activation | D7 retention | > 40% |
+| [Goal] | [Metric] | [Target] |
 
 ## 4. User Personas
 ### Persona 1: [Name]
-- **Role**: [Job title / context]
+- **Role**: [Job title]
 - **Goals**: [What they want to achieve]
 - **Frustrations**: [What currently doesn't work]
 - **Key Behaviors**: [How they'll use this product]
 
 ## 5. Feature Requirements
-
 ### MVP Features (Must Have — v1.0)
 - [ ] **[Feature Name]**: [Description. Acceptance criteria: ...]
-- [ ] **Authentication**: Email/password + Google OAuth. PKCE flow. Session-based.
-- [ ] **Dashboard**: Overview of [key metrics]. Real-time updates via SSE.
-
 ### Phase 2 Features (Should Have — v1.x)
 - [ ] **[Feature Name]**: [Description]
-
 ### Future Features (Nice to Have — v2.0+)
 - [ ] **[Feature Name]**: [Description]
 
 ## 6. Technical Architecture
-
 ### Stack Decision
 | Layer | Technology | Rationale |
 |---|---|---|
-| Frontend | Next.js 15 + React 19 | SSR, App Router, RSC |
-| Backend | Hono + Bun | Type-safe RPC, edge-ready |
-| Database | PostgreSQL + Drizzle ORM | ACID, RLS multi-tenant |
-| Auth | Supabase Auth v3 | PKCE, OAuth, MFA |
-| Payments | Stripe / Polar.sh | [Reason for choice] |
-| Deployment | Vercel + Railway | [Reason for choice] |
-
+| [Layer] | [Technology] | [Reason] |
 ### Architecture Decisions (ADRs)
 - **ADR-001**: [Decision title] — [Decision made and why]
-- **ADR-002**: Multi-tenancy via RLS — Shared schema with Supabase RLS for isolation
-
 ### Multi-Entry Points (if SaaS)
 | Entry Point | Domain | Purpose |
 |---|---|---|
-| Landing Page | `myapp.com` | Marketing, conversion |
-| SaaS App | `app.myapp.com` | Core product |
-| Super Admin | `admin.myapp.com` | Cross-tenant management |
-| API | `api.myapp.com` | Backend (internal + public) |
+| [Entry] | [Domain] | [Purpose] |
 
 ## 7. Data Model (High-Level)
-```
 users ──belongs_to──> workspaces (via workspace_members)
 workspaces ──has_many──> projects
-projects ──has_many──> tasks
-```
 
 ## 8. User Flows
 ### Primary Flow: [Name]
 1. User [action 1]
 2. System [response 1]
-3. User [action 2]
-4. System [response 2] → Success state
 
 ## 9. Non-Functional Requirements
 | Requirement | Target |
 |---|---|
 | Performance | LCP < 2.5s, INP < 200ms |
-| Availability | 99.9% uptime |
-| Security | SOC 2 Type II compliant |
-| Scalability | Support 10K concurrent users |
 
 ## 10. Out of Scope
-- [Explicitly excluded feature or integration]
-- [Another explicitly excluded item]
+- [Explicitly excluded item]
 
 ## 11. Open Questions
-- [ ] [Question that needs a decision before development]
-- [ ] Should we support SSO (SAML) in v1 or defer to v2?
+- [ ] [Question that needs decision]
 
 ## 12. Approval & Sign-off
 | Stakeholder | Role | Status |
 |---|---|---|
-| [Name] | Product | ✅ Approved |
-| [Name] | Engineering | ⏳ Pending |
+| [Name] | [Role] | [Status] |
 ```
 
-### Enforcement Protocol
-1. **Detect**: When user requests a new project build.
-2. **Pause**: Do NOT generate any code.
-3. **Generate PRD, ERD, Docs & Roadmap**: Automatically create a pre-filled PRD draft (`PRD.md`), an Entity Relationship Diagram (`ERD.md`), general Documentation (`DOKUMENTASI.md`), and a Roadmap document (`ROADMAP.md` or `PROGRESS.md`) based on the user's description.
-4. **Review**: Present to user for approval/edits.
-5. **Confirm**: Once the PRD, ERD, Documentation, and Roadmap are approved, proceed to `zero-to-prod-orchestrator` Phase 1.
-6. **Reference**: Cite the PRD, ERD, Documentation, and Roadmap in all subsequent code generation decisions.
+### Phase 2: Post-Code Maintenance & Update Protocol
+
+After every successful feature implementation:
+1. **CHANGELOG.md**: Add entry under `[Unreleased]` (Keep-a-Changelog standard: Added/Changed/Fixed/Removed/Security).
+2. **BLUEPRINT.md**: Update only if architecture, schema, stack, or entry points changed.
+3. **PROGRESS.md**: Mark completed tasks `[x]`, update next steps.
+4. **ADR**: Create a new ADR (`docs/adr/ADR-NNN-title.md`) if a significant architectural decision was made and update index (`docs/adr/README.md`).
+
+#### Files Maintained Frequency Matrix
+| File | Purpose | Update Frequency |
+|---|---|---|
+| `CHANGELOG.md` | User-facing list of changes | Every PR / feature |
+| `BLUEPRINT.md` | Technical architecture overview | Major structural changes |
+| `PROGRESS.md` | Development roadmap and status | Each work session |
+| `docs/adr/` | Architecture Decision Records | Each key decision |
+
+#### ADR Template
+```markdown
+# ADR-001: [Title]
+**Status**: Accepted | Rejected | Proposed | Deprecated
+**Date**: YYYY-MM-DD
+**Deciders**: [Team/Individual]
+## Context
+[What motivated this decision?]
+## Decision
+[What is being decided?]
+## Rationale
+[Why this choice?]
+## Consequences
+**Positive:** / **Negative:**
+## Superseded By
+[ADR-XXX] (if applicable)
+```
+
+### 🎨 Automatic Visual Assets Generation Mandate (CRITICAL)
+**MANDATORY**: When building a new application, use `generate_image` to create a custom logo. Use it as:
+1. The primary application logo (header/navbar).
+2. The website favicon (`favicon.ico`).
+3. The Open Graph (OG) image for SEO (`og:image`).
 
 ---
 
@@ -155,53 +159,25 @@ projects ──has_many──> tasks
 ## 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 dengan `brainstorming`, `zero-to-prod-orchestrator`, `session-memory-manager`.
 
 ### 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.
+Guardrail siklus hidup wajib:
+- **Fase 1 (Pra-Kode):** Memaksa pembuatan PRD, ERD, dan Dokumentasi sebelum kode dibuat.
+- **Fase 2 (Pasca-Kode):** Memelihara dokumentasi setelah setiap fitur sukses: `CHANGELOG.md`, `BLUEPRINT.md`, `PROGRESS.md`, dan ADR.
 
 ### Kondisi Pemicu
-- Pengguna meminta membangun aplikasi, SaaS, atau fitur besar baru dari awal.
-- Tidak ada PRD, BLUEPRINT.md, atau spesifikasi produk yang ada.
-- Ruang lingkup proyek tidak jelas atau ambigu.
-- Pengguna berkata "buatkan saya...", "buat sebuah...", "saya ingin membuat..." untuk proyek baru.
-
-### Mengapa PRD Sebelum Kode
-1. **Mencegah scope creep**: Mendefinisikan batas sebelum satu baris kode pun ditulis.
-2. **Menyelaraskan output AI**: Agen AI menghasilkan kode yang jauh lebih baik saat diberi spesifikasi terstruktur.
-3. **Memungkinkan keterlacakan**: Setiap fitur yang diimplementasikan dapat ditelusuri kembali ke persyaratan PRD.
-4. **Mengurangi pengerjaan ulang**: Menangkap keputusan arsitektur lebih awal (pilihan DB, alur auth, integrasi).
-5. **Spesifikasi dengan kontrol versi**: PRD hidup di repo — perubahan dilacak dan dapat ditinjau.
-
-### Template PRD-as-Code
-Template PRD mencakup 12 bagian:
-1. **Ringkasan Eksekutif**: Apa produk ini, untuk siapa, masalah apa yang diselesaikan.
-2. **Pernyataan Masalah**: Deskripsi masalah yang jelas dengan persona pengguna target.
-3. **Tujuan & Metrik Keberhasilan**: Target terukur yang terkait dengan tujuan bisnis.
-4. **Persona Pengguna**: Peran, tujuan, frustrasi, dan perilaku kunci.
-5. **Persyaratan Fitur**: MVP (Harus Ada), Fase 2 (Sebaiknya Ada), Masa Depan (Bagus Dimiliki).
-6. **Arsitektur Teknis**: Keputusan stack dengan justifikasi, ADR, multi-entry points.
-7. **Model Data**: Hubungan antar entitas tingkat tinggi.
-8. **Alur Pengguna**: Alur langkah-demi-langkah untuk interaksi utama.
-9. **Persyaratan Non-Fungsional**: Performa, ketersediaan, keamanan, skalabilitas.
-10. **Di Luar Ruang Lingkup**: Apa yang secara eksplisit dikecualikan.
-11. **Pertanyaan Terbuka**: Keputusan yang perlu dibuat sebelum pengembangan.
-12. **Persetujuan**: Pemangku kepentingan dan status tanda tangan.
-
-### Protokol Penegakan
-1. **Deteksi**: Saat pengguna meminta pembangunan proyek baru.
-2. **Jeda**: JANGAN hasilkan kode apapun.
-3. **Buat PRD, ERD, Dokumentasi & Roadmap**: Secara otomatis buat draf PRD (`PRD.md`), Entity Relationship Diagram (`ERD.md`), Dokumentasi umum (`DOKUMENTASI.md`), dan dokumen Roadmap (`ROADMAP.md` atau `PROGRESS.md`) yang sudah diisi berdasarkan deskripsi pengguna.
-4. **Tinjau**: Sajikan kepada pengguna untuk persetujuan/edit.
-5. **Konfirmasi**: Setelah PRD, ERD, Dokumentasi, dan Roadmap disetujui, lanjut ke `zero-to-prod-orchestrator` Fase 1.
-6. **Referensi**: Kutip PRD, ERD, Dokumentasi, dan Roadmap dalam semua keputusan pembuatan kode selanjutnya.
+- **Fase 1:** Proyek baru dari awal; tidak ada PRD; ruang lingkup tidak jelas.
+- **Fase 2:** Fitur berhasil; pengguna meminta "perbarui docs"; keputusan arsitektur signifikan.
 
----
-### 🎨 Automatic Visual Assets Generation Mandate (CRITICAL)
-**MANDATORY**: Whenever you are building a new application, scaffolding a project, or finalizing the initial UI/UX, you MUST automatically use the `generate_image` tool to create a custom logo that perfectly matches the application's core concept and aesthetic. 
-This generated image MUST be explicitly used as:
-1. The primary application logo (e.g., in the header/navbar).
-2. The website favicon (`favicon.ico` or equivalent).
-3. The Open Graph (OG) image for SEO metadata (`og:image`).
+### Fase 1: Protokol Penegakan
+1. Deteksi permintaan proyek baru → 2. Jeda (JANGAN kode) → 3. Buat `PRD.md`, `ERD.md`, `DOKUMENTASI.md`, `ROADMAP.md` → 4. Tinjau & setujui → 5. Baru mulai kode → 6. Referensi selalu.
+
+### Fase 2: Pemeliharaan Pasca-Kode
+1. **CHANGELOG.md**: Tambahkan ke `[Unreleased]` (Added/Changed/Fixed/Removed/Security).
+2. **BLUEPRINT.md**: Perbarui jika struktur berubah.
+3. **PROGRESS.md**: Tandai `[x]`, perbarui langkah selanjutnya.
+4. **ADR**: Buat `docs/adr/ADR-NNN-title.md` untuk keputusan besar.
 
-Do not use placeholders for these assets. Generate and integrate them automatically.
+### 🎨 Mandat Aset Visual Otomatis (KRITIS)
+**WAJIB**: Gunakan `generate_image` untuk membuat logo kustom sebagai logo, favicon, dan OG image.

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

@@ -1,7 +1,8 @@
 ---
 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"
+author: "Roedy Rustam"
+version: "3.0.0"
 ---
 
 # Proactive Background Watcher (Sentinel Agent)
@@ -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
 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.
@@ -53,7 +54,7 @@ Activate this skill when:
 ## 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
 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.
@@ -65,4 +66,4 @@ LLM biasa (seperti Claude) sepenuhnya reaktif—diam sampai pengguna mengetik. S
 ### 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.
+- **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.