vibes-plug 1.0.0 → 2.11.0

package/skills/zero-trust-secret-vault/SKILL.md

@@ -0,0 +1,88 @@
+---
+name: zero-trust-secret-vault
+description: "Expert guide for Zero-Trust Secret Management (Infisical, HashiCorp Vault, Doppler), automated API key rotation, and environment security / Panduan ahli manajemen rahasia Zero-Trust, rotasi kunci API, dan keamanan variabel lingkungan."
+author: "Roedy Rustam"
+---
+
+# Zero-Trust Secret Vault & Credential Security Expert
+
+[English](#english) | [Bahasa Indonesia](#bahasa-indonesia)
+
+---
+
+<a name="english"></a>
+## English
+
+### Purpose & Overview
+Production-grade security standards for managing application secrets, environment variables, API keys, database credentials, and TLS certificates using Zero-Trust Secret Managers — Infisical, HashiCorp Vault, and Doppler — featuring automated secret rotation, dynamic credentials, and zero plain-text leaks in repositories or CI/CD pipelines.
+
+### Key Capabilities
+- **Zero Plain-Text Secrets**: Injecting encrypted secrets at runtime without storing `.env` files in production artifacts.
+- **Automated Rotation**: Programmatic rotation of API keys, JWT secrets, and database passwords.
+- **Audit Logging**: Tracking secret access, version history, and permission policies across development teams.
+
+```bash
+# Infisical CLI Runtime Secret Injection
+infisical run -- env | grep DATABASE_URL
+```
+
+### Implementation Checklist
+- [ ] Install Infisical CLI or Vault agent in the deployment environment.
+- [ ] Map environment variables (Development, Staging, Production) in the Secret Manager.
+- [ ] Configure CI/CD pipeline to inject secrets dynamically rather than using `.env` files.
+- [ ] Set up auto-rotation for database credentials and high-privilege API keys (e.g., every 30 days).
+
+### Example: Node.js Infisical SDK
+```javascript
+import { InfisicalClient } from "@infisical/sdk";
+
+const client = new InfisicalClient({
+  clientId: process.env.INFISICAL_CLIENT_ID,
+  clientSecret: process.env.INFISICAL_CLIENT_SECRET
+});
+
+const dbPassword = await client.getSecret("DATABASE_PASSWORD", {
+  environment: "prod",
+  path: "/database"
+});
+```
+
+## Orchestration & Integration
+- Integrates with: `ci-cd-devops-architect`, `authentication-identity-expert`, `mcp-server-architect`.
+
+---
+
+<a name="bahasa-indonesia"></a>
+## Bahasa Indonesia
+
+### Deskripsi
+Standar keamanan tingkat produksi untuk pengelolaan rahasia aplikasi, variabel lingkungan, kunci API, kredensial database, dan sertifikat TLS menggunakan Secret Manager Zero-Trust — Infisical, HashiCorp Vault, dan Doppler — dengan rotasi rahasia otomatis dan jaminan tanpa kebocoran teks polos di repositori atau pipeline CI/CD.
+
+### Fitur Utama
+- **Zero Plain-Text Secrets**: Injeksi rahasia terenkripsi saat runtime tanpa menyimpan file `.env` di artefak produksi.
+- **Rotasi Otomatis**: Rotasi terprogram untuk kunci API, rahasia JWT, dan kata sandi database.
+- **Audit Logging**: Pelacakan akses rahasia, riwayat versi, dan kebijakan izin di seluruh tim pengembangan.
+
+### Checklist Implementasi
+- [ ] Instal Infisical CLI atau agen Vault di lingkungan deployment.
+- [ ] Petakan variabel lingkungan (Development, Staging, Production) di Secret Manager.
+- [ ] Konfigurasi pipeline CI/CD untuk menyuntikkan rahasia secara dinamis (jangan gunakan file `.env`).
+- [ ] Atur rotasi otomatis untuk kredensial database dan kunci API berhak istimewa (misal: setiap 30 hari).
+
+### Contoh: Node.js Infisical SDK
+```javascript
+import { InfisicalClient } from "@infisical/sdk";
+
+const client = new InfisicalClient({
+  clientId: process.env.INFISICAL_CLIENT_ID,
+  clientSecret: process.env.INFISICAL_CLIENT_SECRET
+});
+
+const dbPassword = await client.getSecret("DATABASE_PASSWORD", {
+  environment: "prod",
+  path: "/database"
+});
+```
+
+## Integrasi Orkestrasi
+- Terintegrasi dengan: `ci-cd-devops-architect`, `authentication-identity-expert`, `mcp-server-architect`.

package/.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,20 +0,0 @@
----
-name: Feature request
-about: Suggest an idea for this project
-title: ''
-labels: ''
-assignees: ''
-
----
-
-**Is your feature request related to a problem? Please describe.**
-A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
-
-**Describe the solution you'd like**
-A clear and concise description of what you want to happen.
-
-**Describe alternatives you've considered**
-A clear and concise description of any alternative solutions or features you've considered.
-
-**Additional context**
-Add any other context or screenshots about the feature request here.

package/CONTRIBUTING.md

@@ -1,199 +0,0 @@
-# Contribution Guide / Panduan Kontribusi
-
-[English](#english) | [Bahasa Indonesia](#bahasa-indonesia)
-
----
-
-<a name="english"></a>
-## English
-
-Thank you for contributing to **Vibes Plug**! This guide is designed to make it easy for you if you have *forked* this repository on GitHub to add or update *skills* according to proper standards.
-
-### Contribution Flow (Step-by-Step)
-
-#### 1. Sync Your Local Repository
-Ensure your local repository is connected to the main repository (*upstream*) to get the latest updates.
-
-If you haven't added the main repository as an *upstream* remote, run the following command in your terminal/PowerShell inside the `vibes-plug` directory:
-
-```bash
-# Add upstream remote
-git remote add upstream https://github.com/roedyrustam/vibes-plug.git
-```
-
-Before you start creating a new skill, sync your local `main` branch with upstream:
-
-```bash
-# Switch to main branch
-git checkout main
-
-# Pull the latest updates from upstream
-git pull upstream main
-
-# Sync it to your GitHub fork (origin)
-git push origin main
-```
-
-#### 2. Create a New Branch
-Always create a new, descriptive branch for the changes you want to make:
-
-```bash
-git checkout -b feat/add-skill-<skill-name>
-# Example: git checkout -b feat/add-skill-fast-api
-```
-
-#### 3. Create a New Skill Module
-1. Navigate to the `skills/` directory.
-2. Create a new folder with your skill name using **kebab-case** (e.g., `skills/fast-api`).
-3. Create a `SKILL.md` file inside that folder. You can copy the template from [SKILL.md](file:///c:/Users/roedy/.gemini/config/plugins/vibes-plug/skills/skill_baru/SKILL.md).
-
-Set up the metadata (frontmatter) at the very top of the `SKILL.md` file:
-
-```yaml
----
-name: kebab-case-skill-name
-description: "Short English description / Deskripsi singkat"
-author: "Your Name or GitHub Username"
----
-```
-
-The document body must have the following sections:
-- `# Skill Name`
-- `## Description`
-- `## Instructions` (Contains detailed guidelines, code styling rules, etc.)
-- `## Trigger Conditions` (Conditions/context under which this skill should be activated by the agent)
-
-#### 4. Register the Skill in README.md and BLUEPRINT.md
-To make your new skill recognized and easily discoverable:
-1. **`README.md`**: Register your skill in the **Features and Available Skills** section under the relevant category.
-2. **`BLUEPRINT.md`**: Register your skill module in the **Skill Modules** section.
-
-#### 5. Run the Standardization Script
-We provide an automated script to format markdown, align technology stack versions (e.g., React 19, Next.js 15), and fix emoji encoding issues.
-
-Run the following command before committing:
-
-```bash
-node scripts/update_skills.js
-```
-
-Ensure the script runs successfully and check if any of your new skill files were updated.
-
-#### 6. Commit and Push Changes
-Once everything is neat and validated, commit your changes:
-
-```bash
-git add .
-git commit -m "feat: add skill <skill-name>"
-git push origin feat/add-skill-<skill-name>
-```
-
-#### 7. Create a Pull Request (PR)
-1. Open your forked repository page on GitHub (e.g., `https://github.com/username/vibes-plug`).
-2. You will see a yellow button saying **"Compare & pull request"**. Click that button.
-3. Provide a clear description of the purpose and utility of the skill you added.
-4. Submit your Pull Request (PR) to the `main` branch of the original repository (`roedyrustam/vibes-plug`).
-
-### Additional Rules & Tips
-> [!NOTE]
-> - Ensure instructions are written in a clear and instructive language.
-> - Avoid duplicate instructions with existing skills. If your skill is similar, consider updating an existing skill instead.
-> - Do not include extra frontmatter fields other than `name`, `description`, and `author`, as they will be cleaned automatically by the `update_skills.js` script.
-
----
-
-<a name="bahasa-indonesia"></a>
-## Bahasa Indonesia
-
-Terima kasih telah berkontribusi ke **Vibes Plug**! Panduan ini dirancang khusus untuk mempermudah Anda yang telah melakukan *fork* repositori ini di GitHub agar dapat menambahkan atau memperbarui *skills* dengan standar yang sesuai.
-
-### Alur Kontribusi (Step-by-Step)
-
-#### 1. Sinkronisasi Repositori Lokal Anda
-Pastikan repositori lokal Anda terhubung dengan repositori utama (*upstream*) agar selalu mendapatkan pembaruan terbaru.
-
-Jika Anda belum menambahkan repositori utama sebagai *upstream*, jalankan perintah berikut di terminal/PowerShell di dalam direktori `vibes-plug`:
-
-```bash
-# Tambahkan remote upstream
-git remote add upstream https://github.com/roedyrustam/vibes-plug.git
-```
-
-Sebelum mulai membuat skill baru, lakukan sinkronisasi branch `main` lokal Anda dengan upstream:
-
-```bash
-# Pindah ke branch main
-git checkout main
-
-# Tarik pembaruan terbaru dari upstream
-git pull upstream main
-
-# Sinkronisasikan ke fork GitHub Anda (origin)
-git push origin main
-```
-
-#### 2. Buat Branch Baru
-Selalu buat branch baru yang deskriptif untuk perubahan yang ingin Anda lakukan:
-
-```bash
-git checkout -b feat/add-skill-<nama-skill>
-# Contoh: git checkout -b feat/add-skill-fast-api
-```
-
-#### 3. Buat Modul Skill Baru
-1. Masuk ke direktori `skills/`.
-2. Buat folder baru dengan nama skill Anda menggunakan format **kebab-case** (misalnya `skills/fast-api`).
-3. Buat file `SKILL.md` di dalam folder tersebut. Anda bisa menyalin template dari [SKILL.md](file:///c:/Users/roedy/.gemini/config/plugins/vibes-plug/skills/skill_baru/SKILL.md).
-
-Atur format metadata (frontmatter) di bagian paling atas file `SKILL.md`:
-
-```yaml
----
-name: nama-skill-kebab-case
-description: "Deskripsi singkat / Short description"
-author: "Nama Anda atau Username GitHub"
----
-```
-
-Struktur isi dokumen harus memiliki bagian berikut:
-- `# Nama Skill`
-- `## Deskripsi`
-- `## Instruksi` (Berisi panduan detail, aturan penulisan kode, dll.)
-- `## Kondisi Pemicu` (Kondisi/konteks kapan skill ini harus diaktifkan oleh agen)
-
-#### 4. Daftarkan Skill di README.md dan BLUEPRINT.md
-Agar skill baru Anda dikenali dan mudah ditemukan:
-1. **`README.md`**: Daftarkan skill Anda di bagian **Fitur dan Skills yang Tersedia** di bawah kategori yang relevan.
-2. **`BLUEPRINT.md`**: Daftarkan modul skill Anda di bagian **Skill Modules**.
-
-#### 5. Jalankan Script Standardisasi
-Kami menyediakan script otomatis untuk merapikan markdown, menyelaraskan versi stack teknologi (misal React 19, Next.js 15), serta memperbaiki isu encoding emoji.
-
-Jalankan perintah berikut sebelum melakukan commit:
-
-```bash
-node scripts/update_skills.js
-```
-
-Pastikan script berjalan dengan sukses dan laporkan jika ada file skill baru Anda yang diperbarui.
-
-#### 6. Commit dan Push Perubahan
-Setelah semuanya rapi dan tervalidasi, commit perubahan Anda:
-
-```bash
-git add .
-git commit -m "feat: add skill <nama-skill>"
-git push origin feat/add-skill-<nama-skill>
-```
-
-#### 7. Buat Pull Request (PR)
-1. Buka halaman repositori hasil fork Anda di GitHub (misal: `https://github.com/username/vibes-plug`).
-2. Anda akan melihat tombol kuning bertuliskan **"Compare & pull request"**. Klik tombol tersebut.
-3. Berikan deskripsi yang jelas mengenai tujuan dan kegunaan dari skill yang Anda tambahkan.
-4. Kirim Pull Request (PR) Anda ke branch `main` repositori asal (`roedyrustam/vibes-plug`).
-
-### Aturan Tambahan & Tips
-> [!NOTE]
-> - Pastikan instruksi ditulis dengan bahasa yang jelas dan instruktif.
-> - Hindari duplikasi instruksi dengan skill yang sudah ada. Jika skill Anda mirip, pertimbangkan untuk memperbarui skill yang telah ada.
-> - Jangan menyertakan frontmatter tambahan di luar `name`, `description`, dan `author`, karena akan dibersihkan secara otomatis oleh script `update_skills.js`.

package/SECURITY.md

@@ -1,21 +0,0 @@
-# Security Policy
-
-## Supported Versions
-
-Use this section to tell people about which versions of your project are
-currently being supported with security updates.
-
-| Version | Supported          |
-| ------- | ------------------ |
-| 5.1.x   | :white_check_mark: |
-| 5.0.x   | :x:                |
-| 4.0.x   | :white_check_mark: |
-| < 4.0   | :x:                |
-
-## Reporting a Vulnerability
-
-Use this section to tell people how to report a vulnerability.
-
-Tell them where to go, how often they can expect to get an update on a
-reported vulnerability, what to expect if the vulnerability is accepted or
-declined, etc.

package/skills/senior-fullstack/SKILL.md

@@ -1,167 +0,0 @@
----
-name: senior-fullstack
-description: "Complete toolkit for senior fullstack with modern tools and best practices / Perangkat instruksi lengkap untuk pengembang fullstack tingkat senior dengan alat-alat dan best practices termutakhir."
-author: "Roedy Rustam"
----
-
-# Senior Fullstack Developer (2026 Edition)
-
-[English](#english) | [Bahasa Indonesia](#bahasa-indonesia)
-
----
-
-<a name="english"></a>
-## English
-
-### Description
-Complete guidelines for senior fullstack developers building production-grade applications in 2026. Covers the modern AI-native stack, architecture decision-making, API design, frontend/backend integration, and team-level best practices.
-
-### Trigger Conditions
-- Making fullstack architecture decisions across frontend and backend.
-- Designing API contracts between React 19/Next.js 15 frontend and Node.js/Go/Python backend.
-- Integrating AI features (LLM, agents, RAG) into a fullstack application.
-- Setting up a monorepo with shared types between frontend and backend.
-- Reviewing and improving overall application architecture and code quality.
-
-### Modern 2026 Fullstack Stack
-
-#### Recommended Stacks by Use Case
-
-| Use Case | Frontend | Backend | Database | AI Layer |
-|---|---|---|---|---|
-| **SaaS App (default)** | Next.js 15 (App Router) | Hono / Fastify 5 | Postgres + Drizzle | Vercel AI SDK 5.x |
-| **AI-First App** | Next.js 15 + RSC streaming | Mastra.ai / LangGraph | pgvector + Supabase | Anthropic / OpenAI |
-| **Decoupled SPA** | TanStack Start + React 19 | Hono RPC | Postgres + Drizzle | Vercel AI SDK |
-| **Content Site** | Astro 5 + MDX | N/A (static) | Sanity / Contentful | — |
-| **Mobile** | Expo SDK 53 + React Native 0.79 | Hono / Fastify | SQLite (Expo) + Postgres | Vercel AI SDK |
-
-#### AI-Native Fullstack Patterns
-In 2026, AI is a first-class citizen in fullstack applications:
-- **Streaming AI Responses**: Use Next.js RSC + Vercel AI SDK `streamUI` to stream LLM responses as React components from the server.
-- **Server Actions as AI Triggers**: Use React 19 `useActionState` with Server Actions to invoke LLM calls without an API layer.
-- **Background AI Jobs**: Offload long LLM tasks to BullMQ + Redis workers; stream results via WebSockets or SSE.
-- **Structured AI Output**: Always use `zodResponseFormat` or Pydantic schemas for LLM responses — never parse free-form JSON.
-
-### API Design Principles (2026)
-
-#### Type-Safe Communication
-Choose one approach and be consistent:
-- **Hono RPC**: If backend is Hono — zero codegen, end-to-end types.
-- **tRPC**: If using React Query with Next.js — excellent DX with RSC support.
-- **OpenAPI + codegen**: If you have multiple consumers (mobile, third parties).
-
-#### API Versioning
-- Use URL versioning: `/api/v1/users`.
-- Pin major version in URL, minor versions are backward-compatible.
-- Deprecate with `Deprecation` and `Sunset` headers.
-
-#### Error Response Standard (RFC 9457 Problem Details)
-```typescript
-// Consistent error format across all endpoints
-interface ProblemDetail {
-  type: string;       // URI identifying the error type
-  title: string;      // Human-readable summary
-  status: number;     // HTTP status code
-  detail: string;     // Specific explanation
-  instance?: string;  // URI of the specific occurrence
-}
-```
-
-### SPA vs SSR vs Static — Decision Guide
-```
-SEO-critical + mostly read? → Next.js SSR / Astro 5 (static)
-Highly interactive dashboard? → SPA (TanStack Start / Vite + TanStack Router)
-   → see spa-orchestrator skill for architecture details
-Mixed (marketing + app)?    → Next.js 15 with hybrid routing
-Real-time data?             → SSR + WebSocket or SSE streaming
-```
-
-### Monorepo with Shared Types
-```typescript
-// packages/types/src/index.ts — single source of truth
-export interface User {
-  id: string;
-  email: string;
-  name: string;
-  plan: 'free' | 'pro' | 'enterprise';
-  isSuperAdmin: boolean;
-}
-
-export interface ApiResponse<T> {
-  data: T;
-  meta?: { page: number; total: number };
-}
-
-// apps/api — uses the type
-// apps/web — uses the same type
-// apps/admin — uses the same type
-import type { User } from '@myapp/types';
-```
-
-### Security Checklist (Fullstack)
-- [ ] All user inputs validated with Zod on the server (never trust the client).
-- [ ] JWT secrets rotated every 90 days; use short expiry + refresh tokens.
-- [ ] CSP headers configured (no `unsafe-inline` in production).
-- [ ] All DB queries use parameterized queries — no string concatenation.
-- [ ] File uploads validated for MIME type and scanned before storage.
-- [ ] Rate limiting on all public API endpoints.
-- [ ] Super Admin routes restricted to `admin.domain.com` with `isSuperAdmin` check.
-
-### Code Review Standards
-- Functions < 30 lines; files < 300 lines.
-- No business logic in UI components.
-- Every PR includes relevant tests (unit or E2E).
-- No `any` types in TypeScript production code.
-- Dependencies audited with `pnpm audit` on every PR.
-
----
-
-<a name="bahasa-indonesia"></a>
-## Bahasa Indonesia
-
-### Deskripsi
-Panduan lengkap untuk pengembang fullstack senior yang membangun aplikasi tingkat produksi di 2026. Mencakup stack AI-native modern, pengambilan keputusan arsitektur, desain API, integrasi frontend/backend, dan best practices tingkat tim.
-
-### Kondisi Pemicu
-- Membuat keputusan arsitektur fullstack di frontend dan backend.
-- Merancang kontrak API antara frontend React 19/Next.js 15 dan backend Node.js/Go/Python.
-- Mengintegrasikan fitur AI (LLM, agen, RAG) ke dalam aplikasi fullstack.
-- Menyiapkan monorepo dengan shared types antara frontend dan backend.
-- Meninjau dan meningkatkan arsitektur dan kualitas kode aplikasi secara keseluruhan.
-
-### Stack Fullstack Modern 2026
-
-Rekomendasi stack berdasarkan use case:
-- **SaaS App**: Next.js 15 + Hono/Fastify + Postgres + Drizzle + Vercel AI SDK.
-- **AI-First App**: Next.js 15 RSC streaming + Mastra.ai/LangGraph + pgvector.
-- **SPA Terpisah**: TanStack Start + Hono RPC + Postgres — lihat `spa-orchestrator`.
-- **Situs Konten**: Astro 5 + MDX.
-- **Mobile**: Expo SDK 53 + Hono + SQLite.
-
-### Pola Fullstack AI-Native (2026)
-AI adalah warga kelas satu di aplikasi fullstack 2026:
-- **Streaming RSC**: Alirkan respons LLM sebagai komponen React dari server menggunakan `streamUI` Vercel AI SDK 5.x.
-- **Server Actions sebagai Pemicu AI**: Panggil LLM dari Server Actions React 19 tanpa lapisan API terpisah.
-- **Background AI Jobs**: Offload tugas LLM panjang ke BullMQ + Redis; stream hasil via WebSocket atau SSE.
-- **Output AI Terstruktur**: Selalu gunakan `zodResponseFormat` atau skema Pydantic — jangan pernah parse JSON bebas dari LLM.
-
-### Prinsip Desain API (2026)
-- **Hono RPC**: Zero codegen, end-to-end type-safe jika backend adalah Hono.
-- **tRPC**: Untuk React Query + Next.js dengan dukungan RSC.
-- **OpenAPI + codegen**: Jika memiliki banyak konsumen (mobile, pihak ketiga).
-- **Format Error RFC 9457**: Respons error yang konsisten dengan `type`, `title`, `status`, `detail`.
-
-### SPA vs SSR vs Static
-Gunakan SSR/Astro untuk situs kritis SEO dan banyak baca. Gunakan SPA (TanStack Start) untuk dashboard yang sangat interaktif. Gunakan Next.js 15 dengan routing hybrid untuk aplikasi campuran (marketing + app).
-
-### Monorepo dengan Shared Types
-Definisikan interface dan tipe bersama di `packages/types` — digunakan oleh semua app (web, admin, api, mobile) sebagai single source of truth.
-
-### Checklist Keamanan
-- Input pengguna divalidasi Zod di server.
-- JWT rotasi 90 hari; expiry pendek + refresh token.
-- Header CSP dikonfigurasi.
-- Semua query DB menggunakan parameterized query.
-- Upload file divalidasi MIME type.
-- Rate limiting di semua endpoint publik.
-- Rute Super Admin dibatasi di `admin.domain.com` dengan cek `isSuperAdmin`.

package/skills/senior-fullstack/references/architecture_patterns.md

@@ -1,160 +0,0 @@
-# Architecture Patterns
-
-## Overview
-This reference guide details high-performance architecture patterns for senior fullstack systems. It covers multi-tier caching (Redis), relational database partitioning, and resilient event-driven background queues.
-
----
-
-## Production Architecture Designs
-
-### 1. Multi-Tier Caching Layer (Redis + Memory)
-
-For write-heavy/read-intensive endpoints (e.g., public API stats or product catalogs), hitting the relational database directly is a major bottleneck. Implement a Cache-Aside pattern using memory-first or Redis structures.
-
-#### Pattern: Type-Safe Cache-Aside Implementation (`lib/cache/redis.ts`)
-
-```typescript
-import { Redis } from '@upstash/redis'; // or ioredis
-
-export const redis = new Redis({
-  url: process.env.UPSTASH_REDIS_REST_URL!,
-  token: process.env.UPSTASH_REDIS_REST_TOKEN!,
-});
-
-interface CacheOptions {
-  ttlSeconds?: number;
-}
-
-export async function getOrSetCache<T>(
-  key: string,
-  fetchFn: () => Promise<T>,
-  options: CacheOptions = {}
-): Promise<T> {
-  const ttl = options.ttlSeconds ?? 3600; // Default: 1 hour
-
-  try {
-    // Attempt cache read
-    const cachedData = await redis.get<string>(key);
-    if (cachedData) {
-      return typeof cachedData === 'string' ? JSON.parse(cachedData) : cachedData;
-    }
-  } catch (err) {
-    console.error(`⚠️ Redis read failed for key ${key}:`, err);
-  }
-
-  // Cache miss - execute database hit
-  const freshData = await fetchFn();
-
-  try {
-    // Populate cache asynchronously
-    await redis.set(key, JSON.stringify(freshData), { ex: ttl });
-  } catch (err) {
-    console.error(`⚠️ Redis write failed for key ${key}:`, err);
-  }
-
-  return freshData;
-}
-```
-
----
-
-### 2. High-Performance Indexing and Query Tuning
-
-Poor database performance is almost always caused by missing indexes on fields targeted by `WHERE` and `JOIN` clauses. Use standard PostgreSQL compound indexes and profile execution paths.
-
-#### Pattern: Compound & Partial Indexing (`prisma/schema.prisma` or pure SQL)
-
-```prisma
-// Example Prisma compound index optimized for scoped tenant querying
-model Invoice {
-  id          String   @id @default(cuid())
-  tenantId    String
-  status      String   // PAID, UNPAID, OVERDUE
-  amount      Float
-  createdAt   DateTime @default(now())
-
-  // Optimize compound filters: WHERE tenantId = X AND status = Y ORDER BY createdAt DESC
-  @@index([tenantId, status, createdAt(sort: Desc)])
-}
-```
-
-#### Profiling Queries with PostgreSQL `EXPLAIN ANALYZE`
-
-Run the following SQL diagnostic query inside your migration console to detect costly Sequential Scans (Seq Scan):
-
-```sql
-EXPLAIN ANALYZE 
-SELECT * FROM "Invoice" 
-WHERE "tenantId" = 'tenant_123' 
-  AND "status" = 'PAID' 
-ORDER BY "createdAt" DESC;
-```
-
-*Look for:* `Index Scan using Invoice_tenantId_status_createdAt_idx` indicating the optimizer is executing query lookup paths with O(log N) complexity instead of O(N).
-
----
-
-### 3. Resilient Webhooks & Resilient Background Workers
-
-Handling computationally heavy tasks (e.g., PDF generation, batch emails, image processing) in the standard request/response HTTP loop leads to poor UI performance and timeout failures. Decouple execution paths with background job queues (e.g., BullMQ, Inngest, or Celery).
-
-#### Pattern: Event-Driven Queue Producer (`lib/queue/jobs.ts`)
-
-```typescript
-import { Queue } from 'bullmq';
-import IORedis from 'ioredis';
-
-const connection = new IORedis(process.env.REDIS_URL!);
-
-// 1. Establish the queue
-export const emailQueue = new Queue('EmailQueue', { connection });
-
-export async function queueWelcomeEmail(userId: string, email: string) {
-  await emailQueue.add(
-    'send_welcome',
-    { userId, email },
-    {
-      attempts: 5, // High retry resilience
-      backoff: {
-        type: 'exponential',
-        delay: 5000, // Exponential backoff starting at 5s
-      },
-    }
-  );
-}
-```
-
-#### Pattern: Decoupled Queue Worker (`workers/email.ts`)
-
-```typescript
-import { Worker, Job } from 'bullmq';
-import IORedis from 'ioredis';
-import { sendWelcomeEmail } from '@/lib/email';
-
-const connection = new IORedis(process.env.REDIS_URL!);
-
-// Decoupled consumer execution running in a separate thread/container
-const emailWorker = new Worker(
-  'EmailQueue',
-  async (job: Job) => {
-    if (job.name === 'send_welcome') {
-      const { email, userId } = job.data;
-      await sendWelcomeEmail(email, userId);
-    }
-  },
-  { connection, concurrency: 10 }
-);
-
-emailWorker.on('completed', (job) => {
-  console.log(`✅ Job ${job.id} completed successfully`);
-});
-
-emailWorker.on('failed', (job, err) => {
-  console.error(`❌ Job ${job?.id} failed:`, err);
-});
-```
-
----
-
-## Technical Summary
-Decoupling application layers using structured micro-tier architectures—caching, indexes, and background workers—prevents cascading performance issues, guarantees high availability, and maintains scalable SaaS responses.