vibes-plug 2.11.0 → 3.9.0

package/skills/asisten-ramah/SKILL.md

@@ -1,47 +0,0 @@
----
-name: asisten-ramah
-description: "Skill to make Antigravity respond in a friendly manner / Skill untuk membuat Antigravity membalas dengan ramah."
-author: "Roedy Rustam"
----
-
-# Asisten Ramah / Friendly Assistant
-
-[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
-This skill is a basic example to make Antigravity (me) always respond with a friendly, warm, and polite language style.
-
-### Instructions
-- Always start the conversation or response with a friendly greeting (e.g., "Hello!", "Hi there!", or "Ready to help!").
-- Always be polite and use plenty of emojis in responses.
-- If the user asks about code, always provide words of encouragement before presenting the code.
-
-### Trigger Conditions
-Always active for every interaction with the user.
-
----
-
-<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
-Skill ini adalah contoh dasar untuk membuat Antigravity (saya) selalu membalas dengan gaya bahasa tertentu yang ramah dan sopan.
-
-### Instruksi
-- Anda harus selalu memulai percakapan atau jawaban dengan kata sapaan yang ramah (misalnya: "Halo!", "Hai di sana!", atau "Siap membantu!").
-- Selalu bersikap sopan dan gunakan banyak emoji dalam jawaban.
-- Jika pengguna bertanya tentang kode, selalu berikan semangat sebelum memberikan kodenya.
-
-### Kondisi Pemicu
-Selalu aktif untuk setiap interaksi dengan pengguna.

package/skills/auto-doc-updater/SKILL.md

@@ -1,220 +0,0 @@
----
-name: auto-doc-updater
-description: "Automatically documents every feature change or bug fix successfully built into CHANGELOG.md and BLUEPRINT.md / Otomatis mendokumentasikan setiap perubahan fitur atau perbaikan bug yang berhasil di-build ke CHANGELOG.md dan BLUEPRINT.md."
-author: "Roedy Rustam"
----
-
-# Auto Documentation Updater (2026 — ADR Edition)
-
-[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
-Automatically maintains project documentation after every successful build or feature implementation. Updates `CHANGELOG.md`, `BLUEPRINT.md`, and introduces **Architecture Decision Records (ADRs)** — immutable records of key architectural decisions made throughout the project lifecycle.
-
-### Trigger Conditions
-- A feature, bug fix, or refactor has been successfully implemented and verified.
-- The user asks to "update docs", "document this", or "save progress".
-- After completing a phase in `zero-to-prod-orchestrator`.
-- A significant architectural decision was made (DB choice, auth flow, API design).
-
-### Files Maintained
-
-| 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 |
-
-### CHANGELOG.md Format (Keep-a-Changelog Standard)
-```markdown
-# Changelog
-All notable changes to this project will be documented in this file.
-Format based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
-
-## [Unreleased]
-### Added
-- New feature or capability
-
-## [1.2.0] — 2026-07-29
-### Added
-- Super Admin dashboard on `admin.domain.com` with tenant management
-- Polar.sh billing integration as alternative to Stripe
-- `spa-orchestrator` skill for SPA architecture decisions
-
-### Changed
-- Upgraded React to 19.x with new Compiler (removes need for useMemo/useCallback)
-- Migrated from `tailwind.config.js` to CSS-first `@theme` configuration (Tailwind v4)
-
-### Fixed
-- N+1 query issue in workspace members list endpoint
-- Memory leak in WebSocket connection cleanup
-
-### Security
-- Upgraded Supabase client to Auth v3 with PKCE flow (replaces implicit flow)
-- Service role key moved out of client-side code
-
-## [1.1.0] — 2026-06-15
-### Added
-...
-```
-
-### BLUEPRINT.md Structure
-```markdown
-# [Project Name] — Technical Blueprint
-
-## Architecture Overview
-[High-level diagram or description]
-
-## Tech Stack
-| Layer | Technology | Version |
-|---|---|---|
-| Frontend | Next.js | 15.x |
-| Backend | Hono | latest |
-| Database | PostgreSQL + Drizzle | — |
-| Auth | Supabase Auth | v3 |
-
-## Entry Points
-| URL | Purpose |
-|---|---|
-| `domain.com` | Marketing/Landing |
-| `app.domain.com` | SaaS App |
-| `admin.domain.com` | Super Admin |
-
-## Database Schema (Summary)
-[Key tables and relationships]
-
-## API Endpoints (Summary)
-[Key routes and their purposes]
-
-## Environment Variables Required
-[List of all required env vars]
-```
-
-### Architecture Decision Records (ADRs)
-
-ADRs are **immutable records** of significant architectural decisions. Once created, they are never deleted — only superseded by a new ADR. This creates a historical audit trail of *why* the system is built the way it is.
-
-#### ADR Template (`docs/adr/ADR-NNN-title.md`)
-```markdown
-# ADR-001: Use Supabase for Authentication and Database
-
-**Status**: Accepted
-**Date**: 2026-07-29
-**Deciders**: [Team/Individual]
-
-## Context
-[What is the situation that motivated this decision? What forces are at play?]
-
-We need a database + authentication solution for our SaaS MVP that can be
-delivered quickly without managing infrastructure.
-
-## Decision
-We will use Supabase as our primary backend-as-a-service, providing:
-- PostgreSQL database with Row Level Security (RLS)
-- Auth v3 with PKCE flow (OAuth, magic links, MFA)
-- Realtime subscriptions
-- Storage for user-uploaded files
-
-## Rationale
-- Faster time-to-market than self-hosted Postgres + separate auth service
-- Built-in RLS for multi-tenant isolation without custom middleware
-- Open-source — can self-host later if needed
-- Strong TypeScript SDK with auto-generated types
-
-## Consequences
-**Positive:**
-- No auth infrastructure to manage
-- RLS enforced at DB level — defense in depth
-
-**Negative:**
-- Vendor dependency — migration would require significant refactor
-- RLS requires careful testing to avoid data leakage bugs
-
-## Superseded By
-[ADR-XXX: Migrated to self-hosted Supabase] (if applicable)
-```
-
-#### ADR Index (`docs/adr/README.md`)
-```markdown
-# Architecture Decision Records
-
-| # | Title | Status | Date |
-|---|---|---|---|
-| [ADR-001](./ADR-001-supabase-auth.md) | Use Supabase for Auth + DB | ✅ Accepted | 2026-07-29 |
-| [ADR-002](./ADR-002-polar-billing.md) | Use Polar.sh for billing | ✅ Accepted | 2026-07-29 |
-| [ADR-003](./ADR-003-rls-isolation.md) | Shared Schema + RLS for multi-tenancy | ✅ Accepted | 2026-08-01 |
-| [ADR-004](./ADR-004-ssr-vs-spa.md) | Next.js SSR for main app, SPA for admin | 🔄 Proposed | 2026-08-05 |
-```
-
-### Update Protocol
-After every successful feature implementation:
-1. **CHANGELOG.md**: Add entry under `[Unreleased]` with correct category (Added/Changed/Fixed/Security).
-2. **BLUEPRINT.md**: Update only if schema, stack, or entry points changed.
-3. **PROGRESS.md**: Mark completed tasks `[x]`, update next steps.
-4. **ADR**: Create a new ADR if a significant architectural decision was made (DB choice, auth flow, billing provider, deployment strategy, isolation strategy).
-
-### Skill Orchestration & Handoff
-- **Global Listener**: Invoked automatically after completing milestones in `zero-to-prod-orchestrator`, `brainstorming`, `prd-architect`, or any domain expert skill execution.
-- **Context Handoff**: Coordinates with `session-handoff-resume` to ensure checkpoints and documentation are saved before context switching.
-- **Codebase Auditing**: Coordinates with `vibe-code-gardener` to log dead code purges and structural refactors.
-
----
-
-<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
-Secara otomatis memelihara dokumentasi proyek setelah setiap build atau implementasi fitur yang berhasil. Memperbarui `CHANGELOG.md`, `BLUEPRINT.md`, dan memperkenalkan **Architecture Decision Records (ADR)** — catatan permanen dari keputusan arsitektur kunci yang dibuat sepanjang siklus hidup proyek.
-
-### Kondisi Pemicu
-- Sebuah fitur, perbaikan bug, atau refactor berhasil diimplementasikan dan diverifikasi.
-- Pengguna meminta "perbarui docs", "dokumentasikan ini", atau "simpan progres".
-- Setelah menyelesaikan fase dalam `zero-to-prod-orchestrator`.
-- Keputusan arsitektur signifikan dibuat (pilihan DB, alur auth, desain API).
-
-### File yang Dipelihara
-
-| File | Tujuan | Frekuensi Pembaruan |
-|---|---|---|
-| `CHANGELOG.md` | Daftar perubahan untuk pengguna | Setiap PR / fitur |
-| `BLUEPRINT.md` | Gambaran arsitektur teknis | Perubahan struktural besar |
-| `PROGRESS.md` | Roadmap dan status pengembangan | Setiap sesi kerja |
-| `docs/adr/` | Architecture Decision Records | Setiap keputusan kunci |
-
-### Format CHANGELOG.md (Standar Keep-a-Changelog)
-Gunakan kategori: `Added`, `Changed`, `Fixed`, `Removed`, `Security`. Simpan versi yang belum dirilis di bagian `[Unreleased]` dan turunkan ke versi bernama saat rilis.
-
-### Struktur BLUEPRINT.md
-Ringkasan arsitektur teknis termasuk: stack teknologi dengan versi, entry points (URL), skema database (ringkasan), endpoint API kunci, dan variabel lingkungan yang diperlukan.
-
-### Architecture Decision Records (ADR)
-
-ADR adalah **catatan permanen** dari keputusan arsitektur yang signifikan. Setelah dibuat, tidak pernah dihapus — hanya digantikan oleh ADR baru. Ini menciptakan jejak audit historis tentang *mengapa* sistem dibangun seperti yang ada.
-
-Setiap ADR mencakup: Konteks (situasi yang memotivasi keputusan), Keputusan (apa yang diputuskan), Rasional (mengapa), Konsekuensi (positif dan negatif), dan Digantikan Oleh (jika berlaku).
-
-Kelola ADR dengan indeks di `docs/adr/README.md` yang mencantumkan semua ADR dengan status (Diterima, Ditolak, Diusulkan, Usang).
-
-### Protokol Pembaruan
-Setelah setiap implementasi fitur yang berhasil:
-1. **CHANGELOG.md**: Tambahkan entri di `[Unreleased]` dengan kategori yang benar.
-2. **BLUEPRINT.md**: Perbarui hanya jika skema, stack, atau entry points berubah.
-3. **PROGRESS.md**: Tandai tugas selesai `[x]`, perbarui langkah selanjutnya.
-4. **ADR**: Buat ADR baru jika keputusan arsitektur signifikan dibuat.
-
-### Orkestrasi Skill & Serah Terima
-- **Pendengar Global**: Dipanggil secara otomatis setelah menyelesaikan milestone di `zero-to-prod-orchestrator`, `brainstorming`, `prd-architect`, atau skill domain spesialis mana pun.
-- **Serah Terima Konteks**: Berkoordinasi dengan `session-handoff-resume` untuk memastikan checkpoint dan dokumentasi tersimpan sebelum alih konteks.
-- **Audit Codebase**: Berkoordinasi dengan `vibe-code-gardener` untuk mencatat pembersihan dead code dan refactoring struktural.

package/skills/autonomous-chaos-monkey/SKILL.md

@@ -1,63 +0,0 @@
----
-name: autonomous-chaos-monkey
-description: "AI-driven Chaos Engineering. Randomly injects latency, terminates mock services, and automatically implements circuit breakers / Chaos Engineering berbasis AI. Menyuntikkan latensi secara acak, mematikan layanan simulasi, dan secara otomatis menerapkan circuit breaker."
-author: "Roedy Rustam"
----
-
-# Autonomous Chaos Monkey (Resilience Engineering Agent)
-
-[English](#english) | [Bahasa Indonesia](#bahasa-indonesia)
-
----
-
-<a name="english"></a>
-## English
-
-### Description
-Inspired by Netflix's Chaos Monkey, this agent actively tests system resilience by injecting chaos into staging or local development environments. Instead of assuming the network is reliable, it forcibly kills database connections, drops network packets, and injects severe latency into external API calls. It then analyzes the application's failure mode and automatically writes resilience patterns (Circuit Breakers, Retries, Fallback UI) until the system becomes fault-tolerant.
-
-### Trigger Conditions
-- During Phase 7 (DevOps & Production Hardening) before a major launch.
-- When architecting microservices, event-driven systems, or serverless edge databases.
-- When integrating critical external APIs (e.g., Stripe, DOKU, LLM APIs).
-
-### Operating Protocol
-1. **Chaos Injection**: Uses tools like Toxiproxy, Gremlin (via API), or custom network simulation scripts to disrupt connections.
-2. **Observation**: Monitors application logs and user experience (e.g., does it crash? Does the UI hang indefinitely? Does it return a blank screen?).
-3. **Self-Healing Code Generation**: 
-   - Implements Circuit Breaker patterns.
-   - Adds exponential backoff retries.
-   - Implements graceful degradation (e.g., serving cached data or displaying fallback UI states).
-4. **Verification**: Repeats the chaos injection until the system can survive the disruption without severe user impact.
-
-## Orchestration & Integration
-- Connects to `error-resilience-expert` to implement the actual React Error Boundaries and Circuit Breaker logic.
-- Integrates with `logging-error-tracking-expert` to verify that injected chaos is properly logged and captured in Sentry.
-- Validates the resilience of `async-queue-temporal-expert` workflows during worker outages.
-
----
-
-<a name="bahasa-indonesia"></a>
-## Bahasa Indonesia
-
-### Deskripsi
-Terinspirasi dari Chaos Monkey milik Netflix, agen ini secara aktif menguji ketahanan sistem dengan menyuntikkan kekacauan (*chaos*) ke dalam lingkungan staging atau pengembangan lokal. Alih-alih berasumsi bahwa jaringan selalu stabil, agen ini secara paksa mematikan koneksi database, membuang paket jaringan, dan menyuntikkan latensi parah pada pemanggilan API eksternal. Kemudian, ia menganalisis mode kegagalan aplikasi dan secara otomatis menulis pola ketahanan (*Circuit Breakers*, *Retries*, *Fallback UI*) sampai sistem kebal terhadap gangguan.
-
-### Kondisi Pemicu
-- Saat Fase 7 (DevOps & Pengerasan Produksi) sebelum peluncuran besar.
-- Saat merancang arsitektur microservices, sistem event-driven, atau database serverless.
-- Saat mengintegrasikan API eksternal kritis (misalnya Stripe, DOKU, API LLM).
-
-### Protokol Operasi
-1. **Injeksi Kekacauan**: Menggunakan alat seperti Toxiproxy, Gremlin (via API), atau skrip simulasi jaringan kustom untuk mengganggu koneksi.
-2. **Observasi**: Memantau log aplikasi dan pengalaman pengguna (misal: apakah aplikasi *crash*? Apakah UI macet tanpa batas waktu? Apakah menampilkan layar kosong?).
-3. **Generasi Kode Self-Healing**: 
-   - Menerapkan pola Circuit Breaker.
-   - Menambahkan mekanisme *retry* dengan *exponential backoff*.
-   - Menerapkan degradasi anggun (*graceful degradation*), seperti menyajikan data dari *cache* atau menampilkan state UI pengganti.
-4. **Verifikasi**: Mengulangi injeksi kekacauan hingga sistem mampu bertahan dari gangguan tanpa berdampak fatal pada pengguna.
-
-## Integrasi Orkestrasi
-- Terhubung dengan `error-resilience-expert` untuk mengimplementasikan logika React Error Boundaries dan Circuit Breaker yang sesungguhnya.
-- Terintegrasi dengan `logging-error-tracking-expert` untuk memastikan bahwa kekacauan yang disuntikkan dicatat dengan benar dan terekam di Sentry.
-- Memvalidasi ketahanan alur kerja `async-queue-temporal-expert` selama pekerja (*worker*) mengalami pemadaman.

package/skills/background-jobs-queue-expert/SKILL.md

@@ -1,235 +0,0 @@
----
-name: background-jobs-queue-expert
-description: "Dedicated deep-dive for BullMQ v5, Trigger.dev v3, Inngest, delayed jobs, job deduplication, idempotency, dead letter queues, and job priority / Panduan mendalam untuk BullMQ v5, Trigger.dev v3, Inngest, delayed jobs, deduplikasi job, idempotency, dead letter queue, dan prioritas job."
-author: "Roedy Rustam"
----
-
-# Background Jobs & Queue Expert (BullMQ v5 & Resilient Queues)
-
-[English](#english) | [Bahasa Indonesia](#bahasa-indonesia)
-
----
-
-<a name="english"></a>
-## English
-
-### Purpose & Overview
-Production-grade engineering guide for background job queues and asynchronous task processing using **BullMQ v5**, **Trigger.dev v3**, and **Inngest**. Focuses on the core mechanics of fault-tolerant distributed queues: job deduplication, multi-tenant priority queues, exponential backoff jitter, Dead Letter Queue (DLQ) automated forwarding, and strict transactional idempotency.
-
-### Key Capabilities
-1. **Strict Idempotency**: Ensuring background workers execute with deterministic effects using database-backed idempotency keys.
-2. **Job Deduplication**: Leveraging deterministic BullMQ `jobId` hashing to prevent duplicate enqueueing of ongoing or delayed tasks.
-3. **Dead Letter Queues (DLQ)**: Automatic relocation of permanently failing jobs after retry exhaustion for manual inspection and alerting.
-4. **Tenant Prioritization**: Differentiating throughput between VIP/enterprise tiers and free-tier users using BullMQ job priorities.
-5. **Backoff Jitter & Throttling**: Exponential backoff combined with randomized full jitter to prevent upstream thundering herds.
-
----
-
-### Production Implementation Recipes
-
-#### Recipe 1: Production BullMQ v5 Worker with Deduplication & DLQ Forwarding (TypeScript)
-```typescript
-import { Queue, Worker, Job } from 'bullmq';
-import Redis from 'ioredis';
-
-const redisConnection = new Redis(process.env.REDIS_URL || 'redis://localhost:6379', {
-  maxRetriesPerRequest: null, // Required by BullMQ
-});
-
-export interface NotificationPayload {
-  tenantId: string;
-  userId: string;
-  type: 'email' | 'webhook';
-  payload: Record<string, unknown>;
-  idempotencyKey: string;
-}
-
-// Main Queue
-export const notificationQueue = new Queue<NotificationPayload>('notifications', {
-  connection: redisConnection,
-  defaultJobOptions: {
-    attempts: 5,
-    backoff: {
-      type: 'exponential',
-      delay: 1500, // Starts at 1.5s, doubles up to ~24s with jitter
-    },
-    removeOnComplete: { age: 86400, count: 5000 },
-    removeOnFail: false, // Preserved for DLQ audit
-  },
-});
-
-// Dead Letter Queue (DLQ)
-export const notificationDLQ = new Queue('notifications-dlq', {
-  connection: redisConnection,
-});
-
-/**
- * Enqueues a notification job with strict deduplication and priority
- */
-export async function enqueueNotification(
-  data: NotificationPayload,
-  isVip = false
-) {
-  return await notificationQueue.add('send_notification', data, {
-    jobId: `notif_${data.idempotencyKey}`, // Deterministic deduplication key
-    priority: isVip ? 1 : 10, // Lower numbers denote higher priority in BullMQ
-  });
-}
-
-// Background Worker
-export const notificationWorker = new Worker<NotificationPayload>(
-  'notifications',
-  async (job: Job<NotificationPayload>) => {
-    console.log(`[Worker] Processing Job ${job.id} for Tenant: ${job.data.tenantId}`);
-    
-    // Simulate task processing with idempotency verification
-    if (job.data.type === 'email') {
-      await deliverEmail(job.data);
-    }
-  },
-  {
-    connection: redisConnection,
-    concurrency: 20, // Max concurrent jobs per worker process
-    limiter: {
-      max: 100, // Maximum 100 jobs processed
-      duration: 1000, // Per 1000ms (Rate Limiting)
-    },
-  }
-);
-
-// Forward to DLQ upon exhaustion of retry attempts
-notificationWorker.on('failed', async (job, error) => {
-  if (job && job.attemptsMade >= (job.opts.attempts || 5)) {
-    console.error(`[DLQ] Job ${job.id} exhausted retries. Forwarding to notifications-dlq:`, error.message);
-    await notificationDLQ.add('failed_notification', {
-      originalJobId: job.id,
-      failedReason: error.message,
-      data: job.data,
-      exhaustedAt: new Date().toISOString(),
-    });
-  }
-});
-```
-
----
-
-### Implementation Checklist
-- [ ] Configure `maxRetriesPerRequest: null` on the Redis client as required by BullMQ v5.
-- [ ] Use deterministic `jobId` derived from business logic (`order_${orderId}`) to enforce deduplication.
-- [ ] Add event listener on `failed` to automatically forward permanently dead jobs to a Dead Letter Queue.
-- [ ] Implement rate limiting using worker `limiter` to protect third-party services against rate-limit bans.
-
-## Orchestration & Integration
-- Integrates with: `js-backend-expert`, `async-queue-temporal-expert`, `error-resilience-expert`, `data-telemetry-expert`.
-
----
-
-<a name="bahasa-indonesia"></a>
-## Bahasa Indonesia
-
-### Tujuan & Gambaran Umum
-Panduan rekayasa tingkat produksi untuk antrean pekerjaan latar belakang (*background job queues*) dan pemrosesan tugas asinkron menggunakan **BullMQ v5**, **Trigger.dev v3**, dan **Inngest**. Berfokus pada mekanika inti antrean terdistribusi yang tangguh: deduplikasi job, prioritas multi-tenant, *exponential backoff jitter*, pemindahan otomatis ke Dead Letter Queue (DLQ), dan idempotensi transaksi yang ketat.
-
-### Kemampuan Utama
-1. **Idempotensi Ketat**: Memastikan pekerja (*worker*) mengeksekusi tugas dengan dampak deterministik menggunakan kunci idempotensi yang tercatat di database.
-2. **Deduplikasi Job**: Memanfaatkan penetapan `jobId` deterministik di BullMQ untuk mencegah antrean ganda pada tugas yang sedang berjalan atau tertunda.
-3. **Dead Letter Queue (DLQ)**: Pemindahan otomatis tugas yang gagal total setelah jatah percobaan ulang habis untuk audit dan penanganan manual.
-4. **Prioritas Tenant**: Membedakan prioritas tugas antara pengguna VIP/Enterprise dengan pengguna paket gratis menggunakan nilai prioritas BullMQ.
-5. **Backoff Jitter & Throttling**: Mekanisme penundaan eksponensial dengan *jitter* acak untuk mencegah fenomena *thundering herd* pada server hilir.
-
----
-
-### Resep Implementasi Produksi
-
-#### Resep 1: Worker BullMQ v5 Produksi dengan Deduplikasi & Forward DLQ (TypeScript)
-```typescript
-import { Queue, Worker, Job } from 'bullmq';
-import Redis from 'ioredis';
-
-const koneksiRedis = new Redis(process.env.REDIS_URL || 'redis://localhost:6379', {
-  maxRetriesPerRequest: null,
-});
-
-export interface MuatanNotifikasi {
-  tenantId: string;
-  userId: string;
-  type: 'email' | 'webhook';
-  payload: Record<string, unknown>;
-  idempotencyKey: string;
-}
-
-// Antrean Utama
-export const antreanNotifikasi = new Queue<MuatanNotifikasi>('notifikasi', {
-  connection: koneksiRedis,
-  defaultJobOptions: {
-    attempts: 5,
-    backoff: {
-      type: 'exponential',
-      delay: 1500,
-    },
-    removeOnComplete: { age: 86400, count: 5000 },
-    removeOnFail: false,
-  },
-});
-
-// Antrean Dead Letter (DLQ)
-export const antreanDLQ = new Queue('notifikasi-dlq', {
-  connection: koneksiRedis,
-});
-
-/**
- * Memasukkan tugas ke antrean dengan deduplikasi dan prioritas
- */
-export async function masukkanNotifikasi(
-  data: MuatanNotifikasi,
-  isVip = false
-) {
-  return await antreanNotifikasi.add('kirim_notifikasi', data, {
-    jobId: `notif_${data.idempotencyKey}`, // Kunci deduplikasi unik
-    priority: isVip ? 1 : 10, // Nilai lebih kecil menandakan prioritas lebih tinggi
-  });
-}
-
-// Worker Pemroses
-export const workerNotifikasi = new Worker<MuatanNotifikasi>(
-  'notifikasi',
-  async (job: Job<MuatanNotifikasi>) => {
-    console.log(`[Worker] Memproses Job ${job.id} untuk Tenant: ${job.data.tenantId}`);
-    if (job.data.type === 'email') {
-      await kirimEmail(job.data);
-    }
-  },
-  {
-    connection: koneksiRedis,
-    concurrency: 20,
-    limiter: {
-      max: 100,
-      duration: 1000,
-    },
-  }
-);
-
-// Teruskan ke DLQ jika jatah retry telah habis
-workerNotifikasi.on('failed', async (job, error) => {
-  if (job && job.attemptsMade >= (job.opts.attempts || 5)) {
-    console.error(`[DLQ] Job ${job.id} gagal total. Memindahkan ke DLQ:`, error.message);
-    await antreanDLQ.add('notifikasi_gagal', {
-      originalJobId: job.id,
-      failedReason: error.message,
-      data: job.data,
-      exhaustedAt: new Date().toISOString(),
-    });
-  }
-});
-```
-
----
-
-### Checklist Implementasi
-- [ ] Atur konfigurasi `maxRetriesPerRequest: null` pada koneksi ioredis untuk BullMQ v5.
-- [ ] Gunakan `jobId` deterministik dari ID transaksi bisnis (`invoice_${invoiceId}`) untuk mencegah duplikasi.
-- [ ] Pasang *event listener* pada event `failed` untuk meneruskan job yang gagal total ke antrean DLQ.
-- [ ] Terapkan pembatasan *rate limiter* pada worker untuk menjaga kestabilan API eksternal.
-
-## Integrasi Orkestrasi
-- Terintegrasi dengan: `js-backend-expert`, `async-queue-temporal-expert`, `error-resilience-expert`, `data-telemetry-expert`.

package/skills/bootstrap-to-modern/SKILL.md

@@ -1,94 +0,0 @@
----
-name: bootstrap-to-modern
-description: "Expert skill to refactor and migrate legacy Bootstrap CSS applications to modern stacks using Tailwind CSS v4 and Alpine.js / Skill ahli untuk melakukan refaktor dan migrasi aplikasi Bootstrap CSS lama ke stack modern menggunakan Tailwind CSS v4 dan Alpine.js."
-author: "Roedy Rustam"
----
-
-# Bootstrap to Modern (Tailwind + Alpine.js) / Refaktor Bootstrap ke Modern
-
-[English](#english) | [Bahasa Indonesia](#bahasa-indonesia)
-
----
-
-<a name="english"></a>
-## English
-
-### Description
-This skill transforms legacy web applications styled with Bootstrap (jQuery-dependent or pure CSS) into a modern, utility-first architecture using **Tailwind CSS v4** for styling and **Alpine.js** for lightweight reactive behavior.
-
-### Instructions
-1. **Analyze the Legacy Structure**:
-   - Identify the version of Bootstrap being used.
-   - Locate custom CSS files that override Bootstrap defaults.
-   - Identify interactive components (modals, dropdowns, tooltips, tabs, carousels) that rely on Bootstrap's JavaScript or jQuery.
-2. **Setup Modern Tools**:
-   - Ensure **Tailwind CSS v4** is properly set up in the project (e.g., via CDN for simple projects, or PostCSS/Vite for build steps).
-   - Inject **Alpine.js** via CDN or module bundler to handle interactivity.
-3. **Migration Strategy**:
-   - **Grid & Layout**: Convert Bootstrap grids (`container`, `row`, `col-*`) to Tailwind flexbox (`flex`, `flex-col`, `gap-*`) or CSS Grid (`grid`, `grid-cols-*`).
-   - **Spacing & Typography**: Map Bootstrap spacing (`m-3`, `p-4`) to Tailwind spacing (`m-4`, `p-6`—noting scale differences). Map typography utilities (`text-center`, `font-weight-bold`) to Tailwind equivalents (`text-center`, `font-bold`).
-   - **Colors**: Update Bootstrap semantic colors (`primary`, `success`, `danger`) to Tailwind color palettes (e.g., `blue-600`, `green-500`, `red-500`) or define custom themes in CSS variables for Tailwind v4.
-   - **Components**: Rebuild Bootstrap components (cards, buttons, alerts, navbars) using Tailwind utility classes to match or improve the original design.
-4. **Interactivity with Alpine.js**:
-   - Remove jQuery and Bootstrap JS dependencies.
-   - Replace interactive Bootstrap components with Alpine.js data and directives.
-   - **Dropdowns**: Use `x-data="{ open: false }"` and `@click="open = !open"`.
-   - **Modals**: Use Alpine.js to manage the open state and handle background overlays and click-away events (`@click.outside`).
-   - **Tabs**: Manage active tab state with `x-data="{ tab: 'home' }"`.
-5. **UI/UX Modernization & Skill Integration**:
-   - Do NOT just do a 1:1 translation of Bootstrap classes. The goal is to elevate the design.
-   - You MUST orchestrate and apply guidelines from other UI/UX skills (`ui-ux-expert`, `ui-ux-pro-max`, and `hig`).
-   - Implement Human Interface Guidelines (HIG) principles: Hierarchy, Harmony, and Consistency.
-   - Use vibrant colors, smooth micro-animations, glassmorphism (if appropriate), and modern typography to "WOW" the user.
-6. **Quality Assurance**:
-   - Verify that responsive design behaves correctly across breakpoints (`sm:`, `md:`, `lg:`).
-   - Ensure interactive components (modals, dropdowns) feel premium with Alpine.js transitions (`x-transition`).
-
-### Trigger Conditions
-Active whenever the user asks to migrate, refactor, or update a Bootstrap project to Tailwind CSS, or modernize legacy CSS/JS.
-
----
-
-<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
-Skill ini mengubah aplikasi web lama yang di-style dengan Bootstrap (baik yang bergantung pada jQuery maupun murni CSS) menjadi arsitektur modern berbasis utility menggunakan **Tailwind CSS v4** untuk styling dan **Alpine.js** untuk behavior reaktif yang ringan.
-
-### Instruksi
-1. **Analisis Struktur Lama**:
-   - Identifikasi versi Bootstrap yang digunakan.
-   - Temukan file CSS kustom yang menimpa (override) default Bootstrap.
-   - Identifikasi komponen interaktif (modal, dropdown, tooltip, tab, carousel) yang mengandalkan JavaScript Bootstrap atau jQuery.
-2. **Setup Tools Modern**:
-   - Pastikan **Tailwind CSS v4** disiapkan dengan benar di proyek (misalnya, melalui CDN untuk proyek sederhana, atau PostCSS/Vite jika ada build step).
-   - Masukkan **Alpine.js** melalui CDN atau module bundler untuk menangani interaktivitas.
-3. **Strategi Migrasi**:
-   - **Grid & Layout**: Ubah grid Bootstrap (`container`, `row`, `col-*`) menjadi flexbox Tailwind (`flex`, `flex-col`, `gap-*`) atau CSS Grid (`grid`, `grid-cols-*`).
-   - **Spacing & Tipografi**: Petakan spasi Bootstrap (`m-3`, `p-4`) ke Tailwind (`m-4`, `p-6`—perhatikan perbedaan skala). Petakan utilitas teks (`text-center`, `font-weight-bold`) ke padanan Tailwind (`text-center`, `font-bold`).
-   - **Warna**: Perbarui warna semantik Bootstrap (`primary`, `success`, `danger`) ke palet warna Tailwind (misal: `blue-600`, `green-500`, `red-500`) atau definisikan tema kustom di variabel CSS untuk Tailwind v4.
-   - **Komponen**: Bangun ulang komponen Bootstrap (card, button, alert, navbar) menggunakan kelas utilitas Tailwind untuk mencocokkan atau memperbaiki desain aslinya.
-4. **Interaktivitas dengan Alpine.js**:
-   - Hapus dependensi jQuery dan Bootstrap JS.
-   - Ganti komponen interaktif Bootstrap dengan data dan direktif Alpine.js.
-   - **Dropdown**: Gunakan `x-data="{ open: false }"` dan `@click="open = !open"`.
-   - **Modal**: Gunakan Alpine.js untuk mengelola state terbuka, overlay latar belakang, dan event klik di luar (`@click.outside`).
-   - **Tab**: Kelola state tab aktif dengan `x-data="{ tab: 'home' }"`.
-5. **Modernisasi UI/UX & Integrasi Skill**:
-   - JANGAN hanya menerjemahkan kelas Bootstrap 1:1. Tujuannya adalah meningkatkan kualitas desain.
-   - Anda WAJIB mengorkestrasi dan menerapkan pedoman dari skill UI/UX lainnya (`ui-ux-expert`, `ui-ux-pro-max`, dan `hig`).
-   - Terapkan prinsip Human Interface Guidelines (HIG): Hierarchy, Harmony, dan Consistency.
-   - Gunakan warna cerah, mikro-animasi halus, glassmorphism (jika sesuai), dan tipografi modern untuk memberikan kesan "WOW" pada pengguna.
-6. **Quality Assurance**:
-   - Verifikasi bahwa desain responsif berfungsi dengan benar di semua breakpoint (`sm:`, `md:`, `lg:`).
-   - Pastikan komponen interaktif (modal, dropdown) terasa premium dengan transisi Alpine.js (`x-transition`).
-
-### Kondisi Pemicu
-Aktif setiap kali pengguna meminta untuk memigrasi, merefaktor, atau memperbarui proyek Bootstrap ke Tailwind CSS, atau memodernisasi CSS/JS lama.
-
-
-## Orchestration & Integration
-- Integrates with: `ui-ux-expert`, `ui-ux-pro-max`, `hig`.