vibes-plug 2.14.1 → 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,182 +1,183 @@
----
-name: prd-architect
-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"
----
-
-# PRD Architect & Documentation Lifecycle (2026 Edition)
-
-[English](#english) | [Bahasa Indonesia](#bahasa-indonesia)
-
----
-
-<a name="english"></a>
-## English
-
-### Orchestration & Integration
-Connects with `brainstorming`, `zero-to-prod-orchestrator`, `session-memory-manager` to ensure cohesive execution and documentation updates.
-
-### Description
-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
-- **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.
-
-### Phase 1: Pre-Code Requirements & Enforcement
-**Why PRD Before Code:** Prevents scope creep, aligns AI output, enables traceability, reduces rework, version-controlled.
-
-#### 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]
-**Version**: 1.0.0
-**Status**: Draft | In Review | Approved
-**Created**: YYYY-MM-DD
-**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]
-**Target Users**: [Specific segments]
-**Current Pain Points**: [List]
-
-## 3. Goals & Success Metrics
-| Goal | Metric | Target |
-|---|---|---|
-| [Goal] | [Metric] | [Target] |
-
-## 4. User Personas
-### Persona 1: [Name]
-- **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: ...]
-### 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 |
-|---|---|---|
-| [Layer] | [Technology] | [Reason] |
-### Architecture Decisions (ADRs)
-- **ADR-001**: [Decision title] — [Decision made and why]
-### Multi-Entry Points (if SaaS)
-| Entry Point | Domain | Purpose |
-|---|---|---|
-| [Entry] | [Domain] | [Purpose] |
-
-## 7. Data Model (High-Level)
-users ──belongs_to──> workspaces (via workspace_members)
-workspaces ──has_many──> projects
-
-## 8. User Flows
-### Primary Flow: [Name]
-1. User [action 1]
-2. System [response 1]
-
-## 9. Non-Functional Requirements
-| Requirement | Target |
-|---|---|
-| Performance | LCP < 2.5s, INP < 200ms |
-
-## 10. Out of Scope
-- [Explicitly excluded item]
-
-## 11. Open Questions
-- [ ] [Question that needs decision]
-
-## 12. Approval & Sign-off
-| Stakeholder | Role | Status |
-|---|---|---|
-| [Name] | [Role] | [Status] |
-```
-
-### 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`).
-
----
-
-<a name="bahasa-indonesia"></a>
-## Bahasa Indonesia
-
-### Integrasi Orkestrasi
-Terhubung dengan `brainstorming`, `zero-to-prod-orchestrator`, `session-memory-manager`.
-
-### Deskripsi
-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
-- **Fase 1:** Proyek baru dari awal; tidak ada PRD; ruang lingkup tidak jelas.
-- **Fase 2:** Fitur berhasil; pengguna meminta "perbarui docs"; keputusan arsitektur signifikan.
-
-### 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.
-
-### 🎨 Mandat Aset Visual Otomatis (KRITIS)
-**WAJIB**: Gunakan `generate_image` untuk membuat logo kustom sebagai logo, favicon, dan OG image.
+---
+name: prd-architect
+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 & Documentation Lifecycle (2026 Edition)
+
+[English](#english) | [Bahasa Indonesia](#bahasa-indonesia)
+
+---
+
+<a name="english"></a>
+## English
+
+### Orchestration & Integration
+Connects with `brainstorming`, `zero-to-prod-orchestrator`, `session-memory-manager` to ensure cohesive execution and documentation updates.
+
+### Description
+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
+- **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.
+
+### Phase 1: Pre-Code Requirements & Enforcement
+**Why PRD Before Code:** Prevents scope creep, aligns AI output, enables traceability, reduces rework, version-controlled.
+
+#### 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]
+**Version**: 1.0.0
+**Status**: Draft | In Review | Approved
+**Created**: YYYY-MM-DD
+**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]
+**Target Users**: [Specific segments]
+**Current Pain Points**: [List]
+
+## 3. Goals & Success Metrics
+| Goal | Metric | Target |
+|---|---|---|
+| [Goal] | [Metric] | [Target] |
+
+## 4. User Personas
+### Persona 1: [Name]
+- **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: ...]
+### 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 |
+|---|---|---|
+| [Layer] | [Technology] | [Reason] |
+### Architecture Decisions (ADRs)
+- **ADR-001**: [Decision title] — [Decision made and why]
+### Multi-Entry Points (if SaaS)
+| Entry Point | Domain | Purpose |
+|---|---|---|
+| [Entry] | [Domain] | [Purpose] |
+
+## 7. Data Model (High-Level)
+users ──belongs_to──> workspaces (via workspace_members)
+workspaces ──has_many──> projects
+
+## 8. User Flows
+### Primary Flow: [Name]
+1. User [action 1]
+2. System [response 1]
+
+## 9. Non-Functional Requirements
+| Requirement | Target |
+|---|---|
+| Performance | LCP < 2.5s, INP < 200ms |
+
+## 10. Out of Scope
+- [Explicitly excluded item]
+
+## 11. Open Questions
+- [ ] [Question that needs decision]
+
+## 12. Approval & Sign-off
+| Stakeholder | Role | Status |
+|---|---|---|
+| [Name] | [Role] | [Status] |
+```
+
+### 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`).
+
+---
+
+<a name="bahasa-indonesia"></a>
+## Bahasa Indonesia
+
+### Integrasi Orkestrasi
+Terhubung dengan `brainstorming`, `zero-to-prod-orchestrator`, `session-memory-manager`.
+
+### Deskripsi
+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
+- **Fase 1:** Proyek baru dari awal; tidak ada PRD; ruang lingkup tidak jelas.
+- **Fase 2:** Fitur berhasil; pengguna meminta "perbarui docs"; keputusan arsitektur signifikan.
+
+### 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.
+
+### 🎨 Mandat Aset Visual Otomatis (KRITIS)
+**WAJIB**: Gunakan `generate_image` untuk membuat logo kustom sebagai logo, favicon, dan OG image.