codehava-agent-kit 1.0.0

package/templates/.agent/workflows/test.md

@@ -0,0 +1,144 @@
+---
+description: Test generation and test running command. Creates and executes tests for code.
+---
+
+# /test - Test Generation and Execution
+
+$ARGUMENTS
+
+---
+
+## Purpose
+
+This command generates tests, runs existing tests, or checks test coverage.
+
+---
+
+## Sub-commands
+
+```
+/test                - Run all tests
+/test [file/feature] - Generate tests for specific target
+/test coverage       - Show test coverage report
+/test watch          - Run tests in watch mode
+```
+
+---
+
+## Behavior
+
+### Generate Tests
+
+When asked to test a file or feature:
+
+1. **Analyze the code**
+   - Identify functions and methods
+   - Find edge cases
+   - Detect dependencies to mock
+
+2. **Generate test cases**
+   - Happy path tests
+   - Error cases
+   - Edge cases
+   - Integration tests (if needed)
+
+3. **Write tests**
+   - Use project's test framework (Jest, Vitest, etc.)
+   - Follow existing test patterns
+   - Mock external dependencies
+
+---
+
+## Output Format
+
+### For Test Generation
+
+```markdown
+## 🧪 Tests: [Target]
+
+### Test Plan
+| Test Case | Type | Coverage |
+|-----------|------|----------|
+| Should create user | Unit | Happy path |
+| Should reject invalid email | Unit | Validation |
+| Should handle db error | Unit | Error case |
+
+### Generated Tests
+
+`tests/[file].test.ts`
+
+[Code block with tests]
+
+---
+
+Run with: `npm test`
+```
+
+### For Test Execution
+
+```
+🧪 Running tests...
+
+✅ auth.test.ts (5 passed)
+✅ user.test.ts (8 passed)
+❌ order.test.ts (2 passed, 1 failed)
+
+Failed:
+  ✗ should calculate total with discount
+    Expected: 90
+    Received: 100
+
+Total: 15 tests (14 passed, 1 failed)
+```
+
+---
+
+## Examples
+
+```
+/test src/services/auth.service.ts
+/test user registration flow
+/test coverage
+/test fix failed tests
+```
+
+---
+
+## Test Patterns
+
+### Unit Test Structure
+
+```typescript
+describe('AuthService', () => {
+  describe('login', () => {
+    it('should return token for valid credentials', async () => {
+      // Arrange
+      const credentials = { email: 'test@test.com', password: 'pass123' };
+      
+      // Act
+      const result = await authService.login(credentials);
+      
+      // Assert
+      expect(result.token).toBeDefined();
+    });
+
+    it('should throw for invalid password', async () => {
+      // Arrange
+      const credentials = { email: 'test@test.com', password: 'wrong' };
+      
+      // Act & Assert
+      await expect(authService.login(credentials)).rejects.toThrow('Invalid credentials');
+    });
+  });
+});
+```
+
+---
+
+## Key Principles
+
+- **Test behavior not implementation**
+- **One assertion per test** (when practical)
+- **Descriptive test names**
+- **Arrange-Act-Assert pattern**
+- **Mock external dependencies**

package/templates/.agent/workflows/ui-ux-pro-max.md

@@ -0,0 +1,296 @@
+---
+description: Plan and implement UI
+---
+
+---
+description: AI-powered design intelligence with 50+ styles, 95+ color palettes, and automated design system generation
+---
+
+# ui-ux-pro-max
+
+Comprehensive design guide for web and mobile applications. Contains 50+ styles, 97 color palettes, 57 font pairings, 99 UX guidelines, and 25 chart types across 9 technology stacks. Searchable database with priority-based recommendations.
+
+## Prerequisites
+
+Check if Python is installed:
+
+```bash
+python3 --version || python --version
+```
+
+If Python is not installed, install it based on user's OS:
+
+**macOS:**
+```bash
+brew install python3
+```
+
+**Ubuntu/Debian:**
+```bash
+sudo apt update && sudo apt install python3
+```
+
+**Windows:**
+```powershell
+winget install Python.Python.3.12
+```
+
+---
+
+## How to Use This Workflow
+
+When user requests UI/UX work (design, build, create, implement, review, fix, improve), follow this workflow:
+
+### Step 1: Analyze User Requirements
+
+Extract key information from user request:
+- **Product type**: SaaS, e-commerce, portfolio, dashboard, landing page, etc.
+- **Style keywords**: minimal, playful, professional, elegant, dark mode, etc.
+- **Industry**: healthcare, fintech, gaming, education, etc.
+- **Stack**: React, Vue, Next.js, or default to `html-tailwind`
+
+### Step 2: Generate Design System (REQUIRED)
+
+**Always start with `--design-system`** to get comprehensive recommendations with reasoning:
+
+```bash
+python3 .agent/.shared/ui-ux-pro-max/scripts/search.py "<product_type> <industry> <keywords>" --design-system [-p "Project Name"]
+```
+
+This command:
+1. Searches 5 domains in parallel (product, style, color, landing, typography)
+2. Applies reasoning rules from `ui-reasoning.csv` to select best matches
+3. Returns complete design system: pattern, style, colors, typography, effects
+4. Includes anti-patterns to avoid
+
+**Example:**
+```bash
+python3 .agent/.shared/ui-ux-pro-max/scripts/search.py "beauty spa wellness service" --design-system -p "Serenity Spa"
+```
+
+### Step 2b: Persist Design System (Master + Overrides Pattern)
+
+To save the design system for hierarchical retrieval across sessions, add `--persist`:
+
+```bash
+python3 .agent/.shared/ui-ux-pro-max/scripts/search.py "<query>" --design-system --persist -p "Project Name"
+```
+
+This creates:
+- `design-system/MASTER.md` — Global Source of Truth with all design rules
+- `design-system/pages/` — Folder for page-specific overrides
+
+**With page-specific override:**
+```bash
+python3 .agent/.shared/ui-ux-pro-max/scripts/search.py "<query>" --design-system --persist -p "Project Name" --page "dashboard"
+```
+
+This also creates:
+- `design-system/pages/dashboard.md` — Page-specific deviations from Master
+
+**How hierarchical retrieval works:**
+1. When building a specific page (e.g., "Checkout"), first check `design-system/pages/checkout.md`
+2. If the page file exists, its rules **override** the Master file
+3. If not, use `design-system/MASTER.md` exclusively
+
+### Step 3: Supplement with Detailed Searches (as needed)
+
+After getting the design system, use domain searches to get additional details:
+
+```bash
+python3 .agent/.shared/ui-ux-pro-max/scripts/search.py "<keyword>" --domain <domain> [-n <max_results>]
+```
+
+**When to use detailed searches:**
+
+| Need | Domain | Example |
+|------|--------|---------|
+| More style options | `style` | `--domain style "glassmorphism dark"` |
+| Chart recommendations | `chart` | `--domain chart "real-time dashboard"` |
+| UX best practices | `ux` | `--domain ux "animation accessibility"` |
+| Alternative fonts | `typography` | `--domain typography "elegant luxury"` |
+| Landing structure | `landing` | `--domain landing "hero social-proof"` |
+
+### Step 4: Stack Guidelines (Default: html-tailwind)
+
+Get implementation-specific best practices. If user doesn't specify a stack, **default to `html-tailwind`**.
+
+```bash
+python3 .agent/.shared/ui-ux-pro-max/scripts/search.py "<keyword>" --stack html-tailwind
+```
+
+Available stacks: `html-tailwind`, `react`, `nextjs`, `vue`, `svelte`, `swiftui`, `react-native`, `flutter`, `shadcn`, `jetpack-compose`
+, `jetpack-compose`
+---
+
+## Search Reference
+
+### Available Domains
+
+| Domain | Use For | Example Keywords |
+|--------|---------|------------------|
+| `product` | Product type recommendations | SaaS, e-commerce, portfolio, healthcare, beauty, service |
+| `style` | UI styles, colors, effects | glassmorphism, minimalism, dark mode, brutalism |
+| `typography` | Font pairings, Google Fonts | elegant, playful, professional, modern |
+| `color` | Color palettes by product type | saas, ecommerce, healthcare, beauty, fintech, service |
+| `landing` | Page structure, CTA strategies | hero, hero-centric, testimonial, pricing, social-proof |
+| `chart` | Chart types, library recommendations | trend, comparison, timeline, funnel, pie |
+| `ux` | Best practices, anti-patterns | animation, accessibility, z-index, loading |
+| `react` | React/Next.js performance | waterfall, bundle, suspense, memo, rerender, cache |
+| `web` | Web interface guidelines | aria, focus, keyboard, semantic, virtualize |
+| `prompt` | AI prompts, CSS keywords | (style name) |
+
+### Available Stacks
+
+| Stack | Focus |
+|-------|-------|
+| `html-tailwind` | Tailwind utilities, responsive, a11y (DEFAULT) |
+| `react` | State, hooks, performance, patterns |
+| `nextjs` | SSR, routing, images, API routes |
+| `vue` | Composition API, Pinia, Vue Router |
+| `svelte` | Runes, stores, SvelteKit |
+| `swiftui` | Views, State, Navigation, Animation |
+| `react-native` | Components, Navigation, Lists |
+| `flutter` | Widgets, State, Layout, Theming |
+| `shadcn` | shadcn/ui components, theming, forms, patterns |
+| `jetpack-compose` | Composables, Modifiers, State Hoisting, Recomposition |
+
+---
+
+## Example Workflow
+
+**User request:** "Làm landing page cho dịch vụ chăm sóc da chuyên nghiệp"
+
+### Step 1: Analyze Requirements
+- Product type: Beauty/Spa service
+- Style keywords: elegant, professional, soft
+- Industry: Beauty/Wellness
+- Stack: html-tailwind (default)
+
+### Step 2: Generate Design System (REQUIRED)
+
+```bash
+python3 .agent/.shared/ui-ux-pro-max/scripts/search.py "beauty spa wellness service elegant" --design-system -p "Serenity Spa"
+```
+
+**Output:** Complete design system with pattern, style, colors, typography, effects, and anti-patterns.
+
+### Step 3: Supplement with Detailed Searches (as needed)
+
+```bash
+# Get UX guidelines for animation and accessibility
+python3 .agent/.shared/ui-ux-pro-max/scripts/search.py "animation accessibility" --domain ux
+
+# Get alternative typography options if needed
+python3 .agent/.shared/ui-ux-pro-max/scripts/search.py "elegant luxury serif" --domain typography
+```
+
+### Step 4: Stack Guidelines
+
+```bash
+python3 .agent/.shared/ui-ux-pro-max/scripts/search.py "layout responsive form" --stack html-tailwind
+```
+
+**Then:** Synthesize design system + detailed searches and implement the design.
+
+---
+
+## Output Formats
+
+The `--design-system` flag supports two output formats:
+
+```bash
+# ASCII box (default) - best for terminal display
+python3 .agent/.shared/ui-ux-pro-max/scripts/search.py "fintech crypto" --design-system
+
+# Markdown - best for documentation
+python3 .agent/.shared/ui-ux-pro-max/scripts/search.py "fintech crypto" --design-system -f markdown
+```
+
+---
+
+## Tips for Better Results
+
+1. **Be specific with keywords** - "healthcare SaaS dashboard" > "app"
+2. **Search multiple times** - Different keywords reveal different insights
+3. **Combine domains** - Style + Typography + Color = Complete design system
+4. **Always check UX** - Search "animation", "z-index", "accessibility" for common issues
+5. **Use stack flag** - Get implementation-specific best practices
+6. **Iterate** - If first search doesn't match, try different keywords
+
+---
+
+## Common Rules for Professional UI
+
+These are frequently overlooked issues that make UI look unprofessional:
+
+### Icons & Visual Elements
+
+| Rule | Do | Don't |
+|------|----|----- |
+| **No emoji icons** | Use SVG icons (Heroicons, Lucide, Simple Icons) | Use emojis like 🎨 🚀 ⚙️ as UI icons |
+| **Stable hover states** | Use color/opacity transitions on hover | Use scale transforms that shift layout |
+| **Correct brand logos** | Research official SVG from Simple Icons | Guess or use incorrect logo paths |
+| **Consistent icon sizing** | Use fixed viewBox (24x24) with w-6 h-6 | Mix different icon sizes randomly |
+
+### Interaction & Cursor
+
+| Rule | Do | Don't |
+|------|----|----- |
+| **Cursor pointer** | Add `cursor-pointer` to all clickable/hoverable cards | Leave default cursor on interactive elements |
+| **Hover feedback** | Provide visual feedback (color, shadow, border) | No indication element is interactive |
+| **Smooth transitions** | Use `transition-colors duration-200` | Instant state changes or too slow (>500ms) |
+
+### Light/Dark Mode Contrast
+
+| Rule | Do | Don't |
+|------|----|----- |
+| **Glass card light mode** | Use `bg-white/80` or higher opacity | Use `bg-white/10` (too transparent) |
+| **Text contrast light** | Use `#0F172A` (slate-900) for text | Use `#94A3B8` (slate-400) for body text |
+| **Muted text light** | Use `#475569` (slate-600) minimum | Use gray-400 or lighter |
+| **Border visibility** | Use `border-gray-200` in light mode | Use `border-white/10` (invisible) |
+
+### Layout & Spacing
+
+| Rule | Do | Don't |
+|------|----|----- |
+| **Floating navbar** | Add `top-4 left-4 right-4` spacing | Stick navbar to `top-0 left-0 right-0` |
+| **Content padding** | Account for fixed navbar height | Let content hide behind fixed elements |
+| **Consistent max-width** | Use same `max-w-6xl` or `max-w-7xl` | Mix different container widths |
+
+---
+
+## Pre-Delivery Checklist
+
+Before delivering UI code, verify these items:
+
+### Visual Quality
+- [ ] No emojis used as icons (use SVG instead)
+- [ ] All icons from consistent icon set (Heroicons/Lucide)
+- [ ] Brand logos are correct (verified from Simple Icons)
+- [ ] Hover states don't cause layout shift
+- [ ] Use theme colors directly (bg-primary) not var() wrapper
+
+### Interaction
+- [ ] All clickable elements have `cursor-pointer`
+- [ ] Hover states provide clear visual feedback
+- [ ] Transitions are smooth (150-300ms)
+- [ ] Focus states visible for keyboard navigation
+
+### Light/Dark Mode
+- [ ] Light mode text has sufficient contrast (4.5:1 minimum)
+- [ ] Glass/transparent elements visible in light mode
+- [ ] Borders visible in both modes
+- [ ] Test both modes before delivery
+
+### Layout
+- [ ] Floating elements have proper spacing from edges
+- [ ] No content hidden behind fixed navbars
+- [ ] Responsive at 375px, 768px, 1024px, 1440px
+- [ ] No horizontal scroll on mobile
+
+### Accessibility
+- [ ] All images have alt text
+- [ ] Form inputs have labels
+- [ ] Color is not the only indicator
+- [ ] `prefers-reduced-motion` respected

package/templates/.agent/workflows/vibe-plan.md

@@ -0,0 +1,133 @@
+---
+description: |
+  Orchestrator workflow untuk planning phase lengkap — dari ide ke siap coding.
+  Jalankan di awal project baru sebelum coding apapun.
+  Memandu: Research → PRD → Tech Design → Build Plan (4 langkah, ~1-2 jam total).
+---
+
+# /vibe-plan — Planning Phase Orchestrator
+
+Workflow ini memandu kamu dari ide mentah ke dokumen planning lengkap
+yang siap dipakai agent untuk coding.
+
+**Total waktu estimasi:** 60–90 menit
+**Output:** 4 dokumen siap pakai + backlog terisi
+
+---
+
+## Langkah 1 — Cek Status Project
+
+Pertama, cek dokumen apa yang sudah ada:
+
+```
+Cek keberadaan file berikut:
+- docs/research-*.md     → jika ada, research sudah selesai
+- docs/01-PRD.md         → jika terisi (bukan template), PRD sudah selesai
+- docs/02-TECH-DESIGN.md → jika terisi, tech design sudah selesai
+- BUILD_PLAN.md          → jika ada, build plan sudah selesai
+```
+
+Berdasarkan apa yang ditemukan, langsung lompat ke step yang belum selesai.
+Tampilkan status ke user:
+
+```
+📊 Status Planning [Nama Aplikasi]:
+
+Step 1 — Research:      [✅ Selesai / ⏳ Belum]
+Step 2 — PRD:           [✅ Selesai / ⏳ Belum]
+Step 3 — Tech Design:   [✅ Selesai / ⏳ Belum]
+Step 4 — Build Plan:    [✅ Selesai / ⏳ Belum]
+
+Mulai dari Step [N]? (yes/no)
+```
+
+---
+
+## Langkah 2 — Jalankan Planning Secara Berurutan
+
+### Step 1: Research (~20 menit)
+```
+Tujuan: Validasi ide, analisa pasar, identifikasi risiko
+Skill: vibe-research
+Output: docs/research-[AppName].md
+
+Jalankan skill vibe-research sekarang.
+Setelah selesai dan user approve → lanjut ke Step 2.
+```
+
+### Step 2: PRD (~20 menit)
+```
+Tujuan: Definisikan fitur, user stories, scope MVP
+Skill: vibe-prd
+Input: docs/research-[AppName].md (baca dulu)
+Output: docs/01-PRD.md (terisi penuh)
+
+Jalankan skill vibe-prd sekarang.
+Setelah selesai dan user approve → lanjut ke Step 3.
+```
+
+### Step 3: Tech Design (~20 menit)
+```
+Tujuan: Pilih stack, desain arsitektur, buat ERD awal
+Skill: vibe-techdesign
+Input: docs/01-PRD.md + docs/research-*.md
+Output: docs/02-TECH-DESIGN.md (terisi + ERD + API contracts)
+
+Jalankan skill vibe-techdesign sekarang.
+Setelah selesai dan user approve → lanjut ke Step 4.
+```
+
+### Step 4: Build Plan (~15 menit)
+```
+Tujuan: Breakdown task per sprint, siapkan backlog
+Skill: vibe-buildplan
+Input: docs/01-PRD.md + docs/02-TECH-DESIGN.md
+Output: docs/04-BACKLOG.md (terisi) + BUILD_PLAN.md
+
+Jalankan skill vibe-buildplan sekarang.
+Setelah selesai → tampilkan summary.
+```
+
+---
+
+## Langkah 3 — Summary Akhir
+
+Setelah semua step selesai, tampilkan:
+
+```
+🎉 Planning Phase Selesai!
+
+Dokumen yang sudah dibuat:
+✅ docs/research-[AppName].md    — Validasi ide & analisa pasar
+✅ docs/01-PRD.md                — Product Requirements (N user stories)
+✅ docs/02-TECH-DESIGN.md        — Stack: [ringkasan stack] + ERD
+✅ docs/04-BACKLOG.md            — [N] sprint, [M] total task
+✅ BUILD_PLAN.md                 — Panduan build phase
+
+Stack yang dipilih:
+- [ringkasan 1-liner stack]
+
+Sprint 1 Goal: [goal sprint 1]
+Task pertama: T001 — [nama task pertama]
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+Siap coding! Mulai dengan:
+  /new-feature  → untuk fitur size M/L
+  /dev-reset    → jika butuh setup environment dari awal
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+Sebelum coding, pastikan:
+□ AGENTS.md sudah ada di root project
+□ .env.local sudah diisi credentials
+□ Docker Compose sudah jalan (docker compose up -d)
+```
+
+---
+
+## Aturan Penting
+
+- Jangan skip ke coding sebelum minimal Step 2 (PRD) selesai
+- Setiap step harus dapat **approval eksplisit** dari user sebelum lanjut
+- Jika user ingin ubah sesuatu di step sebelumnya, kembali ke step itu dulu
+- Workflow ini bisa di-resume kapanpun — cukup jalankan `/vibe-plan` lagi dan ia akan cek progress
+- Dokumen yang dihasilkan adalah **living documents** — update setiap sprint jika ada perubahan scope

package/templates/.agent/workflows/vibe-recap.md

@@ -0,0 +1,17 @@
+---
+description: Rangkum percakapan saat ini agar bisa pindah ke chat baru tanpa hilang konteks
+---
+
+# Vibe Recap — Context Compaction
+
+Gunakan workflow `/vibe-recap` atau `/recap` saat percakapan AI (context window) sudah terlalu panjang atau AI mulai kehilangan fokus.
+
+Sebagai AI, tugasmu:
+1. Buat atau perbarui file `docs/recap.md`.
+2. Tulis rangkuman komprehensif dari semua hal yang kita diskusikan di sesi kerja ini.
+3. Struktur wajib di dalam `recap.md`:
+   - Fitur / Bug apa yang sedang dikerjakan tadi.
+   - Keputusan arsitektur terakhir yang disepakati.
+   - Daftar file apa saja yang sudah diubah di sesi ini.
+   - Langkah selanjutnya yang tertunda (*Next Steps*).
+4. Beritahu user: "Recap berhasil dibuat di `docs/recap.md`. Silakan buka obrolan baru (*New Chat*) dan perintahkan saya untuk membaca file tersebut agar kita bisa melanjutkan dengan memori yang lebih segar!"

package/templates/.antigravity/rules.md

@@ -0,0 +1,64 @@
+# Rules — Project [Nama Proyek]
+# File ini selalu dimuat Antigravity setiap sesi.
+# Letakkan di: .antigravity/rules.md (root project)
+
+## Stack & import paths
+
+- Runtime: Node.js 22 LTS, TypeScript strict mode — no `any`
+- Prisma 7: import dari `@/generated/prisma`, BUKAN dari `@prisma/client`
+- Next.js 16: `params`, `searchParams`, dan `headers()` selalu di-`await`
+- BullMQ: gunakan konstanta dari `QUEUES` object, jangan string literal
+
+## Next.js 16 — patterns wajib
+
+```typescript
+// params — async
+export default async function Page({ params }: { params: Promise<{ id: string }> }) {
+  const { id } = await params
+}
+// headers() — async
+const session = await auth.api.getSession({ headers: await headers() })
+// webhook
+const token = (await headers()).get('x-callback-token')
+```
+
+## Coding standards
+
+- Setiap async function wajib try/catch dengan log `[module:method]` di catch
+- Setiap komponen yang fetch data wajib punya loading, empty, dan error state
+- Semua input user wajib divalidasi dengan Zod sebelum masuk ke database
+- File upload: hanya jpg/png/webp, maksimal 5MB
+- `findMany` wajib ada `take` + `skip` — jangan query tanpa limit
+- Soft delete: gunakan `deletedAt DateTime?` — jangan hard delete data penting
+
+## Keamanan & privasi (UU PDP)
+
+- Secrets dan API keys hanya di env vars — TIDAK PERNAH di kode
+- Log tidak boleh print password, token, NIK, nomor rekening
+- Data sensitif (NIK, rekening) disimpan terenkripsi dengan pgcrypto
+- Firebase: hanya gunakan `firebase_messaging` — JANGAN aktifkan Analytics/Crashlytics
+
+## Sebelum coding
+
+- Cek komponen yang ada di `/components/ui/` sebelum buat baru
+- Untuk fitur size M atau L: cek apakah ada spec di `specs/` dulu
+- Satu fokus per sesi — jangan ubah hal di luar scope yang diminta
+- Konfirmasi sebelum hapus atau refactor kode yang sudah ada
+
+## Git & commit
+
+- Format: `type(scope): deskripsi` — contoh: `feat(auth): tambah Google OAuth`
+- Types: feat, fix, chore, docs, refactor, test
+- Jangan push langsung ke `main` — selalu via Pull Request
+
+## Adaptive Memory & Checkbox Task Tracking (Senjata Utama AI)
+
+- **Checkbox Workflow**: Setiap kali user memberikan perintah untuk membuat atau memperbaiki fitur, kamu WAJIB memecahkannya menjadi langkah-langkah detail di `docs/task_on_hand.md` dengan format Checkbox (`[ ] Step 1`, `[ ] Step 2`). Kamu harus mengeksekusi instruksi tersebut SATU PER SATU secara berurutan dan mengubah statusnya menjadi `[x]` setiap kodenya selesai! Jangan pernah melompat langkah!
+- **Troubleshooting Log**: Setiap menemukan error dan berhasil memperbaikinya, kamu WAJIB mencatatnya di `docs/troubleshooting.md` (Pesan Error, Penyebab, Solusi). Ini mencegah pengulangan kesalahan yang sama di sesi berikutnya.
+- **Template Code**: Saat disuruh membuat komponen/file baru, SELALU periksa apakah ada referensi *snippet* di `templates/.agent/snippets/` dan teladani struktur kodenya 100%.
+- Di setiap awal sesi, kamu WAJIB membaca `docs/task_on_hand.md` dan `docs/recap.md` (jika ada) untuk *loading context*.
+
+## Context7
+
+- Saat coding Prisma 7, Next.js 16, Better Auth, BullMQ, Socket.io:
+  tambahkan `use context7` di prompt untuk mendapat docs terbaru